Matt

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.

Changed Current Release to No

You could always move to cloud and have proper guest page caching and a very fast CDN which will help. 😇

Nothing significant changed, I've been through the PRs that were committed. I find running Pagespeed on different days gets different results.

I've just moved it to a ticket, can you check your FTP/admin credentials in the client area and I'll take a look.

I'll review the changes but nothing springs to mind.

What was the previous version you had used? The code Matt has found was from way back in February. Oh and, Beta 4 is out around now.This has just one fix for the forum listing's last topic/author info for when you're using the classic table view. I wasn't brave enough to roll it right into final, so we'll do the final release tomorrow if nothing explodes.

Beta 3 is now available We've just made Beta 3 available. This restores the new permission extension system, and fixes a few more issues: #4559: Commerce category image ratios are now consistent across site #4558: Allow Theme Editor to change secondary buttons #4545: Additional settings for Community Experts #4552: Polished Announcement UI - Issue #4451: Minor UI bugs (announcements) - Issue #4463: Minor UI bugs (announcements (2)) #4550: Group badges no longer shrink in topic lists #4551: Improved the RSVP block when viewing events #4553: Made Guidelines header consistent with other pages #4548: Allow Editor Embeds, Giphy Images and Stock Replies in ACP #4547: Remove core_hive_subscribers DB table #4546: Ensure archived topics are not updated by TopicSync #4543: Fix Build Extension Skeleton File #4542: Fix an issue where extensions from the Extension Generator were not loading correctly #4541: Fix an issue where tags converted to lowercase used the wrong URLLet us know how you get on!