Manage consent on Cookie Policy and Legal Hub doesn’t work

Hi @marco74it,

Have you made restrictions to the Rest-API. Not necessarily the last few days. The latest update from Complianz uses the Rest API to gather settings.

Most likely this is in a security plugin, and you could try to exclude Complianz so it can use the Rest-API,

regards Aert

When I load the REST API url that supplies the manage consent html I get the following error:

{“code”:”rest_cannot_access”,”message”:”DRA: Only authenticated users can access the REST API.”,”data”:{“status”:401}}

This means you have limited the entire REST API to logged in users only. Complianz uses the REST API for the consent html page.

If you remove this limitation the issue should be resolved.

Rogier: thanks for your answer. What you experienced was due to a test.
WP Security plugin has a setting that can be flagged / unflagged (“Check this if you want to stop REST API access for non-logged in requests”).
I flagged it for few minutes today to see if the setting change was affecting complianz.io behavior. It’s now unflagged as it has always been. If you run your test again you will see a different result.

Original plugin problem still persists.

Addon info: website is using Disable REST API plugin. All sites plugin including complianz.io are whitelisted there.
I am not aware of any other setting not I have other plugins limiting REST API.
After the white listening activity I see a kind of improvement: the manage consent settings are now visible on both the cookie policy page as well as the legal hub page.

But .. the Cookie bar pops up on each and every page of the site again and again .. regardless of the fact that users are clicking Accept All.

I’d really appreciate an help as my next option is to remove the plugin. I am really getting customers reports on this ..

• This reply was modified 3 years, 10 months ago by marco74it.

@marco74it When checking the .js file on your site, it is not exactly the file that is in the current plugin.

I can see you are on 4.9.1, but the version is stripped from the .js URL. I think your server is caching the .js file. This means that even if you don’t have any cache active, and your browser is cleared, your server will keep serving the old .js file. I suspect this is the issue currently.

If you have a “clear cache” option on your hosting environment, please try clearing that.

If you have the option to leave the version at the end of the URL, please do so, as that ensures the correct file to be loaded.

Hello,

thanks. Cache cleaned and situation improved. I am now testing with different browsers and devices.
Do you mind to explain (or to point to an article that does it) how you checked the version ? It may useful for further checks.

M

I just completed a full round of tests and .. unfortunately no changes … Tried with few different browsers in incognito mode ..
When I open the site home page the cookie banners pops up. After clicking on accepting all cookies, while browsing the site, the banner shows up on each and every page I click on ..

Hi @marco74it,

To see if the correct file is loaded, I check for some changes. For example, In the latest file, the cookie path is set like this:
path:cmplzGetCookiePath()

In the previous version it was
path:”/”+cmplzGetCookiePath()

I just checked your site again in a private window. The issue seems to have been resolved by clearing those caches. If you still experience issues, please clear your browser cache completely.

As your server seems to strip the version from the .js url (complianz.min.js instead of complianz.min.js?ver=4.9.2) the new file is not forced after the update. The new file is now served by the server, but may still be cached by the browser. If you check in a private window you should see it work.

Hello Rogier,

I tried clearing caches (on all browsers and devices I have) as well as on the server level. Clearing went well. Also asked hosting support to confirm it.

Unfortunately the problem with the cookie banner still persist.

This morning I had to disable the plugin as it was really impacting usability.
I will try again to do some tests / cache checking this evening but, I hope, you also have other suggestions.

@marco74it,

I would start with ensuring that the plugin version is appended to the script URL’s. That will ensure the new file from being loaded.

When I checked yesterday, it worked fine when the new complianz.js file was loaded. That time when I could reproduce the issue, I could see the old file was still loaded.

If you still have this issue, I can try if I can reproduce the issue on your site, or on a staging site if you can set that up. Then I can double check the file, and the settings.

I would start with ensuring that the plugin version is appended to the script URL’s. That will ensure the new file from being loaded.

How can I do ?

If you still have this issue, I can try if I can reproduce the issue on your site, or on a staging site if you can set that up. Then I can double check the file, and the settings.

How can we practically organize it ?

At the moment the plugin is disabled. I could not find an easy way to block the cookie banner without disabling the plugin fully.

Hi @marco74it,

To do this,

You can enable safe mode under Complianz -> Settings; and add some CSS to hide the banner if necessary;

#cc-window {display:none;}

You can try disabling optimizations plugins to see if this helps, including caching and minification for example.

regards Aert

Thanks, I will take actions later today/

When it come to the optimization plugin, I can try t disable or can I whitelist scripts or css or toher elements. May you let me know exact script name(s) that I need to exclude from optimization to avoid the issue ?

On the optimizations plugin: plugin has always been there and complianz used to work properly with it. Something has changed (not on the optimization plugin side) days ago

Some more information.

I am using SG Optimizer as plugin to optimize WP performances. It’s a plugin developed by Siteground (the hosting provider).

I analysed the site with GTMetrix and found this script (I guess this is the one you were referring to) https://www.artemperature.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js

As per the plugin configuration possibilities, I could do the following tests:
1. Exclude URLs from being cached – I tried to exclude the JS url (https://www.artemperature.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js/)
2. Exclude URLs from HTML Minification – I tried to exclude the JS url (https://www.artemperature.com/wp-content/plugins/complianz-gdpr/assets/js/complianz.min.js/)
3. Defer Render-blocking JS – I excluded from the deferring the following: complianz.min.js, cokkieconsent.js and postscribe.min.js
4. I disable the option the option to remove versions from query string
5. I disabled Minify JavaScript files
6. I disabled Combine JavaScript files

I also tried a randomic combination of the above. For all test cases I clean the site cache as well the browser one and tested using incognito mode.

None of the above worked. The problem is still there.

I just enabled Safe Mode so you can maybe do some checks as well.

Pls let me know what you think as I really feel out of options.

@marco74it,

I just checked again in several browsers: IE, Safari, Chrome. The issue is resolved in all browsers.

The fact that it’s working on all browsers I tested with means your issue is caused by caching in your browser. If you close all browser windows, clear all cookies and history, then try again, it should be resolved. Please also try a private window. Perhaps also try a different browser than the one you’re using normally.