Matt

The long awaited day is now here: 5.0.0 is now available! We feel that we're ready to fully support v5 and the time has come to make that first release of 5.0.0. While there are outstanding bugs, we felt it was the right time to move it beyond a perpetual beta and into the limelight as our primary version. We're considering this very much a soft launch in that we've still got new documentation to finish, and some large website changes but we didn't want to hold up the release for those. Thank you all so very much for your months of testing, feedback, help, support and time. You have been invaluable in moving this project forward. We started alpha testing way back in June 204 and this is probably our most tested release, and we have you to thank for this. While today marks the release of 5.0.0, it's really the starting line for us and we can't wait to build on it and see it evolve over the next year. We're not slowing down the pace, and I would expect 5.0.1 to follow pretty soon. We made it! We'll keep this club open for a while, but you can now post your feedback in the main forums. If you have any old Alpha 5 demos, these will expire soon but if you needed a short extension to get data off it please let us know.

Changed Beta Release to No

Changed Current Release to No

A little update is on its way into the cloud to fix a few issues: Fixes issues with last post timestamps Fixes an issue when attempting to access security settings Fixes an issue with the Search API Fixes an issue with cloud email Fixes issue where logos were disappearing in the theme editor

Changed Long ID to 5000048 Changed Release Date to 02/03/2025

Yes, at some stage we'll put that into an upgrade step as an option.

I'll do a patch today for this.

Removing features is never easy and it's something we don't take lightly. I understand the argument that we could just leave everything the way it is, but that won't help us progress. And progress we must. We have finite development resources, this means that we have to focus on toolsets which are needed for the current age. We announced the username log-in deprecation in 2022. It's not something new with v5. All we have done is followed up on the deprecation. Status updates were put into Invision Community during the boom time for social media where we felt we needed to add social tools to remain competitive. However, on most communities these are unloved areas of the community full of throw away comments and unanswered questions. I know that a small number of communities thrive on status updates which is why we've kept the data and our considering migration options. In the mean time, the third-party developers have stepped up with different solutions. Finally, a reminder that v4 will remain a viable platform for quite a while yet so there is no urgent rush to upgrade to v5 if you need more time to plan your upgrade and find solutions to deprecated features.

Our plan is for a fairly soft and quiet 5.0.0 release and then focus on the needs of those moving from v4. We keep all the status data, so it's trivial to convert it into a forum, or whatever if/when we wanted to do that. If the need isn't huge, I might just do a one-off app or something that does it rather than bake it into the product, but we won't know until more people start upgrading.

Yes, it's been reverted while we work out some issues with it. The column can remain, that's fine.

Just released a little update to fix a few things. #3463: Fixes an issue where in some cases forumRow will throw an error #3449: Restore IPS Template Highlighting Outside of Editor #3457: Removed refresh button from Android PWA #3459: Use featured color for indicator

Changed Status to Fixed I'll do a patch today for this.

Changed Status to Fixed

Changed Status to Not a bug

The old style Ajax polling has been removed in v5. It is not terribly efficient and it's generally better to push when there is new data rather than constantly pull. This is what we do with Invision Community Cloud.

Changed Status to Fixed Thanks, all sorted for the next beta.

It isn't funny, I think Esther just meant that it considers its own theme to be invalid silly. Do you have your v5 site credentials stored in the client area? I'd like to take a look.

Thanks! We really appreciate the feedback and I'm pleased that you're enjoying it. 5.0.0 is just the beginning, we're excited to develop it further over the year.

If you DM me the URL, I can take a look.

Are things marked when you manually refresh the page?

There is a fix that we're testing in this Beta.

I just used it and it marked it all as read. Can anyone else reproduce this?

Two days is a long time in Invision Community: Beta 14 is out. We've only gone and released Beta 14 a mere 48 hours after releasing Beta 13! This has some fixes for the achievements form, custom image setting fields and last post information. We wanted to get some extra testing done. It's almost like we're preparing for something soon. 🤔

Changed Current Release to No