Matt

We can renew it one more time. Pretty soon we're going to have to cull all these demos as we move towards the final release.

tl;dr we chose a fixed range of colours that we adapt based on if you are using light or dark mode. Adding any colours may mean posts are illegible on either light or dark mode.

Where are you hooking it?

It's a bit too broad of a question to answer with any real insight. What is it you want to do?

Should be fixed in an hour or so. Thanks for your patience.

It's removed in Beta 5.

Beta 5 is out, and you can blame Mick for the title of this post. 😅 If you're under 40, you'll have no idea what that gif is all about, don't worry. It's just an ancient movie from the before times. Anyway, Beta 5 is working its way through the cloud system and will be available in your AdminCP shortly. As always, the full change log is here: https://invisioncommunity.com/release-notes-v5/ Thanks!

Changed Current Release to No

Sorry. It’ll be tomorrow now.

It's getting a bit late here in the UK. We'll get it out Monday.

Ehren, you look different today.

This is wonderful Jimi! I'll get this out across our social channels.

I'm going to tag in our CSS maestro @Ehren for assistance.

A merge tags feature wouldn't be a bad idea for when people change their minds.

v4.* you can keep using MyISAM. It's only version 5 that enforces InnoDB.

We really require InnoDB for v5 as it's a vast improvement on MyISAM. As we develop new functionality, we want to make use of foreign keys which MyISAM doesn't support.

We do not mention account deletion, just to clarify.

Invision Community 4.7.19 will be released in November and contains many updates along with the report center improvements. While Invision Community 5 moves through the beta process, I wanted to let you know about all the updates coming in Invision Community 4. I've already spoken about the Report Center updates, which bring more professionalism and compliance to that area, and this blog will outline a few other highlights for the forthcoming release. Dormant Account Login Notification Keeping member accounts secure is a top priority for all community teams, and with data breaches containing usernames and passwords regularly shared on the dark web, it makes sense to be vigilant to a potential account takeover. Your members will now receive an email if a successful login occurs six months or more since the last log in to ensure the account is still in the right hands. If the account owner is not responsible for logging in, they can contact the community team to ensure the account is returned to the owner. Prepare for Invision Community 5 We have added a new information dashboard to the AdminCP so you can review the impact of the upgrade and ensure the PHP and MySQL versions are suitable. Of course, our Invision Community Cloud customers need not worry about this as we take care of it for you. You can also see impacting items you may want to know, such as deprecated and removed features that your community currently has enabled. This dashboard is a great starting point for evaluating your upgrade when the time comes. SEO Improvements We regularly review SEO best practices to ensure that your community presents itself in the best way to search engine bots and spiders. This update comes in two parts; the first is a new crawler setting to reduce links on the page for guests and search engine bots. This new feature removes hyperlinks around dates in comment feeds and removes the sharer menu item that shows the sharing box. These links dominate the crawl budget for little value, leaving little time for crawlers to work their way deeper into your content. The second SEO-focused feature is the permalinks to specific comments throughout the community. Currently, the permalinks point to a content handler (do=findComment&comment=123) that locates the correct page number and then issues a 301 redirect to the correct page (topics/1-topic-title/page/2/#comment-123). While 301 redirects are not a problem for search engines, and it's been a long time since a 301 redirect incurred any SEO penalty, the permalink is in a different format to the actual comment URL, which is handled via a fragment. Putting aside search engine optimization for a moment, working to eliminate a lot of redirects positively impacts performance. The new permalink is simply the actual link using a fragment to locate the post in the browser's viewport. This removes the need for a 301 redirect and reduces any search engine confusion over the permalinks canonical URL. Of course, the page number may change if topics are merged or many posts deleted, and we have some client scripting magic to handle that eventuality. It's an exciting time here at Invision Community with a brand new version in development and several new features for our stable product line. Let us know if you have any questions in the comments. View full blog entry

Looks great 🙂

If anyone is using V5 for their production site, or a public test site, drop the link below!

Looks brilliant!

I'll need to check. AWS forked ElasticSearch and it's been a bit muddy since then as they have both diverged quite a lot.

I need to do something with that font file. I'll add it to my list. Ideally it'd be added to the resources area anyway.