Plugin integration with CookieYes defined cookies

Explaining it another way round:

If I am a dev of a plugin, and I want to put a cookie ‘abc’, do I need to check the CookieYes cookies to know if I have the right to set the cookie?
And if yes, how can I check the cookie I want to check, supposing that CookieYes is properly setup for my cookie ‘abc’, shall I check the category of CookieYes or is the value of the cookie present in some way?

I didn’t find my defined cookie consent state present in any newly created cookie that CookieYes would have created.
I just see that the category of my ‘abc’ cookie I have added to CookieYes changes when I change the setting of that category. So shall I check that cookie category to know if I have the right to set the cookie, is this the way to go?

Hi @doolyo,

Greeting from Webtoffee!

Our GDPR Cookie Consent plugin works based on script blocking. In order to manage the cookies, the block requires to block the script that adds the cookies. As such the plugin require you to insert the script via the cookie categories(head/body script fields under the cookie category edit page).

Since it is not possible to move a script that is added via another plugin to ours, it won’t let you block the script. Our pro version plugin includes a filter that can block scripts from any plugin or theme directly without copying or deleting the original script.

You may please check out the plugin and you can contact the support in our site itself for assistance regarding set up.

Hello.

Thank you for your explanations.
I unerstand that the pro version of the plugin will allow more plugins to be blocked automatically with the “Script blocker” feature, is that correct?

This would not help as I need to be blocking cookies for plugins that are little personal plugins and which sets cookies on the website. I want them to be blocked/handled by the “GDPR Cookie Consent” plugin too. However I guess that this would need for each plugin an integration phase with your plugin, in a paid manner, is that correct too?

What I think is missing here is a “Universal Cookie Consent Standard” that you should be setting up with other Consent Manager plugins.
It would be very simple and would work this way. This is my first draft of this standard:

The Consent Manager plugin must set this cookie as soon as the page is loaded (it would be in the “Strictly Necessary” GDPR category, so no need of any user consent for this:
“consent_manager_exists”
With values:
– ‘0’ : The first time this cookie is set, it sets it to 0, for priority issues. It is NOT yet meaning that it exists (as the dev plugin might be accessed before the Consent Manager plugin and hence the cookie not set).
– ‘1’ : The subsequent times this cookie is read, and its value is ‘0’, it is set to ‘1’ by the Consent Manager, to tell that the Consent Manager exists. Plugin developers need to check this value of ‘1’ to know that the manager exists.
– Not existent: If this cookie does not exist or is set to ‘0’ during two consecutive page loads, then no Consent Manager exists for this website.
This will help plugin developers to know if they have to wait for user’s consent or not. If they see that this cookie exist, then they will wait for the “consent_manager_accepted” cookie to be set, and then check other Consent Manager standard cookies if he is allowed to set his cookie.

The Consent Manager plugin must set this cookie when the user consent is given (Any consent button is clicked, like Accept or Reject buttons), so that other plugins know the user has given his consent to some cookies or maybe none:
“consent_manager_accepted”
With values:
– ‘yes’ : The user gave his consent.
– ‘no’ or ‘null’ or Not existent: The user did not yet give his consent.

Then, each cookie that is setup in the Cookie List of your plugin (or any other), would add a new cookie that starts with the following:
“consent_manager_cookie_”
Then it would be followed by the name of the cookie.
With values:
– ‘yes’ : The related cookie is allowed to be set, with user’s consent verified
– ‘no’ : The related cookie is NOT allowed to be set by the plugin, user didn’t give his consent for that cookie
– ‘null’ or Not existent: The user did not yet decide for that related cookie
I.e. if there is a cookie called “wonderful_plugin_cookie” in my plugin, and I set it up in the Cookie List of your plugin, then once the user has enabled it in the category and accepted, we would have this:
“consent_manager_cookie_wonderful_plugin_cookie” = “yes”
Hence once the plugin sees this cookie and value, he can set the original “wonderful_plugin_cookie” cookie properly to its real value.

What about that, do you think you could setup such a standard to be defined, so that plugins creator would be able to follow it?
Of course, this standard would need to be using generic names like defined here, and not correlated to your plugin only. This is because if a user decides to change his Consent Manager plugin for e.g. “Cookie Notice”, then he will have nothing to change at all in his plugin.

The advantage of this standard is that it is really easy to implement on your side, and also on the side of the plugin developer, who will just need to do a plugin update that will just check the value of this “consent_manager_” cookie state before setting his cookie, as long as the “consent_manager_exists” cookie exists and equals “1”.
The only thing the plugin developer needs to add is a page load counter cookie, to be able to know if the “consent_manager_exists” set to ‘0’ is a counting thing or not. If after his counting cookie like e.g. “wonderful_plugin_count” set first at 0, and is then set to 1 by himself, and he sees that the “consent_manager_exists” is still not set to ‘1’, then the Consent Manager does not exist for sure, and he is allowed to set his cookie too (because maybe in his zone it is not required).

What do you think of such an implementation?
The advantage is that the burden of cookie implementation will not be on your side anymore and you would win TONS of hours of plugin integration development, whereas plugin developers would implement that in a few hours only on their side, with an update of their plugin, and without any support need from you, winning time for him and for you too.

Regards.

Hi @doolyo,

Apologies for the delay in response.

Your proposal seems very interesting and promising. While it indeed lessens our burden in the prospect of development, getting all the plugin developers to make their plugins listen to this one plugin’s consent cookie is a difficult and nearly impossible task.

WordPress is trying to get such integration within itself natively. Let’s hope someday this would be available and we can all integrate compliance easily.

Ok good thank you it is great to hear that wordpress is doing some native work to support this natively. Let’s hope it will become much easier.

Kind regards