Antonio Candela
Forum Replies Created
-
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] No Banner in Frontend visibleHello @kaschwei ,
I’m glad to hear you managed to solve the issue on your own. I just checked your site, and I can confirm that the banner is now displaying correctly on the frontend.
If you run into any other questions or need help with additional configuration, feel free to reach out anytime.
Best,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Javascript conflict since last updateHello @ijscobrand ,
if disabling AJAX solves the problem, then that’s perfectly fine, you can safely keep it that way.
If you need help with anything else or run into further issues, we’re at your disposal.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Javascript conflict since last updateHello @ijscobrand ,
Thank you for reaching out.I’ve checked your page URL and don’t see any JavaScript errors in the console. I also tested the free version of the ICS Calendar plugin, and I wasn’t able to find any conflict with Complianz.
Could you please check if the issue might be related to caching? Try excluding both Complianz (here’s how) and ICS Calendar from your cache configuration.
Additionally, if you’re blocking the calendar before consent, please try temporarily disabling the pre-blocking, this is an important step during troubleshooting, as it helps confirm whether the issue is caused by the blocking logic or something else.
Let me know what you find.
Best regards,
AntonioHello Mike,
Thank you very much!Hello @cutu234 ,
Thank you for reaching out.
Our plugin does not deactivate itself automatically under normal circumstances. The only situation that could potentially lead to an unexpected deactivation is a crash, in which case WordPress may automatically disable a plugin to prevent further issues.
If that happened, there should be a related entry in your site’s error log. If you can locate it, please feel free to share it here, we’ll be happy to take a look.
In any case, there’s no need to worry, all current versions of the plugin are stable and safe to use.
Best,
AntonioHello @dillhausen,
Thank you for reaching out.Thank you for bringing this up and for the detailed explanation. We’re currently looking into this behavior to better understand the detection and classification of the cookie you mentioned.
We’ll review the situation and provide you with an update as soon as possible.
Thanks again for your patience and for taking the time to report this.
Best,
AntonioHello @webintenerife ,
I’m really glad to hear that you managed to solve the issue!
If you’d like, you can also use the new MU plugin, I’ve added the missing element to the whitelist directly via code in the same gist I shared earlier.
This should make the integration smoother.If you need anything else or run into any further issues, we’re at your disposal.
Best,
AntonioHello @aazgalerie ,
I want to reassure you that the issue is already scheduled for a complete revamp.
Best,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Cookie ploicy page contentHello @testcs1041,
Would it be possible for you to send us a short video showing the issue so we can review it? Also, could you please try the same shortcode on another page to see if the behavior is the same?
Lastly, can you confirm that the plugin is updated to the latest version? This will help us make sure we’re testing under the same conditions.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Facebook Pixel not blockedHello @jpnl,
Thank you for reaching out.
I’ve checked your site, and Facebook is indeed blocked before consent. You can confirm this by visiting your site as a regular visitor and inspecting it through your browser’s Developer Tools → Network and Application → Cookies tabs.
Before accepting the banner, you’ll notice that Facebook scripts are not loaded, confirming that the blocking is working correctly. Here you can find a video that describes this behaviour.
I hope this helps!
Best regards,
AntonioHello @mymothersdaughter ,
Thank you for reaching out.
This message usually appears when two shortcodes are present on the same page: one for the UK region and one for the EU region. That’s why you’re seeing the “Region UK not activated for cookie-statement” message.
I tested this behavior locally and got the exact same result. Here’s a quick screenshot showing the same scenario (and yes, on the WordPress forum it’s not possible to upload images directly)
Please double-check the page to see if there’s a second shortcode present somewhere (for example, in a block, widget, or template). Once removed, the message should disappear.
Could you verify this and let us know?
Best regards,
AntonioHello @webintenerife ,
Thank you for the update.
In this case, since OpenStreetMap is embedded through a third-party plugin (Ultimate Maps by Supsystic), this falls under an expected exception, meaning the automatic blocking may not work as intended. Our integrations are designed to cover most generic embed methods, but when a map is inserted via an external plugin, this behavior is expected.
For situations like this, you’ll need to either use the Script Blocker or a custom integration. I’ve gone ahead and prepared a custom integration you can use, which you’ll find at this link: https://gist.github.com/tonai126/a3ab2734ec0c10d9be9fcb29af17cc6f.
It’s an MU plugin that works alongside the OpenStreetMap service available under Complianz → Integrations → Services.
Here’s what you need to do:- First, activate the OpenStreetMap service in the Complianz dashboard.
- Then, upload the MU plugin to your
wp-content/mu-pluginsdirectory. - If you have caching enabled, please clear your cache afterward.
Once done, the map should work correctly; I’ve tested it in my local environment without any issues.
Please let me know how it goes.
Best regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Cookie ploicy page contentHello @testcs1041,
There’s no need, in this case, to make the option appear while using the Classic Editor, you just need to insert the shortcode and then save the post or page.
Once it’s saved, the option will appear, and you’ll be able to select your preferred setting.Here’s a short example video showing how it works.
Can you please check this and let me know?Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Issue in your pluginHello @laurapn ,
Thank you for reachiing out.I am sorry to hear that. If the React app is failing to load correctly, you can open your browser console to see the exact error message that will tell us why it’s breaking.
If only some dashboard panels are crashing, it could be due to either:
- REST API issues, in this case, you’ll see an error in the browser console related to
/wp-json/complianz/v1/. If this is the case, please check here. - Insufficient server resources, sometimes the site doesn’t have enough PHP memory or processing capacity. You can check your PHP variables (like
memory_limit,max_execution_time, etc.) to see if they’re in a normal range.
Could you please send us both the console errors and the PHP configuration info? The more details we have, the easier it will be to identify what’s happening.
I hope this helps.
Best regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Cookie ploicy page contentHello @testcs1041 ,
thank you for the follow-up.
The “Document Status” option is available regardless of the Complianz version. This setting isn’t located in the plugin options but rather inside the page editor, whether you’re using Gutenberg or the Classic Editor.
Once you insert the Complianz shortcode on your policy page, the Document Status will appear in the sidebar, as explained in our guide.
Best regards,
Antonio