Complianz Cookie Path is not taken into account

Hi,

we have Complianz plugin installed for some time – thanks for that great piece of work.

However, we’re running two WordPress installations:
domain.com
domain.com/path

Hence, we set COOKIEPATH and SITECOOKIEPATH in both installations wp-config.php files respectively:

define( ‘COOKIEPATH’, $_SERVER[‘HTTP_HOST’] . ‘/’ );
define( ‘SITECOOKIEPATH’, $_SERVER[‘HTTP_HOST’] . ‘/’ );

– and for the other –

define( ‘COOKIEPATH’, $_SERVER[‘HTTP_HOST’] . ‘/path’ );
define( ‘SITECOOKIEPATH’, $_SERVER[‘HTTP_HOST’] . ‘/path’ );

… which works, the Cookie paths are beging set correctly.

Still, it seems that Complianz does not take those paths into account. Or more precisely, they are set (we can see the paths in Chromes Cookie tab), yet each time we open the second installations frontend, we’re being asked again to accept cookies.

The issue only comes up when Cookies were accepted on one of the two installations first. Again, there are two Cookies with the same name and different Cookie paths present, yet they do not seem to be interpreted the right way as far as the Cookie banner is concerned. They seem to be ignored.

(We temporarily fixed it be just replacing one installations Cookie names for Complianz Cookies, e.g. setting complianz_consent_status to complianz_consent_status_root, cmplz_marketing to cmplz_marketing_root etc. – but that only manages not to show the banner over and over again, yet it does not save Cookie selection correctly.)

Could you please check wether the plugin is actually capable of supporting this right now? IMHO Cookie paths should be taken into account even when using just one installation, even though you won’t notice errors that quickly.

Thanks!

Warm regards
Erik