Matt

I am mock-agnostic, it isn't limited to people who pay our bills. Poor jokes aside, I meant no offence. Although tickers in general are fairly poor UI. v5 comes with an autoplaying carousel option which might be better.

Yes, unfortunately it was delayed. There was an issue with our GitHub integration which meant that when I went to build at around 3pm, nothing happened. It was fixed last night. It was also 1:30am my time. Built and waiting for it's time to shine.

Beta 10 is finally here Yes, we battled bravely through snow, ice, mince pies, festive men in red suits, New Year celebrations and a last minute issue with our build system yesterday to bring you Beta 10. All the fixes are in the release notes as usual. We do not expect many betas until the final release now. The feature set is locked, so we'll just be triaging bug reports a bit more to essential things. I'll aim to run through the bug tracker to close out fixed bugs. Let me know how you get on.

Changed Current Release to No

That's the plan! We're a-choppin'

We've mostly been eating mince pies. Through bitter experience, we know better than to make software releases around the holidays. More than one of us has spent Christmas Day fixing a crisis or patching a release. We want our staff to have some proper time away so we do not do anything beyond support between Christmas and New Year. Esther has been working through the bugs, but we're also working on an upgrade of a clone of our main site to prep for that later this month. I'll be finishing bug fixing and get another beta out this week. Internally, 5.0.0 is now "locked" except for bug fixes so we are on the run up to the final release. I wouldn't worry too much about the number of bugs, we don't always go back and say which are fixed, but many are.

I'd say that's about right. It doesn't cache full HTML page outputs. It really acts as a memory layer between the database and PHP. We put things in there that don't change very often and it saves a DB lookup.

I love this message. I hope it's going well so far.

Well, that's 8 minute of my life I'm not getting back. I'm also not able to sign up to the forum. 😅

Our Cloud platform uses Redis for data caching (data stores, temporary caches, etc) and CloudFlare for CDN caching (mostly for guests). This does not happen. We serve up a text/html page in full for each request. As mentioned above, our Cloud platform will use Cloudflare to serve this page to guests if a suitable cached version is found, but logged in members always get a normal page. Again, this not a feature. MySQL does have some short term query caching. We cannot really cache anything for logged in members or you would have issues with sessions, CSRF tokens, content on the page you can't see, etc, etc.

We want to do a club focused update post 5.0.0, so something like this is very possible.

This has been fixed for the next beta.

It's weird because the stats show roughly 50/50 between mobile and desktop usage for forums across our cloud network. I hope that v5 makes it easier for people to use their mobile device to interact with the forum.

We're pretty close to being ready for the final release. We just have a few things we need to do internally first but we're close.

We pay for storage, not transactions so it won't really affect costings. I'm not sure that switching to SQLite (at considerable cost) will actually make any tangible benefit in terms of speed.

The pricing has already been set. To upgrade to Invision Community 5, you will need to switch to the Classic license, and all the details of the costings are presented before you confirm the license switch. You cannot use the beta on your production site, but you can sign up for a v5 demo here: https://invisioncommunity.com/clubs/page/3-beta-information/

As long as you pass code web vitals, you’ll be fine. Also good luck running a large busy site on SQLite. 😀

I ran both tests again, and got this result. Yes, we do benchmark, but the claim about speed is based on using native lazy loading, removing loads of JS, moving assets into correct locations, the new CSS framework being smaller and the HTML structure being more compact.

Are you basing that opinion off screenshots from Adlago? He has spent years optimising his v4 installation to get the best PageSpeed score possible. I'm unsure how long he has spent with v5. In any case, a good portion of PageSpeed is down to the server, the use of CDN, etc. It's not just the software. Running the same test three times will give you three different scores, it's not an exact science. Likewise, running "grid" or "feed" view in v5 will result in lower performance scores because there's more images on the page; but I wouldn't just optimise for PageSpeed, actual humans use your community. In terms of "out of the box and running on the same hosting set up", here's our v4 compared to v5.

It really didn't.

As punishment, I will remove one random template hook point.

Changed Long ID to 5000040

Added an issue, but please remember to post bugs in the bug tracker. 🙂