Reply To: Weird plugin conflict after latest update

Yeah, that still smells like cache layer nonsense to me. I’ve had “plugin conflicts” that only showed up on cached pages and it wasn’t the plugin at all, it was some busted cached variant getting reused after the update. If you’ve only disabled 2 plugins, I wouldn’t assume much yet. Clear page cache, object cache, CDN cache if there is one, then hit the same URLs uncached and see if the error actually survives. Also worth checking if it’s tied to one template or block output. Random pages usually aren’t random — it’s often one query/widget/block getting cached and sprayed everywhere. If Redis or whatever’s in play is involved, I’d look there before I start playing plugin whack-a-mole.