Compatibility with the WeePie Cookie Allow plugin

As a temp solution for your users, if what you want is to simply only serve the cached version for pages when cookie: wpca_consent=1 you could tell your users to modify the file: PgaCache_Environment.php:

1. Go to line 754 – it should be blank
2. Add the line:

$rules .= " RewriteCond %{HTTP_COOKIE} wpca_consent=1 [NC]"

This would work for users who are behind an apache (or litespeed or other apache clone type) servers — ie., htaccess file — (which is likely 85% of them) and are using disk:enhanced mode — likely 95% of them are. It would be pretty easy to do the same for nginx and disk:basic but i am too lazy to bother to give you that code too.

Hi,

Thanks so much for thinking with us and your time and effort for this reply!

Hope W3TC Team will follow this up!

[ Signature deleted ]

I have discussed the feature of making groups, where one group of scripts is compulsory and the other is conditional. The team is going to work this out, but we’re not sure how, and mostly when it’ll be released.

Hi Weepie,
First of all, have you found a fixing concerning so-said compatibility issue?
Secondly, is your weepie plugin similar to what cookiebot or tarteaucitron.js ones do as far as explicite consent handling ? Is it able to dynamically identify all cookies interfering during our site navigation?
Thanks for your appreciated answer : )
CGC

Hi @gidomanders,

I was wondering if we could work towards a solution in order to make the W3TC plugin compatible with our plugin.

At the moment we have developed a solution together with WP Fastest Cache which also involves some extra .htaccess rules like @@fistfullofcrisco also suggested.

[moderated]

Thanks in advance and kind regards

• This reply was modified 6 years, 5 months ago by Andrew Nevins.

@weepie, You can share code using Pastebin, please stop asking people to email you.

Hi @anevins, Apologies, we were not aware of this. Kind regards

Hi @gidomanders,

Just to let you know.

Lately we have improved our plugin regarding caching compatibility by moving the PHP logic to the JavaScript. In short this means:

• The bar/box is now in-depended from the server: the JavaScript decides, based on the cookie values, to show/not show the bar/box
• The blocking/un-blocking of content in the HTML (scripts, iFrames, etc) is ‘prepared’ server-side, but the JavaScript decides again to block/un-block the content

This means that, also with cached pages, our WeePie Cookie Allow plugin should function well with the LiteSpeed Cache plugin.

The only thing is that the cache (I think) should be cleared when:
• a user saves one of the settings tabs of our plugin (because they can impact the frontend like colors, texts and cookie settings)
• a user activate/de-activate our plugin

For our customers who are using your plugin, would you be able to test our plugin compatibility or ask your developement team to take a look at it? If yes, we would be realy happy:)!

Thanks in advance and kind regards,
Team Weepie

@weepie thanks for letting us know! I will take a look at the plugin shortly.

To make your plugin compatible by clearing caches after settings were saved, you could just call w3tc_flush_all(). Or you could notify the user in WP Admin that it’s recommended to clear the caches to keep the user in charge. You could even copy the button from our notification when settings changed to make it easier.