Matt

I would imagine the silence is just a period of reflection and deep thought.

This. We cache widgets so we can't show the read/unread styling. It's been this way since 4.5 (2020).

It should already clear out Redis. If it doesn't, that's a bug. Although to be clear, it "clears" the Redis cache by changing the prefix used for all Redis keys. So you will still have a lot of data in Redis just after you cleared caches, but the Redis TTL will clear them out eventually because Invision Community will no longer ready/write to those specific keys. So if you spot lots of data still in Redis after hitting "Clear Caches" then that's not a bug. If you clear caches and Redis is still returning 'old' data to Invision Community directly, that is a bug.

It's in our back log. We'll get to it pretty soon though.

Redis is not a cache for the database in the literal sense. We use Redis as a cache for data that is otherwise stored in the database to allow us to retrieve it quickly, but it doesn't assist queries directly like that.

Just make sure all the files from /applications/forums/data/ are up to date on your server.

Yeah, I made a pretty sizeable mess of the release. The team had to rescue it while I was away from my desk.

During the build process, some of the line ending characters changed. It's safe to just keep using your custom.css when asked.

Excellent, glad to hear you got it resolved. 🙂

Now this is definitely on the roadmap. It's in the core framework, so just need to update Pages to use it.

How are you adding this HTML to the editor? Does your member group have permission to post HTML? All posts are cleaned to remove potentially breaking elements, but this is bypassed if you have permission to post HTML.

I think it'd be worth submitting a support request so we can make sure there's not an issue elsewhere.

There is an option when you upgrade to keep existing ranks, or use the new ranks. However, that information isn't much use to you right now. You can recreate the old system by re-setting up your old rank names and levels and disabling every achievement rule except the one for Comment/Reply and New Content Item. You won't need a recent back up, just one to show the previous names and rank levels.

I see you had your questions answered. 🙂 Let me know if you need anything else.

I think that's most likely the issue, so a rebuild after upgrading should fix it for you.

It loads instantly for me. No issues at all.

Best submit a ticket and we can take a look.

Unfortunately, this is not currently a feature.

It took about a weekend to rebuild this site, so that sounds about right.

There were a few bugs with the comment rule extension, which should be fixed in 4.6.4. It likely counted 1 topic as one content item and 1 post, rather than just 1 thing. So effectively 2 points per topic instead of 1 when rebuilding.

Submit a ticket. Somethings gone wrong®.

Manually awarded badges are not removed by a rebuild. It would also remember "7 days logged in". It depends on many factors, such as using traffic to run tasks versus cron. You could squeeze it through by running the specific task via cron every minute. Likewise, you could choose the "Run Now" option when viewing the background tasks and leave a browser window open churning through them. When you rebuild you ask the system to pick through every single data point again (comments, topics, members, reactions, etc). It's an intensive operation so it's not something you'd want to do regularly. In the future I may be able to have a rebuild specific rule option.

It's something we've thought about for a later version. The ability to essentially have one badge update for milestones. We have no immediate plans for this though.