On 2/28/2026 at 2:34 AM, Nuclear General said:

There seems to be an issue with the final 5.0.16 release. When you have an ipsDialog box open, you cannot scroll the site. It removes the scrollbars from the browser window.

Its not clear what you mean here, as havinga dialog open would usually mean you dont have access to what is behind it. Could you please screenshot what you are referring to?

here is a video. it shows 5.0.14 and 5.0.16, you'll notice that the scrollbar on the right disappears when a dialog box pops up on 5.0.16 but not on 5.0.14

There shouldnt actually be a scroll bar when there is a dialog. There isnt anything to scroll

Here's one of the Applications page on 5.0.14 and 5.0.16 where there should be scrollbar when the upload dialog is open

16 minutes ago, Nuclear General said:

Here's one of the Applications page on 5.0.14 and 5.0.16 where there should be scrollbar when the upload dialog is open

While I am not self-hosted, if you have a wheel on your mouse and move your cursor over to the underlying page and manipulate the wheel, it does scroll the page.

Yes. However the bug is on the previous release, rather than the latest.

2 hours ago, Marc said:

Yes. However the bug is on the previous release, rather than the latest.

No, the bug is in the latest version, and not in the previous release.

When i want to react on a user with a smiley, then suddenly the scrollbar is gone, and can't go lower to select a smiley for example.
So when the drop down is open, and is partly below the lowerpart of the screen, you cannot scroll down to view the dropdown for example.
Middle mouse wheel is also locked-out.

I think the orginal bug report that was fixed, was then a popup was open, and you scrolled down, the popup was out of view and the website looked "grayed out"
So i think this locking was a fix to prevent that.

My solution to this would, to allow the scrollbar, but reposition the popup, when scrolling down, so the popup is always in view, but you can still scroll.

Ah, thats 2 different issues. Where you were showing in your previous videos, that is by design and fixed. What you are showing in your image there is that its affecting a dropdown, which it shouldnt be. That is indeed a bug which I will add to our tracker

7 hours ago, Marc said:

Ah, thats 2 different issues. Where you were showing in your previous videos, that is by design and fixed. What you are showing in your image there is that its affecting a dropdown, which it shouldnt be. That is indeed a bug which I will add to our tracker

How would that be by design now? I don’t like how I cannot scroll anymore when a dialog box is open. That is not a fix in my opinion.

Edited March 5Mar 5 by Nuclear General

1 hour ago, Nuclear General said:

That is not a fix in my opinion.

Repositioning the popup to stay in view when scrolling, would be a fix for you? At least for me yes.

Edited March 4Mar 4 by Moestuin

I’d rather the dialog box remain functional while still allowing the entire page to scroll. Locking the page in place isn’t a fix—it’s a hindrance. One of the useful aspects of the current behavior is being able to open a dialog and still scroll the page to see the surrounding context. With the ‘fix,’ the experience is actually worse than before. Disabling page scrolling whenever a dialog is open is the wrong approach.

Edited March 5Mar 5 by Nuclear General

When the dialog is open, you should not be able to interact with anything behind it. The dropdown however isnt one of those, so that is a bug

Any active users want to give me a rundown on version 5? I'm currnetlly on version 4.7.23 classic/self hosted and I'm very happy with the set up today. I just clicked the license update button so I have access to 5 now.

I have one custom created app by a dev, and a couple vibe coded apps (game changing for me).

I want to hear about any gotchas or anything like that. I'll probably do the upgrade on a test server since this is the first upgrade since i started vibing.

Just looking for crib notes, I can figure things out....

Hi @cascadeclimbers,

Long story short, apart from emphasising the importance of a full backup for your existing community, any apps or plugins you have installed on v4 will likely not work in v5.

You would have to engage the original developer to confirm whether the app can be updated to work on v5 and use your test installation to confirm the vibe-coded apps work for your use case.

Ooof!!! That sucks! I’ll being herded towards the upgrade cliff due to PHP, but my apps likely won’t work going from 4 to 5!

Well I guess it’s work just gonna be a lot of testing and updating apps (I have 3). Thank you @Gary appreciate your guidance.

anyone here who has made the jump from 4 to 5 comment on how difficult it was to update apps so they work in 5? With how well using Claude works now (and it’s only getting better), I would think this isn’t going to be too bad. Is 5 that drastically different when it comes to apps that a slight adjustment to an existing 4.x app won’t work?

And of course @Gary ! Backups backups backups

27 minutes ago, cascadeclimbers said:

but my apps likely won’t work going from 4 to 5!

They absolutely wont. You would need updates from the authors of those applications.

Yeah I got the full rundown from Claude. I have a plan. 6 months ago I would have been in a bad spot with all this, but the world is far different now.

“The authors”. 😉. This is gonna take a lot of tokens.

28 minutes ago, cascadeclimbers said:

Yeah I got the full rundown from Claude. I have a plan. 6 months ago I would have been in a bad spot with all this, but the world is far different now.

“The authors”. 😉. This is gonna take a lot of tokens.

Make a subdomain like beta.yourdomain.com and restore a backup from your www to that.
Then adjust config/make that domain working, protect with .htaccess user/pass so it won't be public for everyone.
Use your -testinstall key from invsion community.
Do the upgrade first on on you beta envoiremnt. Then style and fix the plugins what you need, when your don't you can copy over the config / changes when your going to upgrade your www.

Thank you @Moestuin !

Is there a reason why the latest update is telling me my version of PHP is unsupported, when it is in fact newer than the recommended minimum version?

Among the other issues I've been dealing with, this isn't a welcome notice tbh, especially seeings as this latest update is being listed as a serious security update. Can this be fixed please? I shouldn't have to downgrade my PHP just to meet an upgrade check...

3 minutes ago, Dreadknux said:

Is there a reason why the latest update is telling me my version of PHP is unsupported, when it is in fact newer than the recommended minimum version?

Among the other issues I've been dealing with, this isn't a welcome notice tbh, especially seeings as this latest update is being listed as a serious security update. Can this be fixed please? I shouldn't have to downgrade my PHP just to meet an upgrade check...

Take a look here for more info on this

https://invisioncommunity.com/forums/topic/486657-5017-is-now-available/page/3/#findComment-3020037

1 minute ago, Marc said:

Take a look here for more info on this

https://invisioncommunity.com/forums/topic/486657-5017-is-now-available/page/3/#findComment-3020037

OK, thanks Marc. Any way I can cancel the upgrade process, so that my community doesn't continue to see downtime while I seek a downgrade path for my php?

1 minute ago, Dreadknux said:

OK, thanks Marc. Any way I can cancel the upgrade process, so that my community doesn't continue to see downtime while I seek a downgrade path for my php?

The only way is to revert to your backup