Cache plugin seems to interfere with the functionality

If caching (W3 Total Cache) is enabled, the functionality is unreliable.

It’s hard to understand what is going on, but I noticed that the user can’t accept the cookies: clicking on Accept reloads the page, but the cookie banner is still there and the script tag has not been injected into the page (I have added a console.log just to check and it is not showing up). The wpgdprc-consent cookie is set to accept, but it’s as if the plugin is not reading it at all.

If I disable the caching plugin, the cookie acceptance starts working again.

But here is the funny thing: if after having accepted the cookies I enable the caching plugin again, I am no longer presented with the cookie notice even if I clear the cookies and reload. Actually, even if I change browser, open a private tab, whatever.

For example, in the current stage of the cache, this page doesn’t ask for the cookie. All the others do.

It looks like the cookie setting is somehow cached per-page in the backend and that changes how the pages are served regardless of what the consent cookie actually says. In fact, if I navigate away from that page and onto another, the cookie setting is lost and it starts asking for it again.

Am I the only one with this kind of problem?

Otherwise this is a lovely plugin. If only this caching problem gets solved…

I will leave the cache on for now so you can debug this, hope it doesn’t take you too long (I am aware today is a Sunday).

Thanks for anyone’s help with this.

Note: to debug, make sure you see this message in the console “gdpr plugin loaded the script”. That’s when you know the plugin has … yep, loaded the script.

• This topic was modified 8 years ago by Emanuele Feliziani. Reason: Added a note for debugging

The page I need help with: [log in to see the link]