Consent banner keeps popping up

@rogierlankhorst Thank you for your work! Have a nice day!

@marketingnexuzhealth This branche has been merged into 4.9.6, and is now released.

@rogierlankhorst I upgraded to 4.9.6 and unfortunately the problem has reappeared for the same users who had the problem before. I will try to revert back to the special branch you created.

I just asked to see what cookies they have on their computer and, again, they have a cookie complianz_policy_id on the /nl/ path with an older value. Other than the twocomplianz_policy_id cookies, they have no other cookies for the site, so the acceptance is not getting registered at all.

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

I’m having this issue also. I don’t have a live site yet as I’m developing locally, but it is really annoying that every page load requires to accept again.

I did notice that the “accept” creates complianz_ cookies with “path” equal to the page that the acceptance was given, rather than just “/” which would accept for the whole site.

This seems to be the main cause of the issue on my end as these extra cookies conflict with the ones set on the homepage and then the banner pops up again.

@marketingnexuzhealth

As of 4.9.6, a fix for the creation of multiple cmplz_policy_id cookies is implemented. A quick fix for users who have an “extra cookie” is to make a temporary change in the Wizard.

If you set “This website uses cookies” to “No” (Wizard > Cookies > Integrations) and click Save, this will increase the cmplz_policy_id so that the old cookie is not used anymore. You can now revert the changes and set “This website uses cookies” back to “Yes.”

Hope this helps,
Jarno

@hades200082

As this seems to be a different issue than the one described in this topic, could you create a separate topic so we can provide further assistance?

Thanks,
Jarno

I have managed to reproduce the problem in a systematic way and in any browser, even incognito, and solved it.

This happens because we have the site implemented in a sub-directory of the main web.

If I delete my main-site cookies, the repetitive requests stop in the sub-directorie’s site and, as soon as I put them back, the banner returns with every page refresh. The order of access to the two sites does not have any influence and it only happens in the sub-directorie’s site.

I solved it by implementing the hook force-empty-cookie-path.php via a mu_plugin (Must Use), but forcing the sub-directorie’s path; i.e return ‘/mysubdirectory’;.

<?php
/* Force consent cookies on the root or, to choose a subfolder 
* Add subfolder between '' on line 6 e.g. /mysubdirectory/
*/
function my_cookie_path($path) {
    return '/mysubdirectory';
}
add_filter( 'cmplz_cookie_path', 'my_cookie_path'); 

• This reply was modified 3 years, 4 months ago by . Reason: corrected /mysubdirectory
• This reply was modified 3 years, 4 months ago by . Reason: added code

In multisite environments, the 5.2 release prefixes the main site cookies with ‘rt’, which should resolve the issue.

If these are separate setups, your fix is a good solution.

The problem is that browsers have issues with the same cookies on root and sub directory.

Thanks @rogierlankhors. Mine is not a WP multisite installation, but simply 2 Complianz installations, in the root and subdirectory.

With regards to my above stagtement

I solved it by implementing the hook force-empty-cookie-path.php via a mu_plugin…

sorry, thought I had fixed it, but what happend was that I had not reproduced the problem correctly.

Now I have realized that it still fails. Basically, once you set the sub-domain cookies it forces the root site to set the cookies again, and from then on the banner ALWAYS repeats on the sub-domains site. If set first the root cookies and then the sub’s ones, but dont’t refresh the root cookies, the the sub’s banner works correctly

This is no WP multisite intallation, but even though I tested the today’d releases of Complianz 5.2.0 and 5.2.1, but none solved the problem.

Has anybody a similar setup, but fixed it?

In another tread I was told that my solution is valid for sites that have single Complianz installation in a sub-directory, but our case having another Complianz in the root’s site, might not work, because of the way browsers handle cookies.

So, I think there seems to be easy solution for this; either use another cookie controll software, to avoid colsions, or migrate the web to it’s own domain.

Hi @akleines2,

I would recommend opening a new thread for your specific situation, as this will increase the visibility of your question. Also, some issues look very similar to each other but might have completely different causes.

Kind regards,
Jarno