Works with cache plugins?

Hi Metuza.

Thank you for your interest on our plugin.

I don’t see why it would not work with cached websites.

Let me know if something doesn’t work as expected so I can further investigate.

WP Fastest Cache unfortunately caches the site with or without the Google Analytic Script Codes served with an if function to the header. This way it can happen that people trigger cookies they didn’t give permission to. -.- Or is wp_header not the place where I should put the scripts?

Thank you for testing this out.

I need to think about what the solution for this would be. I’ll open an issue on github.

Thank you both

Hi,

Just to let you know that the Consent Banner “sticks” when using WP Super Cache.

I have tested it with WP Super Cache deactivated (and cleared cookies both times) and it works fine when deactivated.

Maybe the “I Agree” button can clear cache and reload the page?

Thanks for a great plugin though!

Lee

From what I could see from WP Super Cache, there’s no way around it.

https://www.ads-software.com/plugins/wp-super-cache/#faq

Looks like this caching kills any type of dynamic solution that is not javascript based.
That’s why the privacy bar is still showing, or the reconsent takeover is still showing even after agreeing to the terms.

I still don’t know what our options here are. I will update the issue on GitHub and maybe someone can help us over there.

I belive that the only way around the use of cache plugins is the use of ajax. I have just done a popup login/register plugin for my site and first i got nonce problems then i got cookie problems and at the end redirect to my account page problems.

I had to rebuild the plugin and make it 99% ajax controlled to make sure nonce, cookies and other functionality was not cached.

Brgds
Rune

I proposed a solution for this on GitHub. I tested it with WP Super Cache enabled and it seems to be working as expected. Can anyone else test this before I release the new version?

You can test it by downloading the beta version here: https://github.com/trewknowledge/GDPR/archive/1.1.4-beta-1.zip

Let me know if you find anything that is still not working. That way I can have it fixed and launch it on Monday.

Well… Since there was no feedback on this, I released version 1.1.4 with the additions I did for working with caching plugins. Not 100% sure it works yet but it seems like it.

If you still have issues with it, feel free to open a new support ticket.

There are some caching plugins that can handle separate versions of the pages depending on a cookie.

E.x.: If there is a cookie that has the content “Y” (user accepted) the caching plugin will fetch a version of the page containing the analytics code. Otherwise (cookie not set or has the content “N” for declined) the version without the analytics code will be delivered.

I know two caching that can handle this: Comet Cache & Swift Performance (maybe only the Pro versions can).

That’s good to know.
But is still a lot to ask from people to know how to configure all this.

Well… Since the update that might have fixed the caching situation, I haven’t heard any more complaints. I’m going to consider that good news ??

Hi @fclaussen,

I see there is a cookie set when the user clicks on the accept button:
gdpr%5Bprivacy_bar%5D = 1

So this solution should work (if the name ‘gdpr%5Bprivacy_bar%5D’ is always the same) with Comet Cache Pro depending on a cookie value:
https://cometcache.com/kb-article/introduction-to-dynamic-version-salts/

I′ll try Swift Performance next…