[INVISION COMMUNITY] - Invision Community 5: Week 1 Update

[NewsBot]

It's been a very eventful week here at Invision Community, with the launch of Invision Community 5 and I wanted to take a minute to give an update on what has happened and what we've learned this week.

Fixes and Patches

Despite being a brand-new platform, Invision Community 5 has had a very low number of critical issues, primarily thanks to months of careful testing and preparation before this release.

We have made two patches this week that fix the following issues:

• An issue where some Cloud sites would block .svg and webp images when uploaded.

• An issue where updating the approval queue during the v4 to v5 upgrade could fail.

• An issue where the Policy Page would show an error when Send Grid is enabled.

• An issue where some template hook locations were missing.

• An issue where PayPal attempts to use a full name even when it's not required.

We've been reading all your posts about your experiences upgrading to Invision Community 5, and there is one area where we think we can improve.

Pages Upgrades

Right now, once the v4 to v5 upgrade has completed, your Page Databases retain their custom templates. However, because the CSS framework has changed, those pages look broken.

We plan to rename all v4 Pages templates containers and reset the defaults on all the databases very soon (likely 5.0.2) so your pages do not look broken after the upgrade. You can then choose from one of the new default views or move your customisations back into the default templates.

We will also add this information to the Invision Community 4 "Prepare for v5" page in the Admin CP.

In the meantime, reverting custom Pages Templates will solve broken views.

Next Release

We want to continue releasing regular releases as we fix issues. Invision Community 5.0.1 is expected to be available early next week.

Before I go, I just wanted to mention that I've heard some customers looking forward to upgrading this weekend. Just keep in mind that support is limited over the weekend, and we always recommend taking at least a database backup before you run the upgrader.

Thanks again for all your help this week!