The new Clubs feature has been a huge hit with Invision Community users and we are expanding it to include invite-only options, notifications, exposure on the main community pages, paid memberships, and more.

Custom Email Footers

Your community generates a lot of email and you can now include dynamic content in the footer to help drive engagement and content discovery.

Admins can set an option so any Club a member is part of will also show in the parent application. So if you are in a Club that has a Gallery tab then those image will show both in the Club and in the main Gallery section of the community.

Club members can now follow an entire Club rather than just each content section.

There is a new option on the Club directory page for a list view which is useful for communities with many Clubs.

If you have Commerce you can now enable paid memberships to Clubs.

Admins can set limits on number of Clubs per group.

If a group has delete permission in their Club, they can now delete empty containers as well.

Members can ignore invitations.

Moderation and Administration

Unrestricted moderator or administrator permission sets in the AdminCP are visually flagged. This prevents administrator confusion when they cannot do something as they will be able to quickly see if their account has restrictions.

Direct support for Sparkpost has been removed. Anyone currently using Sparkpost will automatically have their settings converted to the Sparkpost SMTP mode so your email will still work.

Your cache engines (like Redis) will be checked on upgrade and in the support tool to ensure they are reachable.

Third-party applications will now be visually labeled to distinguish them from Invision Community official applications.

The queued tasks list in the AdminCP is now collapsed by default as queued tasks are not something people need to pay much attention to during normal operations.

When upgrading from version 3 series you must convert your database to UTF8 and the system saves your original data in tables prefixed with orig. The AdminCP now alerts you these are still present and allows you to remove them to reclaim storage space.

On new installs there are now reasonable defaults for upload limits to keep people from eating up storage space.

Categories in all apps (forums, gallery albums, databases, etc.) no longer allow HTML in their titles. This has been a concern both in terms of security and usability so we were forced to restrict it.

Large improvements to the Redis cache engine including use for sessions.

The login with HTTPS option has been removed and those who were using it will be given instructions to convert their entire community to HTTPS.

Images loaded through the proxy system now honor image limits for normal uploads.

We now consider BBCode deprecated. We are not removing support but will not fix any future issues that may come up.

There's a lot to talk about here so we are going to lock this entry to comments so things do not get confusing. Feel free to comment on upcoming feature-specific entries or start a topic in our Feedback forum.