Consent banner keeps popping up

@rogierlankhorst @aahulsebos

One of the users who still has the problem sent me their cookie list. What I see is that all complianz_ and cmplz_ collies show up for the / path, except for complianz_policy_id. This shows up with the value of 15 (the current) for the / path, and the value 14 for the /nl/ path. I suspect this causes a conflict whereby the value is checked for the /nl/ path, but stored for / causing the consent popups being triggered on every page.

In my browser (which does not have the problem at this time) there is no cookie with the /nl/ path.

So, my guess is that there is a conflict between these cookies. This probably is an interaction between the WPML paths and Complianz. Note that when you first arrive on the site the path is /, but if you click a link to the home page the path becomes /nl/. I would expect the policy to be stored at the root level, not at the language level unless you have a reason to do so.

@marketingnexuzhealth, the different paths are the problem here. In your current version this path won’t get set anymore, so new users won’t have this problem. To resolve the issue for users with older cookies with a path still in the browser, I have created a branch which updates the cookie policy ID, and clears the Complianz cookies regardless of path for all users with a previous cookie policy ID.

If you install this branch, the issue should go away for your users. After the cookies have been cleared each user can consent again, and the issue should be gone.

https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/clear-wrong-path-cookies

Ok, I will try that later today.

Strange thing is that the issue has not shown up on previous updates of the policy, all which were executed well after WPML was activated (in fact, WPML was installed and activated well before I added Complianz).

I will keep you updated on the results.

Quick question though: does this keep all my settings & do I keep this version afterwards?

@rogierlankhorst I now get a reported error in the Complianz settings screen:

Uncaught_ReferenceError:_cmplzClearAllComplianzCookies_is_not_defined op regel 2 van https://nexuzhealth_com/wp-includes/js/jquery/jquery_min_js

But at least one user has now reported that the issue is resolved.

However the shortcode [cmplz-manage-consent] no longer seems to work.

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

I’m sorry, the minification didn’t run on the file. I regenerated the .js file, can you re-install the zip file?

This fixed the shortcode not working, but still the error is reported on the Complianz settings screen, probably because it still is in the logs.

@marketingnexuzhealth If you refresh your homepage when logged in, the error should clear from the dashboard.

Yes, that works. All seems to be OK now. Thank you for the swift solution.

Will you be merging this into the main branch? I have no way of knowing if/when all my users have revisited the site so that the cookie issue is resolved.

Thanks,

Thomas

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

Hi @aahulsebos @rogierlankhorst!

I′ve got the same problem, but only on mobile devices. It works fine on iMac and Windows Laptop in Safari, Firefox, Chrome and Edge. But on mobile devices the cookie banner is popping up everytime I open one of the pages of my website, even if If accepted several times.

What can I do to fix it?

@juliablaukontor can you post your domain? As your issue is limited to mobile this is a different issue. Possibly a javascript error caused by your theme.

@marketingnexuzhealth yes, this this will get merged into master. Please check the changelog before upgrading to make sure it’s merged.

@rogierlankhorst & @aahulsebos I have the same problem as above mentioned in Chrome concerning https://minitransat.fr/fr/ and https://minitransat.fr/en/.
In the cookies list (inspector->application) here is what I had:

name value
complianz_consent_status allow
complianz_policy_id 14
complianz_consent_status dismiss
complianz_policy_id 14

I had them twice and what helped was to clean manually the cookies and to reload the page. But we cannot ask users to clean their cookies manually. It should not be possible to create twice the cookies needed for the Complianz.

@flogr, this multilanguage specific issue has been fixed in 4.9.2, installing the branche above will clear these cookies for existing users as well.

This branch will get merged in one of the coming releases.

@rogierlankhorst Could you post here when the branch is merged into main? That way I get a notification when I can switch back to the main branch.