Hello @dillhausen ,
Thank you for reaching out.
This is an uncommon issue. Could you please share a video of your configuration and send a list of your active plugins? This will help us understand the ongoing issue.
Thanks in advance and looking forward to hearing from you.
Hi @antoiub ,
thank you very much for looking into this. I didn’t know how to make a video, so I made screenshots instead. They are uploaded to Google drive here (except for the banner configurations, as I thought they are irrelevant for this issue). I use Mailpoet for email notifications about new blog posts, and complianz to hide the Mailpoet opt-in form before consent is given (on this page), because the form uses Google recaptcha.
As I said, on my live site everything is still ok. Chapter 7 is still in the cookie policy. The only difference between test and live in terms of configurations is:
- live is still on complianz v7.2.0, because I have the issue with the missing chapter
- the live site has not yet activated the “new and improved website scan”
- Jetpack is not installed on my live site, only in test (but this has been the case since I started with complianz
Thank you
-
This reply was modified 4 months, 1 week ago by
dillhausen.
Hi,
any updates? Meanwhile, v7.3.1 is out, but there were no changes to the cookie policy according to the release notes. I have not yet installed it, because I don’t want to interfere in any debugging process on your side…please tell me if I should install the new version.
Thanks
Updated to version 7.4.0.1, but problem persists
Hello @dillhausen ,
Thanks for the constant updates and the screenshot. Could you please try to delete the page generated by Complianz and regenerate it with the latest version? It might be bugged. Unfortunately, I am not able to reproduce the issue.
Thanks in advance. Wishing you a happy Easter!
Hi @antoiub,
Thanks. Unfortunately, deleting the page and re-creating it with the wizard does not help!
But I found out some interesting behaviour: I created a page on my own and used the 2 available shortcodes and the Gutenberg block for the cookie policy on this page. According to my understanding, the shortcode [cmplz-manage-consent] should re-create exactly the missing former chapter 7, which is indeed the case. The Gutenberg block also creates the chapter 7, but they are NOT THE SAME. The chapter 7 in the Gutenberg block always shows the “On AMP…” clause, whereas the shortcode always shows the possibility to manage cookie consent, no matter of the browser settings like DNT etc.
Maybe this finding gives you a hint about the root cause…
I could create my own page with the 2 shortcodes and my own text, but then I loose all the advantages of a synchronized cookie policy, correct?
Thanks
Sorry, I have to correct myself in part: the shortcode behaves completely as expected: With DNT, it shows the message “WE have received a privacy signal from your browser”, without DNT it shows the possibility to manage consent. Everything else does not behave as expected.
Hello @dillhausen ,
Thank you for your hints. After further checking your original page and the one created after, there’s a substantial difference. On the original one, the Complianz JavaScript is not loading; therefore, the cookie categories cannot be shown (screenshot here). On the other page, it is loading, which is why the categories are displayed (screenshot). Have you disabled Complianz on the original cookie page somehow? We have a guide that explains how to exclude the banner from the pages, that you can find here, basically unchecking the setting will restore the categories and loads the complianz js.
Please let me know. Looking forward to hearing from you.
Thank you! That was the solution! I had deactivated complianz on the cookie policy right from the beginning, because people shall be able to read the policy without being interrupted by the banner (at least, that was my understanding why a page should have complianz deactivated, but I might have been wrong…)
Thanks again!
Hello @dillhausen ,
I am glad to hear that. By its logic, the Complianz Banner won’t load inside the Cookie Policy, as the possibility to choose preferences is available in the Cookie Policy itself (e.g., selecting which cookie category to enable by checking them in section 7.1).
Anyway, I am glad that we solved this. Wishing you a nice day!
