Jump to content
View in the app

A better way to browse. Learn more.

Learn more

5.0.20 is now available!

This topic contains 45 posts with an estimated read time of 24 minutes. A summary containing the most significant posts is available with an estimated read time of 6 minutes.

Featured Replies

man in white shirt holding us a flagPhoto by Glen Rushton on Unsplash

One more lap.

We've been around the track a few times now, but we're not quite ready to wave the chequered flag on 5.0 just yet.

Before we move on to 5.1, we've got one final minor release for you.

Besides the normal bug fixes in this release, we've also added Opensearch powered suggestions when creating topics or Pages Records. You can see this in action on our community.

image.png

You can find the full change log here

Can the beta update be used in production, or are beta versions generally considered safe? And once the stable version is released, will it be possible to update directly from the beta version to the stable release?

4 minutes ago, DracoBlue said:

Can the beta update be used in production, or are beta versions generally considered safe? And once the stable version is released, will it be possible to update directly from the beta version to the stable release?

Beta versions are considered beta. We recommend only final releases for live use. You can use them on a live site, and we consider them safe. But if you are unsure, use the stable release. You can indeed upgrade from them

4 minutes ago, Marc said:

Beta versions are considered beta. We recommend only final releases for live use.

Client Area

We consider beta releases generally safe to use on a live site, but, as a beta release, there will probably be undiscovered issues. Any issues on your community during the beta stage may not be fixed until a future release. We will usually not specifically address any individual issues on your community. This means you will have to wait (sometimes several days) for a new release to get fixes.

Edited by DracoBlue

Yes, we consider them generally safe to use on live sites. But as beta you may find issues. Recommend is the stable release of course. If you are unsure (as you seemed there) then stable releases would be the best option

Alpha - Things are probably going to be broken
Beta - If nothing breaks, this will end up stable. We think its good to go
Stable - Recommended for most people

To explain my answer above more clearly. If you are personally unsure, use the stable release. If you have already read the disclaimer, as you clearly have there. And you are sure. Go ahead. Of course if we 'can' use it on a live site, you can indeed upgrade. I have expanded on my answer above so as not to cause confusion

  • Author

5.0.20 Beta 2 is out.


#7473 Fixed an issue upgrading on plans with Quests.
#7475 Fix an issue where Stripe was not automatically taking payments where gateways were limited to specific countries.
  • Stuart changed the title to 5.0.20 Beta 2 is now available!

For suggestions to work I assume we need to change from MySQL to Opensearch in the CP, and that a server is provided. We're on cloud.

So, is the stable version coming on Monday? 😅

#7212 Hide banned members from search results and profile views

OMG Thank you! Now I don't have to manually scrub spam links and text they put in their profile anymore.

Edited by C0MRAD

Testing the Opensearch suggestion on this site. Using event as the word in the new post title:

Works in Feature Support and Design and Customization forums.

Doesn’t work in Ideas and Requests.

Such a great idea…

19 hours ago, DracoBlue said:

So, is the stable version coming on Monday? 😅

I can tell you thats a no :)

7 hours ago, NSPN said:

Testing the Opensearch suggestion on this site. Using event as the word in the new post title:

Works in Feature Support and Design and Customization forums.

Doesn’t work in Ideas and Requests.

Such a great idea…

I think it's enabled per-forum, but then, I'm still in middle of coffee #1 so my memory is only at 90% accuracy.

Testing 5.0.20 Beta 2 in a demo environment - Maybe found a bug with menus?

I have set Pages as my default app.

When I use the default menu and click Forum it goes back to the default "Pages" page & NOT to my forum page

I can make a new menu item and it works fine except the the breadcrumb links back to the default "Pages" page.

I can make a new menu item for the forum and it works fine but that does not fix the breadcrumb.

10 hours ago, John Horton said:

Testing 5.0.20 Beta 2 in a demo environment - Maybe found a bug with menus?

I have set Pages as my default app.

When I use the default menu and click Forum it goes back to the default "Pages" page & NOT to my forum page

I can make a new menu item and it works fine except the the breadcrumb links back to the default "Pages" page.

I can make a new menu item for the forum and it works fine but that does not fix the breadcrumb.

This was very odd. Seems it was the default app hadn't saved properly. When I switched it out then back again it corrected the problem

  • Stuart changed the title to 5.0.20 Beta 3 is now available!
  • 2 weeks later...
  • Author

5.0.20 Beta 3 is out.

Changes since beta 2:

#7488 Fix archiving resetting itself on cloud even if it's not forced.
#7512 Stop Redis SORT from locking up the online list
#7529 Moving CMS Records does not trigger topic creation.
#7530 Fix Workflow key changing when editing.

search.png
I developed a comparable script that calculates the match percentage and disables the submit button in the DOM when it exceeds 88%, not just through CSS. It works with any application by just adding the input ID. It would be helpful if you could implement a similar feature.

On 9/12/2026 at 5:12 AM, Baian007 said:

search.png
I developed a comparable script that calculates the match percentage and disables the submit button in the DOM when it exceeds 88%, not just through CSS. It works with any application by just adding the input ID. It would be helpful if you could implement a similar feature.

Its not clear what you are trying to achieve there, or how this relates to the latest beta. Please could you clarify?

@Marc If i look close to it, it seems that if a post looks like AI with a rating of 88% or higher, it disabled the post submit button. So it seems to be an AI text blocker.

  • Stuart changed the title to 5.0.20 is now available!
  • Author

5.0.20 is now available.

There's only one change since the previous beta.

#7540 Port subscription upgrade logic from v4.

Um... any idea what this is about? These are IC5 core apps, and they're somehow not compatible with this update?

Screenshot 2026-09-16 at 20.27.46.png

EDIT: For what it's worth, all IC5 core apps are on the same version (all 5.0.19) so it's not that they need to be updated first as the installer advises. Any ideas?

Screenshot 2026-09-16 at 20.32.14.png

Edited by Dreadknux

4 minutes ago, Dreadknux said:

Um... any idea what this is about? These are IC5 core apps, and they're somehow not compatible with this update?

Screenshot 2026-09-16 at 20.27.46.png

Did they not download as part of the other files being applied?

Just now, Jim M said:

Did they not download as part of the other files being applied?

Hm, that might be it actually, when it did the download/extraction thing the loading bar crashed out and I had to reload, so it probably didn't download from the source... should I download the package directly from the client section and upload myself, or do you recommend another method?

5 minutes ago, Dreadknux said:

Hm, that might be it actually, when it did the download/extraction thing the loading bar crashed out and I had to reload, so it probably didn't download from the source... should I download the package directly from the client section and upload myself, or do you recommend another method?

Yeah, manual upload will be the only way if the upgrade was partially applied, I'm afraid.

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.