• Resolved albridi

    (@albridi)


    Hi there ?? !

    I have a nested WordPress installation to have a WooCommerce store separate from the main site, but within the same domain. I mean: https://www.blabla.com/shop, where Blabla and shop are two WordPress installations.

    The problem is that if a user enters the store directly, and I only have Complianz installed in the main installation (Blabla), the site does not comply with GDPR because he would never see the Cookies banner. So I installed Complianz on both installations, but this is causing strange behavior from the plugin. On the main site, it remembers the settings, but not on the store site. On the store site, the banner fires over and over… sometimes. Sometimes it is the opposite. The main site activates the banner several times and the store remembers the settings.

    Also, I installed the “Advanced noCaptcha & invisible Captcha” plugin and the comments store form shows a mess until I disable Complianz. If I disable Complianz, the form displays the reCaptcha fine.

    How can I fix this?

    Thanks in advance.

    Regards.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    The site in the /shop url will set the cookies in the /shop path, in your case you’d want it on the root.

    Please follow these instructions to achieve this:

    https://complianz.io/set-cookies-on-root-domain-mu-plugin/

    Thread Starter albridi

    (@albridi)

    Hi Rogier, thanks for supporting ?? !

    I followed the instructions and it worked on localhost, but not on the live site, and I’m pretty sure I did it the same way.

    What could be wrong?

    Thanks in advance.

    Regards.

    Thread Starter albridi

    (@albridi)

    By the way, regarding how “Advanced noCaptcha & invisible Captcha” is displayed after activating Complianz… will the mu-plugin also solve this issue?

    Greetings.

    Thread Starter albridi

    (@albridi)

    I have to correct myself. I’ve checked it today and the mu-plugin approach doesn’t work at all on my localhost install, and neither on the live site :(.

    Any other tips to fix this?

    Regards.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @albridi,

    Recaptcha placeholder
    This depends a bit on where ReCaptcha is used, sometimes the placeholder might appear slightly off. If you implement consent for Advanced NoCaptcha & Invisible Captcha as described in this article, this will look much better: https://complianz.io/how-to-implement-recaptcha-and-consent-for-ninja-forms/

    Consent cookies on root domain
    Strange one, could you confirm that this PHP file has been uploaded to the folder /wp-content/mu-plugins/?

    Perhaps you could provide an URL to the site in question so we can look into the behavior? You can reach out to us by email on support(at)complianz.io if you’d rather not share it publicly.

    Kind regards,
    Jarno

    Thread Starter albridi

    (@albridi)

    Hi @jarnovos thanks for supporting ?? !

    Regarding the placeholder for reCaptcha, now it seems to look ok after installing a plugin that adds a consent check box. It looks that it fixed itself ?? . The mess of the WordPress comments form is gone for now. That thing (the WordPress comment form) is awful and unfriendly for responsive design.

    Yes I can confirm that I have created the mu-plugins subfolder in the wp-content folder of the first WordPress of the two nested installations. That is: domain folder -> wp-content -> mu-plugins. I think it’s right because I can see it on the plugins dashboard under must-use. And I copied and pasted the code that you supply in the force-cookies-on-root.php file that is inside the mu-plugins folder.

    Sure I’ll send you the URL by email to your attention, I really appreciate it because this site is still under development. Thanks for this ?? .

    Kind regards.

    Plugin Author Aert Hulsebos

    (@aahulsebos)

    Is referred to mail. Any updates will be shared.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Problem with WordPress nested installation’ is closed to new replies.