Jump to content
View in the app

A better way to browse. Learn more.

Learn more

4.7.26 is now available!

This topic contains 40 posts with an estimated read time of 25 minutes. A summary containing the most significant posts is available with an estimated read time of 7 minutes.

Featured Replies

22 minutes ago, Stuart said:

If that's the case, why will it take you so long to update to version 5?

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

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.

Unfortunately, that would not really constitute a reason or us delaying the end of version 4 due to AI really. End of support for the product entirely was announced to give 9 months to migrate. At some point, we do have to stop, and place more emphasis on version 5.

Its worth pointing out here, the advent of AI would actually make it more important we concentrate on a single major release, rather than less.

  • 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.

7 minutes ago, Stuart said:

Using a new version number creates extra friction because it'll prompt every customer to run an upgrade when they visit their AdminCP.

May just be true for version 4.x.x & self-hosted customers, but the upgrade had to be done anyways.

7 minutes ago, Stuart said:

Will we stop doing that in future? yes, that's part of the development plan

Sounds good & looking forward to have more clarity for such occasions in the future.

In any case thanks for publishing fixes asap. ❤️

Edited by Bonaparte

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.

28 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.

I find it wild to post such in a topic for a recent security patch for their v4 product. And I am by no means a fanboy of v5 (yet) - but as pointed out already the EOL has been clearly communicated early enough - also if the v4 product is considered "perfectly working" then it is up to your accountability to keep your (self-hosted) installation on that (soon to be discontinued) release ring.

Luckily we are living in a world where one can freely choose the product from any vendor they like.

Edited by Bonaparte

5 hours 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.

I've been porting over our v4 to v5 and while I wasn't a fan initially it's not as bad as even I thought. I'll give you it's different but in a lot of ways good.

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

After the latest update, when I log in to the control panel I get to see the converter as the default page and not the dashboard. It's been years since I had converted from phpbb2.

image.png

4 minutes ago, Andreas Grace said:

After the latest update, when I log in to the control panel I get to see the converter as the default page and not the dashboard. It's been years since I had converted from phpbb2.

image.png

Needs a ticket opened. Did you set the permissions for each group as the message says?

1 hour ago, Stuart said:

On the Applications page, I suspect you have the Converter application above the System application. Re-order them so System is at the top!.

Thanks, Stu, this fixed it! By the way, it was a long time since I saw the converter page, it reminded me of the great job you had done getting me to invision from my heavily modded phpbb2.

On 11/14/2026 at 1:55 AM, Marc said:

Its worth pointing out, there are considerably more people using version 5, than there are using version 4

That's not a surprise when by cancelling security updates for v4 you're effectively forcing people to move to v5 no matter how unpopular doing so is.

5 minutes ago, Mack_au said:

That's not a surprise when by cancelling security updates for v4 you're effectively forcing people to move to v5 no matter how unpopular doing so is.

Sorry to hear you feel that way. Unfortunately, it’s simply not possible to please everyone.

The reality is v4 was in need of modernisation and is over a decade old at its core. We have done well, in our opinion, to keep it up to date as long as we have. A testament it seems you share, given you would like it to stay. New versions will eventually come, as with all software.

Let me give an insight as to how long we have kept going with version 4, by giving examples of where others were at the time.

Chrome was on version 41. It’s now on version 154

Internet exporer was still supported and edge didn’t exist. Edge is now on version 158

safari was version 8 and it’s now version 27

PHP was 5.6 and now 8.5

MySQL was 5.6 and now 8.4

these are the technologies that the base of Invision 4 was built around. Windows has had 2 major releases and macOS has had 3.

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.