Emediate

Another vote here.

Definitely some merit to this idea. We are implementing AI in so many places now and so far, it's only helped productivity and/or workflows. Hopefull this is on the radar and roadmap for Invision before other platforms get the jump on us.

I'm at a loss here. Our developer says there is a problem with Redis enabled. Our hosts have looked into it and posted here, seeking support for a Redis problem. Really not sure what else we can do?

@Marc - any update please? We need Redis, however when enabled, it breaks other functionality as outlined above. Is there an issue with Redis and Invision? Do we need to do something on our end to resolve this? We're stuck here for nearly 1 month since this was posted here.

@GoHosting mentioned above, they needed to enable this to solve another prior problem. But this option is not working as expected.

THanks Marc. Hopefully it doesn't take too long as our unapproved topic and post counts continue to rise!

Is there a different way to go about getting some assistance with this? 3 people have requested help now, the owner of the site/license (me), the developer, and the hosts.

@Matt / @Marc any possible further suggestions on this please?We're all a bit stuck on this one.

Could you expand on this please? Again, with a signficant amount of data being sent through Sendgrid, our deliverability has been flawless (with the right setup of course) - how would PostMark have "better" deliverability? We just to make sure we are not missing something.

Is there a reason PostMark is recommended over Sendgrid? We use Sendgrid across our company in multiple instances (not just forums). I noticed its deprecated, even though it has remained on our install even after upgrading (thanks). But is there a particular reason we should be investigating PostMark instead?

These errors have started popping up repeatedley. Hosts have asked me to raise it with Invision as they don't have an answer. Invision 4.7.20 Database Version 10.11.11-MariaDB Cache Engine: Redis PHP Version 8.1.31 Introducing Redis was the most recent change. And by concidence, we switched off Elasticsearch and then switched it back on again - these two things happened around the same time these errors started appearing.

So this is incorrect then? Becasue that caught my attention this morning and would 100% stop us from upgrading to v5.

Installed 4.7 with no problems. Clearly 5 isn’t quite ready (acknowledging it is Beta). Feel free to move my thread. It was more for your benefit than mine. Did that three times, and nothing showing in the server logs unfortunatlely. I don’t want to be a beta tester. I’ve run with 4.7 now.

Fresh install, clean server and db. Failed more than once at the same point. PHP 8.2

I set up notifications already.