Upon testing, it looks like this is a caching issue. I’m using Kinsta + Cloudlfare to cache the content pages where this plugin is running. Cache is disabled for logged-in users, which is why the error doesn’t show up then. Is there a workaround here that doesn’t involve disabling the cache entirely for content pages?
Does the plugin use a nonce or a token for validating requests? If so, what is the lifetime of that token? I’ll make sure the cache on the site matches that lifetime.
-
This reply was modified 11 months, 2 weeks ago by sahava.