Dll

Put some extra information in the failed login messaging perhaps? Or just on the login page. Make your contact options very visible and so on. If someone has been a member of a community a long time and come back after a while, you can assume they'll be fairly motivated to get logged in, so I don't suppose an extra step of sending an email will put too many off? Alternatively, (as we've found at times on our community), people will start a fresh account if they can't login and will probably then use that to ask about their old one. The change really isn't the end of the world, although we did spend 12 months notifying people in varying ways before making the change.

I think with the amount of time you've wasted on this community over the last couple of years moaning about the change of login, you could have probably written a hand written letter to every one of your members advising them of the change.

Does this means that using pages for things like ads.txt no longer works?

They maybe need to look again then, as it looks a bit ridiculous at monitor widths above 1800px (which isn’t that wide).

@Adlago, you appear to be misunderstanding how the caching works. It's not a local cache on a users machine, it's caching the html for the block server side, so the backend isn't generating it each visit. If you cache it for 1 hour, it'll retrieve the html from that cache for 1 hour, and then check again for an update the first load after that. Once it's done that, it'll cache it again for an hour. So, setting it for one hour will make it faster across the hour than setting it for 5 minutes.

Nice to see Invision finally get over their apparent pathological dislike of all things cloudflare and embrace its obvious advantages

B2 maybe good, but I'd possibly suggest you're storing up a whole load of hassle (support wise) for yourselves by saying any other compatible s3 service is ok, as some of them definitely aren't. Cloudflare R2 caused us some issues on 4.7.19 with caching and the IPS system could never delete from it properly. In the past google cloud buckets were problematic as well.

When you say they can be used right now, I assume you mean just on V5?

Certainly agree with this. We've been self-hosted and cloud-hosted (currently back to self-hosted for the time being at least). We're comfortable managing servers etc, but the removal of the stress and time of doing the nuts and bolts of that for our community was a definite plus when we were cloud based. I don't think the comparison in price between a VPS or even dedicated server at some random host vs a SAAS product is ever a particularly fair one.

Thanks, you're correct. Re-installing that solved it.

Hi, since yesterday we're seeing this error when trying to access reports: SELECT * FROM `reportmsg_messages` ORDER BY msg_position Table '[dbname].reportmsg_messages' doesn't exist We've not made any manual database changes or anything, so are quite concerned as to what is happening and what may have caused it.

Matt, I appreciate the reply. We have been customers for the best part of 20 years now, and although I have, at times, been vocal in voicing concerns (cloud vs self-hosted not being one of them btw), I'm sorry to hear that the negativity around the cloud is continuing to create hassle for you and the team. It's a lesson learned that things may be going on out of sight which affect the things we do see, so apologies if my comments in this thread have added to that.

The reason we found for this was that we were using an 's3 compatible' storage bucket for the theme files, js etc (Cloudflare R2). We were 'mirroring' it from an S3 bucket for better compatibility (so we thought!) and it was fine up to the update but I assume something changed in the way storage buckets are handled during the update. The only way we found to fix was to switch back to (the recommended) actual Amazon S3 storage for them.

Ahrefs is a brilliant example - yes they have tiers, but they also communicate about them properly. They also have impeccable timing, as right now they are beta testing a new ai content feature and they're properly transparent about it, in that they're saying that 'at the moment' everyone has access while it's a beta feature, but in time it will be a paid for addon. Everyone then knows where they stand. As for the 'them vs us' - the sad thing in that the biggest cause of that isn't the change itself - most people get how different products and pricing tiers work. It's the way it has been handled and communicated from the off. It's become a problem of Invision's own making, which is a shame for all concerned, especially as the lessons just never seem to be learned.

You're of course welcome to your opinion, but have a read of the posts in this thread, is there confusion due to a lack of transparency or not?