Dreadknux

Not sure what’s happening here, but I just checked my V5 instance on Google Chrome (macOS) and it’s looking a bit crazy in there. Here’s how it looks on desktop Safari (Version 18.0 (20619.1.26.31.6)), as it should look: Here’s the same page on Google Chrome (Version 129.0.6668.59 (Official Build) (arm64)): Here’s a different set of blocks on the same page in Safari, as it should look: And here’s the same set of blocks on latest version of Google Chrome: I’ve tried resetting caches, hard-resetting the page, even updating and closing/re-opening the browser. But it still looks the same broken mess on Google Chrome. :( EDIT: Also getting some crazy design issues on this instance too:

I have this image widget on the Page Editor. I have its visibility settings saved so that it should only appear in Desktop view. But it still appears when sizing the browser window down to ‘tablet’ resolution. And when viewing the site in Theme Editor, the block is still visible when setting the view to ‘Tablet’. ^ The block appears in “Large (desktop)” view - this is correct. ^ The block still appears in “Medium (tablet)” view - this is incorrect. The block disappears when Mobile view is activated, as expected. It’s just Tablet view where the block ignores the command and still appears.

I think I had a similar issue in a past alpha, but upon taking screenshots for an entire different topic for the Suggestions forum I came across this whopper. Steps to replicate (for me, anyway): Create Topic Post Topic Actions > Copy to Database > Create Article from topic (Fields changed: Title, Content, Allow Comments [from unchecked to checked], Copy Posts [from unchecked to checked], Show Item Message? [from checked to unchecked], Use Original Author [from checked to unchecked], Image added, Tags added) See the following error: OutOfRangeException: (0) #0 /var/www/html/5000021/applications/cms/modules/front/database/topic.php(322): IPS\Patterns\ActiveRecord::load(23) #1 /var/www/html/5000021/system/Dispatcher/Controller.php(128): IPS\cms\modules\front\database\topic->form() #2 /var/www/html/5000021/applications/cms/modules/front/database/topic.php(84): IPS\Dispatcher\Controller->execute() #3 /var/www/html/5000021/system/Dispatcher/Dispatcher.php(169): IPS\cms\modules\front\database\topic->execute() #4 /var/www/html/5000021/index.php(16): IPS\Dispatcher->run() #5 {main} Backtrace: #0 /var/www/html/5000021/init.php(859): IPS\Log::log('OutOfRangeExcep...', 'uncaught_except...') #1 [internal function]: IPS\IPS::exceptionHandler(Object(OutOfRangeException)) #2 {main}

As of Alpha 12. Ehren shared the following code in order to allow any main-content elements to adjust their positions to the size of my sticky headers: :root{ --i-scroll-padding: calc(var(--i-headerPrimary--he) + 10px); --i-sticky-offset: calc(var(--i-headerPrimary--he) + 10px); }But this seems to no longer work in the latest version. Has the CSS logic changed? In inspector, I can see some new variables: The first two seem new, not sure what the difference between those are, and the third doesn’t seem to be listening to my override CSS code at the top there. Any ideas?

Dialog boxes that float when using Page Editor stretch off to the side of the browser window, and clicking a block will show its options menu taking up the entire height of the browser. Chrome Version 127.0.6533.100 (Official Build) (arm64) on macOS 14.5

Not sure what’s going on here, maybe it’s part of the ongoing (and still happening, sadly) issue where tags are not appearing in content items (despite being added and visible in listing pages)… but I’ve noticed that nothing appears in the Tag area of a Page record when viewing as a guest. Guest User: Logged in User: Note the Tag section underneath the headline/featured badge. Appears for logged in users (but only prefix tag, it seems) but nothing at all for Guest. If the concept for IC5 is to use tagging as as the backbone for content discovery, it’s important for Guests to be able to view and access tags the same way as logged-in users.

Not sure if this is a bug or not but thought I'd flag it. I embedded a local content link elsewhere on this site, and the embed looks kinda strange. There’s a quote box within the embed wrapper that basically duplicates the same content as the embed box itself. There isn’t any need for the quote box (or its contents) to be there, really.

I swear I have logged this somewhere before (maybe on the Alpha Club on the main IPS site) so apologies for bringing it up in a new topic rather than bumping an existing one… But this is still an issue in the current alpha version. See below;

I click ‘Theme’ at the bottom of the page, and no menu appears. On macOS 14.5 using Chrome Version 127.0.6533.100 (Official Build) (arm64)

If a Page record has not been given an associated image when created, the ‘Cover Photo’ options still appear but is not clickable. There is no default cover photo area displayed like in other areas of the suite (tag pages, profiles, etc).

It seems that posting a topic and then copying to database will create a duplicate topic in the forum, rather than integrate the page record into the existing topic. The top forum topic item there is the original, which I copied to make the article (which created the bottom forum item in the image above there). My AdminCP options are exactly the same as in V4, so there shouldn’t be anything weird going on from that side of things: I actually just tried to replicate the steps in order to full screenshot every step, but when I copy-to-database’d a brand new original topic and hit ‘Save’ on the post editor, I received this error message instead: Not sure what’s going on there, but the duplication of topics is definitely not expected behaviour.

Seems to happen on profile hovercards and on Tag pages which don’t have a cover image set. ^ This one extends a fair distance outside of the boundaries of the covercard. ^ This one goes a little crazy and goes waaaaay off the page! :) EDIT: Just saw it on profile page too, when checking reputation (it doesn’t go OOB when checking the profile page in general): And again on a Tag page, this time with an uploaded cover image, on a mobile view (note: this screenshot was made on a desktop browser with the browser window narrowed to mobile width, not on an actual mobile device, if that helps):