Jump to content
View in the app

A better way to browse. Learn more.

Learn more

4.7.26 is now available!

You are viewing a curated collection of the most significant posts in this topic with an estimated read time of 7 minutes. The full topic contains 40 posts with an estimated read time of 25 minutes.

Featured Replies

The edit is better, I understand for cloud it being needed potentially as its your servers, its just disappointing to have it affect us who (currently) dont use redis.

I have followed the discussion in the other threads so I dont want to replicate here, just to say our online list was permissions locked and never public so it got no traffic besides me using it for spotting anomalies. Its a pity the admincp online list didnt have a lot of the functions for admin use. I do actually find it incredibly useful when you are monitoring one site.

Edited by sudo

  • Author

Important Update

We have released a patch for 4.7.26 with some important security updates. Please go to AdminCP > Support to apply the patch.

Cloud customers have already been updated, no further action is required.

Downloads of 4.7.26 have been updated with these fixes, if you do not see a patch available on the support page you already have these updates.

On 11/9/2026 at 11:28 PM, sudo said:

just to say our online list was permissions locked and never public so it got no traffic besides me using it for spotting anomalies. Its a pity the admincp online list didnt have a lot of the functions for admin use. I do actually find it incredibly useful when you are monitoring one site.

DavPi has a fix for that.

forum.invisionize.pl - Support Invision Community (IPS4, Invsion Community 5,IP.Board)
No image preview

(DP47) Restore Who's Online

Apka przywraca gości i ich licznik w sekcji "Kto jest online?" w IPS 4.7.26. Pozwala filtrować listę według grup i zobaczyć, jakie strony przeglądają odwiedzający. Adresy IP są widoczne tylko dla osób

One thing I'd like to raise: the latest security fix was published under the very same version number as the release it patches.

As an admin, that leaves me unable to tell from the version alone whether a site is actually patched. It also makes support conversations ("which version are you on?") and keeping track of our own upgrades harder than it needs to be. I wasn't even sure if the disclaimer in the AdminCP isn't scamming me, as I could not find an corresponding patch release notice from Invision.

That got me thinking about versioning more broadly. Have you considered following Semantic Versioning (semver.org)? In short:

  • MAJOR (X.0.0): removals or breaking changes

  • MINOR (x.Y.0): new features, nothing removed or changed in function

  • PATCH (x.y.Z): backward-compatible fixes, including security fixes

The recent changelog, for example, mixed security fixes with feature removals (the online list simplification, the support administrator tool, the legacy loginProcess path).

Under SemVer, admins and plugin authors would see at a glance which updates are safe to apply right away and which need a closer look first. Even if full SemVer isn't a fit, simply never reusing a version number (e.g. 4.7.26 or 4.7.27 for a re-release) would already help a lot.

Would love to hear your thoughts, and whether other admins see it the same way.

Edited by Bonaparte

  • Author
1 hour ago, Bonaparte said:

One thing I'd like to raise: the latest security fix was published under the very same version number as the release it patches.

As an admin, that leaves me unable to tell from the version alone whether a site is actually patched. It also makes support conversations ("which version are you on?") and keeping track of our own upgrades harder than it needs to be. I wasn't even sure if the disclaimer in the AdminCP isn't scamming me, as I could not find an corresponding patch release notice from Invision.

That got me thinking about versioning more broadly. Have you considered following Semantic Versioning (semver.org)? In short:

  • MAJOR (X.0.0): removals or breaking changes

  • MINOR (x.Y.0): new features, nothing removed or changed in function

  • PATCH (x.y.Z): backward-compatible fixes, including security fixes

The recent changelog, for example, mixed security fixes with feature removals (the online list simplification, the support administrator tool, the legacy loginProcess path).

Under SemVer, admins and plugin authors would see at a glance which updates are safe to apply right away and which need a closer look first. Even if full SemVer isn't a fit, simply never reusing a version number (e.g. 4.7.26 or 4.7.27 for a re-release) would already help a lot.

Would love to hear your thoughts, and whether other admins see it the same way.

Right now we have two choices to make, either use our patch system and send out a notification to self-hosted customers or release an update with a new version number. Using a new version number creates extra friction because it'll prompt every customer to run an upgrade when they visit their AdminCP. Quite often this isn't needed with version 5 because we precompile templates and JS. Those not using the latest patch will see a large red banner asking them to update.

Will we stop doing that in future? yes, that's part of the development plan but we have to work within the confines of what's possible today.

1 hour ago, PatrickRQ said:

We have very complex environment, many dependencies were built on the top of IPS. Even with AI it takes time.

I think you may have made my point. To be clear though, we have no plans to extend version 4. It's not fully compatible with newer PHP versions and that large change was implemented in version 5.

Invision seem to be pursuing a method of trying to force people to upgrade to the unpopular v5 by having v4, a perfectly working version, become vulnerable due to a refusal to keep updating it.

  • Management
19 minutes ago, Mack_au said:

Invision seem to be pursuing a method of trying to force people to upgrade to the unpopular v5 by having v4, a perfectly working version, become vulnerable due to a refusal to keep updating it.

We just want everyone on a very secure version of Invision Community that runs on a very secure version of PHP.

To do anything else in the world of agentic AI is insanity.

I've been hired by many clients lately who needed help migrating sometimes very complex platforms from v4 to v5. There are no limitations, nor is there anything you need to lose because of the migration. Get in touch, and the only thing you'll regret is not doing the migration sooner. 😉V5 is a wonderful next step for your community.

Edited by Cedric V

Recently Browsing 0

  • No registered users viewing this page.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.