Matt

I've just pushed 5.0.8 Beta 3 to deployment, which should show up soon.There's not a huge amount that has changed, but we wanted just to test one last thing before we release the final version tomorrow.

Long before 3.0 is released. But then the sun will die in about 5 billion years and that may also be first.

The patch is safe. It's a few lines of code. The people that have been having trouble and been doing things like this:

I'll DM you, there's a few things odd.

Are you client area details up to date? I can take a look now for you. DM me if anything has changed.

I hear what you're saying but our build system is pretty fixed in its ways. When we release a new build ID (107803) as a git tag, we can name it either something new (4.7.21) or call it the same as the current release and then it'll be detected as a patch. A patch is often an easier path for customers because a full release (new human ID) would mean you'd have to run the upgrader. Also we tend to assign out human IDs a little in advance, so we have a lot of 4.7.21 already done by the time we needed to make a patch, which would mean we'd need to mess with tags in git to reset them to new IDs. For example, with 5.0.7, we already had a 5.0.8 in beta testing. We are looking to improve the patch system so that they are surfaced to the dashboard so it is more clear. There hasn't been a chance in unread icons. The changes were for the oauth call back endpoint and calendar events. Do you get this resolved? Just upload the files from the zip to the your server, overwriting the existing files.

Invision Community 5.0.8 Beta 2 is out! The full list of changes in 5.0.8 has been updated in the release notes. The changes between beta 1 and beta 2 are as follows: #4763: Update gallery carousel links when changing the image - Issue #4632: [5.0.7] Gallery Carousel Does Not Advance - Issue #4616: [5.0.7] Comments Box In Gallery Doesn’t Appear Without Refreshing #4728: Fixes an issue where the menu form won’t load when there are many tags #4704: Implement recommended tags #4765: Clear Custom CSS Draft when empty Custom CSS field saved #4756: Improved alignment of staff page #4754: Improved alignment of poll vote counts #4752: Improved alignment of "Club pending approval" message on mobile #4750: Improved alignment of some FA icons #4748: Removed social SVG icons from accessibility tree #4746: Fix an issue where a deleted achievement rule can throw an exception #4745: Fix an exception when moving comments from pages to forums #4743: Fix an issue where theme editor settings were always marked as edited #4742: Fix an issue where widgets would override dev-defined templates #4736: Prevent focus-within from collapsing title #4734: Fix an issue where club membership status was not properly updated after accepting an invitation #4733: Improved the REST API documentation for the transaction object #4732: Fix an issue where the contact us editor was not cleared after submission #4731: Editor dropdowns no longer appear behind upload area text #4727: Fix an issue where importing pages dev templates did not always set the correct group #4724: Fixes an issue where the contact us form guest verify process fails #4719: Replaced lingering ipsButton--intermediate with ipsButton--primaryRecommended TagsIf you have a lot of tags and want a way to surface a smaller subset of them to the top, then recommended tags is for you! Any tag 'recommended' via the AdminCP will show at the top of the list when tagging in content. Let us know how you get on!

We've released a security update for Invision Community 4.7.20 and Invision Community 5.0.7We recommend that all those using Invision Community update to the latest version as soon as possible. Please note that Invision Community Cloud and Enterprise customers on either v4 or v5 already have this security update applied. What does this update do?This update fixes two issues in Invision Community 4.7.20 and one in Invision Community 5.0.7. We will update this topic with more information when we're confident most customers have upgraded. These issues were reported to us by Egidio Romano from Karma(In)Security. We thank Egidio for reporting these issues to us as always. I'm using the self hosted version (Invision Community Classic) on a version older than the latest, what should I do?You can upgrade to the latest versions of 4.7.20 or 5.0.7 via the AdminCP. Follow the instructions in the banner to upgrade to the latest version which has been updated to include the security update. I'm using Invision Community 5.0.8 Beta 1, what should I do?You can upgrade to Invision Community 5.0.8 Beta 2. I'm using Invision Community Cloud, what should I do?You don't need to do anything. All packages except Invision Community Classic are already protected even if you're not on the latest version. If you have any questions, let me know!

Of course. :)

Unfortunately not. The only way to do it would be to essentially have a text area where you manually type in your entire post but then what happens if a user who doesn't have admin permission to edit it? The post will end up being almost entirely stripped as Tiptap doesn't understand it. You wouldn't be able to toggle between a HTML post and a normal editor. Can you tell me more about your specific need?

I'd recommend Laravel Herd for localhost. The only thing I can think of is \n versus \r Just add define( 'UPGRADE_MD5_CHECK', false ); into your constants.php file.

5.0.8 Beta 1 is now available! We have a bumper beta ready for you all this week. Head over to the release notes to see the full list. Along with many fixes, this release brings a lot of accessibility updates, UI improvements, new permission extension methods to force include or deny specific node IDs in getItemsWithPermission and nodesWithPermission We also have a little beta-ish feature we're calling 'Node Groups'. Groups are a way to easily select multiple forums as a moderator in different areas of the suite. You set up Groups via the Forum page in the AdminCP and then when, as a moderator, you go to choose forums in a forum selector (default streams, saved actions, etc) you can easily select that group instead of having to remember all the forums you'd normally select. In this little example, I create a group for 'Support' which includes my support forums. Then, when I create a new saved action that I only want to apply to my support forums, I can include that group. The great thing is that it auto-updates. So adjusting the Forum Group will automatically update where that saved action is available. We're still rolling this out across the suite, but let us know your thoughts.

We've released a security update for Invision Community 5.0.7 for those using Invision Community Classic.We recommend that all those using Invision Community Classic update using the AdminCP as soon as possible. To do this, log into your AdminCP, head to System > Support and apply the patch from the top left box. Please note that Invision Community Cloud and Enterprise customers already have this security update applied. What does this update do?The update fixes a security vulnerability with the theme editor. This issue was reported to us by Egidio Romano from Karma(In)Security. We thank Egidio for reporting this issue to us. I'm using the self hosted version (Invision Community Classic) on a version older than 5.0.7, what should I do?You can upgrade to 5.0.7 via the AdminCP. Follow the instructions in the banner to upgrade to the latest version which has been updated to include the security update. I'm using the self hosted version (Invision Community Classic) who upgraded to 5.0.7 previous to this announcement, what should I do?You can use the patch system as described at the top of this post. I'm using Invision Community Cloud, what should I do?You don't need to do anything. All packages except Invision Community Classic are already protected even if you're not on the latest version. If you have any questions, let me know!

It's more likely a caching issue, I'm sure we can improve it by ignoring the cache if we get specific header codes.

And as a reminder, even Google's own sites fail core web vitals.

This is the balance you must find. As soon as you start adding images, and more JS then things start heading lower but then is your priority as a community owner to create the fastest page possible, or create a rich community that is partially funded through advertising? Pagespeed is important, but so is paying the bills and having functionality that humans need.

Ok, 100% safe.

100% safe. Wait 99% safe Well it's above 60%.

I feel the same about building each release. Help is never far away though. 😀

Should be all sorted now.

Can you send in a ticket, attached to your cloud account and I can take a look.

Oh, that site is with the dinosaurs now. I'll probably deactivate it. It's not been updated for a while.

Whatcha doing there Riko?

This is an odd one. I can reproduce it but no one else can. I have a PR for the next release, but in method download() of file applications/core/modules/admin/applications/applications.php just remove Phar::unlinkArchive($pharPath); for now. That will solve the error.