Aert Hulsebos

Hi @nicmare,

These assets are loaded during the cookie scan, which is currently running (?complianz_scan). This might take a while, let me know when it’s finished, and the assets are still loaded or when you think it might be taking to long.

regards Aert

Hi @ryandesigned,

I can’t reproduce the exact variables of the video. What I can see is that on my end at least the cookies (only 2 in our case) work as expected and give the correct values.

You can also check the console – messages for logs by Complianz, Rolex and Adobe. Which seems to suggest the code is correct.

What I do see, is on a reload on an iFrame page, as seen in the video and reproduced on our end is an error on setting:

cmplz_set_rlx_cookie(false);
cmplz_rolex_enabled = false;

i think this is due to the script being initialised faster than the iFrame is found by javascript. We can try waiting for the iFrame to load with an adjustment I just pushed to https://github.com/Really-Simple-Plugins/complianz-integrations/blob/master/rolex-mu-plugin/rolex/script.js

regards Aert

Hi @ryandesigned,

Could you replace the script.js with this version? https://github.com/Really-Simple-Plugins/complianz-integrations/blob/master/rolex-mu-plugin/rolex/script.js

Let’s see if this helps,

regards Aert

Hi @mesw,

Could you post the exact call, because 0.15sec doesn’t sound like a cookie scan and I can’t reproduce it at my end,

regards Aert

Hi @wpwebman,

This: “I’ve found that without consent Matomo cookies seem to be blocked initially but after a few clicks around the website Matomo cookies are being added for the website”

sounds like it’s working as you want it to? So no cookieless before consent, cookies after consent.

You only need to check if cookieless tracking starts prior to consent, which probably with a URL parameter. Do you have a website I can check?

regards Aert

• This reply was modified 1 year, 2 months ago by Aert Hulsebos. Reason: spelling

Hi @estudiojan,

https://elhuertico.es/?nocache works, so clearing WPFC should help.

regards Aert

Hi @mkarena,

I think I figured out that everytime ‘dimplex’ is in the URL, Complianz is disabled.

This would only be possible if there was a MU plugin, or if a page like /dimplex/ had Comlpianz disabled – and URLs which then contained ‘dimplex’ were also disabled.

If you don’t know which page, or MU plugin you could verify by duplicating a page, but changing the URL without dimplex to know for sure.

regards Aert

Hi @estudiojan,

There’s a CSS rule:

div[data-nosnippet] {
display: none !important;
}

in /wp-content/themes/ochahouse/assets/css/default.css.

Because they use ‘!important’ we can’t override it, and I’m not sure why they would do this. You could use a child theme with the same default.css, but remove the line. Or remove it directly,

regards Aert

Hi @mkarena,

Do you explicitly block the banner on a specific page, either on the page with the checkbox or MU plugin?

If so, does the page where you block the banner and other pages have something in common in the URL?

If you could provide examples, I might have a better understanding what’s happening. regards Aert

Hi @lilateamfiveinc, could you try below version of the plugin?

https://we.tl/t-4URJXOySe3

Let me know, thanks!

Hi @wbweb2019,

Most likely because you have a GTM/GA plugin installed like GTM4WP or Google Site Kit. In these plugin you can configure GTM.

If you want to use GTM with Complianz, make sure you select Google Tag Manager under Consent – Statistics in the wizard, so Complianz will fire the appropriate custom events.

regards Aert

Hi @cwalterpas-solutionsch,

The plugin is default in English, the rest are translations. These are the 2 Complianz blocks available: https://snipboard.io/VAtzWO.jpg

I expect the default language is German, with an English translation? Is this page situated on a URL e.g. yourdomain.com/en/cookie-policy? This is the preferred option.

regards Aert

Hi @ryandesigned,

For a bit more detail, are we talking about: <script src="//assets.adobedtm.com/7e3b3fa0902e/7ba12da1470f/launch-5de25****d80.min.js"></script>

As I understand it this should be added on HTML pages only, by the user. Complianz doesn’t enqueue the script, just handles its release on HTML, and Rolex uses the set Rolex consent cookie to handle it in the iFrame.

So I would expect the code is implemented site-wide, but must be removed from iFrame pages.

Is this correct, or didn’t I understand the question? regards Aert

• This reply was modified 1 year, 3 months ago by Aert Hulsebos.

Hi @johnmandarine,

The reason are the hyperlinks on the banner below. I assume you’re using the same page for both the Privacy Statement and Terms & Conditions?

If so, we could remove one to make it a bit better;

a.cmplz-link.privacy-statement {
    display: none;
}

Let me know if we need to something afterward, regards Aert

Hi @lilateamfiveinc,

This part of the Divi Integration under Complianz – Integrations. Not the error of course, but integrating with the map.

Disabling will remove this error, but might cause an issue with the map, if not already.

Could you post your URL, because I would be interested in seeing if pausing Nitropack would help, or if there’s an issue with Google Maps.

Let me know, regards Aert