Antonio Candela
Forum Replies Created
-
Hi @r16n ,
Thank you for reporting this.
We have flagged the issue to our development team and opened an internal task. We will get back to you as soon as we have an update.
Best regards,
Antonio@dirkmaplelane – @developmentvict – @zenzen279
Hi everyone,Thanks for the detailed reports and especially for the workaround, @dirkmaplelane. I’ve passed everything from this thread along to our development team, including the snippet you shared.
The underlying issue is already on our task list and the devs are actively working on it. We’re aiming to ship the fix in the next release. I’ll update this thread as soon as I more updates.
Thanks for your patience while we get this sorted.
Best regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Email obfuscation does not workHi @simonclay ,
The obfuscation is there to protect the address from bots and crawlers that scrape pages looking for email addresses to spam. To human visitors, the end result is just plain text showing the real email (e.g.
info@yoursite.com), which they can read and copy into their email client.It’s intentionally not a clickable
mailto:link, because that’s the easiest pattern for scrapers to harvest. So visitors do see the correct address, they just can’t click it directly.I hope this answer your question.
Best regards,
AntonioHi @grntwlkr,
Thanks for the report, but this is actually intentional, not a bug.
ex.comis a decoy we inject into the email markup as an anti-scraping measure. Bots that scrape raw HTML pick up the broken version and end up with a useless address, which is the goal. For PDFs the decoy is stripped out before rendering.If you’re curious, the relevant code is public: https://plugins.trac.wordpress.org/browser/complianz-gdpr/.
If you’re seeing
ex.comin the rendered page in a normal browser (not view-source), that would point to the plugin’s CSS not loading on your site, usually a caching or optimization plugin. In that case I kindly ask you to consult: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/.
I hope this helps.
Best regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Unable to block iframeHi @elo8617,
The Script Center URL blocker isn’t catching
app.superhote.combecause the Superhote iframe bypasses the standard blocking mechanism.The reliable solution is to wrap the iframe in a Consent Area Block, which prevents the iframe from loading at all until the user gives consent. You can follow the official guide here: https://complianz.io/gutenberg-block-consent/.
Once you’ve wrapped the iframe in the Consent Area Block, you can fully customize the placeholder shown to visitors before consent. Here’s an example of HTML + CSS you can use:
HTML
<div class="cmplz-consent-block">
<span class="cmplz-consent-block-title">Bookings and availability – Superhote</span>
<p class="cmplz-consent-block-text">To view the availability calendar and make a booking, please accept Superhote cookies.</p>
<div class="cmplz-consent-block-actions">
<button class="cmplz-consent-block-button">Accept</button>
<a href="/cookie-policy" class="cmplz-consent-block-link">Which cookies?</a>
</div>
</div>CSS:
.cmplz-consent-block {
max-width: 600px;
margin: 2rem auto;
padding: 2rem;
background-color: #f8f9fa;
border: 1px solid #e0e0e0;
border-radius: 12px;
box-shadow: 0 2px 8px rgba(0, 0, 0, 0.06);
text-align: center;
font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, sans-serif;
color: #333;
}
.cmplz-consent-block-title {
display: block;
font-size: 1.25rem;
font-weight: 600;
margin-bottom: 0.75rem;
color: #1a1a1a;
}
.cmplz-consent-block-text {
font-size: 1rem;
line-height: 1.5;
margin-bottom: 1.5rem;
color: #555;
}
.cmplz-consent-block-actions {
display: flex;
justify-content: center;
align-items: center;
gap: 1.5rem;
flex-wrap: wrap;
}
.cmplz-consent-block-button {
background-color: #0066cc;
color: #fff;
border: none;
padding: 0.75rem 1.75rem;
font-size: 1rem;
font-weight: 500;
border-radius: 6px;
cursor: pointer;
transition: background-color 0.2s ease, transform 0.1s ease;
}
.cmplz-consent-block-button:hover {
background-color: #004fa3;
}
.cmplz-consent-block-button:active {
transform: scale(0.98);
}
.cmplz-consent-block-link {
color: #0066cc;
text-decoration: none;
font-size: 0.95rem;
border-bottom: 1px solid transparent;
transition: border-color 0.2s ease;
}
.cmplz-consent-block-link:hover {
border-bottom-color: #0066cc;
}
@media (max-width: 480px) {
.cmplz-consent-block {
margin: 1rem;
padding: 1.5rem;
}
.cmplz-consent-block-title {
font-size: 1.1rem;
}
}I tested it on my staging site and the blocking before consent works correctly. The end result should look like this: https://prnt.sc/VLkSt-sF1hDe.
Best regards,
Antonio- This reply was modified 2 weeks, 3 days ago by Antonio Candela.
Forum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] WP MAPS PROHi @benrobertson ,
Thanks for reaching out!
WP Maps Pro is a paid/premium plugin, and the WordPress.org forum rules don’t allow detailed support discussions around paid plugins on this platform. That said, I can confirm we do offer compatibility with such plugins through our plugins integrations.
If you’re running into difficulties getting the two to work together, I’d kindly ask you to reach out either to our support team or to WP Maps Pro’s own support channel, where the right people can take a proper look at your specific setup and help you sort it out.
Kind regards,
AntonioHi @gwuk ,
Thanks a lot for the detailed report!
I had a quick look online at Hallmaster (https://hallmaster.com/booking-systems/online-booking-system/online-calendar-booking-system/) and it appears to be a paid service. Given that, integrating it correctly with Complianz could involve some nuances around the placeholder, blocking behavior prior to consent, and possibly your custom theme, which makes it a bit tricky to troubleshoot fully on an open community forum, especially without being able to see your specific setup.
Would you mind reaching out to us directly through our support channel at https://complianz.io/support? That way we can take a proper look at your configuration, help you get the integration working correctly, and then come back here to post the solution publicly so the rest of the community can benefit from it as well.
Looking forward to hearing from you.
Kind regards,
Antonio
Hi @griotta,Thanks for taking the time to flag this-
I want to be upfront with you on something: plugins evolve constantly, and as much as we try to stay on top of every update, it can happen that we miss new scripts being introduced by third-party integrations. When that happens, it can lead to a partial block of the integration in question, which is exactly what you’re observing here. That’s also one of the reasons we rely so much on the community to spot these cases, feedback like yours is genuinely valuable.
In this specific case, the plugin has been renamed to Meta for WooCommerce, and given the changes around their Conversions API and parameter collection scripts, it would really help us if you could open a support ticket on our side at https://complianz.io/support. That way we can do a proper review of everything the plugin is currently injecting and update our integration accordingly.
Real-world test cases like the one you’re working on are honestly the best way for us to validate this kind of thing, so your input would be much appreciated.
Thanks again for the heads-up.
Best regards,
AntonioHi @power2009,
Thank you so much for taking the time to put together such a detailed and well-researched report. We already have an internal task open regarding this issue, so it’s on our radar. That said, I’ve personally forwarded your proposed solution to our development team, so they can take your input into account when working on the fix.
I’ll keep you posted as soon as I have any concrete update from their side.
Thanks again, feedback like this genuinely helps us improve the plugin!Kind regards,
AntonioHi @emite ,
Apologies for the late reply on this.
Both of the cookies you mentioned are actually present in our cookiedatabase.org, but they’re listed under a wildcard pattern that catches all the variants:
wp-settings-*coverswp-settings,wp-settings-1, etc.wp-settings-time-*coverswp-settings-timeand its numbered variants.
So the entries you linked to are correct, and the plugin should be picking them up via these wildcards.
Could you please try re-running not only the cookie scan but also the sync with cookiedatabase.org itself, and let us know if the cookies get properly associated afterwards? Sometimes a fresh sync resolves the mismatch.
For reference, I tried to reproduce the issue on my local setup and the sync works correctly on my end, both cookies are detected and assigned to the right service, so it might be a sync state on your specific install that needs refreshing.
Looking forward to your feedback.
Kind regards,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Issue with GA4 and WooCommerce eventsHi,
Answered in https://wordpress.org/support/topic/best-beginner-friendly-setup-for-ga4-woocommerce-events-complianz/.
BR,
AntonioHi @le-tom
Thanks for the detailed question and sorry for the delayed answer. This has already handled by our Legal Department.
Following Google’s announcement about reCAPTCHA moving from data controller to data processor (effective April 2, 2026), our legal team reviewed the change and we pushed an update to the generator earlier this year. The reference to Google’s reCAPTCHA Privacy Policy and Terms of Use has been removed from the auto-generated Cookie Policy text, in line with Google’s new guidance.
To address your points directly:
- Yes, the wording was reviewed by our legal team when Google announced the change.
- Yes, and the update is already live. The sentence pointing users to Google’s reCAPTCHA Privacy Policy / Terms of Use has been removed from the synchronized text.
- No special handling is needed on your end. If document synchronization is active, the updated wording should already be in place on your site after the next sync, no need to break automation or edit the page manually.
- No, you do not need to disable synchronization. The fix is delivered through the normal sync flow.
One clarification worth adding on categorization (since this comes up often): Google’s controller-to-processor change concerns the allocation of GDPR responsibilities between Google and the website owner. It does not change how reCAPTCHA should be categorized in the CMP, because categorization is determined by the purpose and technical function of the technology, not by the legal qualification of the provider. So the existing category mapping for reCAPTCHA in Complianz remains correct and will not be re-mapped.
If you’re still seeing the old wording on your site after a successful sync, please make sure that:
– the Complianz plugin is updated to the latest version,
– document synchronization has run successfully,
– and any page/browser cache has been cleared.If the outdated text persists after that, just reply here with the URL of the page and we’ll take a closer look.
Best regards,
AntonioHi @jessica1418,
Thanks for following up, and apologies that your previous message went unanswered.
Let me address your questions one by one:
General recommendation
Before getting into the specifics, I’d genuinely encourage you to invest a little time in learning the basics of Google Tag Manager (GTM) and event tracking. I know it might feel like overkill at first, but truly, GTM knowledge is one of those things that pays off massively in the long run, you’ll find yourself reaching for it again and again. For a project like yours (GA4 + WooCommerce events), GTM is really the most reliable and flexible foundation.
A small but important clarification
There’s no such thing as “Complianz Consent Mode”, what we support is Google Consent Mode v2, which is the official Google framework. Keep in mind that this is a Premium-only feature, so it’s not available in the free WordPress.org version of Complianz.
Recommended setup
For your use case, I’d suggest combining Complianz with our general-purpose GTM guide, which will allow you to work with custom events: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/.
You’ll also need to install GTM4WP, paying particular attention to this specific step: https://complianz.io/simplified-guide-to-google-consent-mode-v2/#:~:text=GTM4WP%20Procedure%20Note%3A.
Then, from your WordPress Dashboard, go to Settings > Google Tag Manager, navigate to the Integration tab, check the box for WooCommerce, and enable Track enhanced e-commerce.
Once that’s done, you can create all the events you need directly in GTM. There are plenty of beginner-friendly tutorials on YouTube that walk through exactly this kind of setup, so I’d recommend starting there.
Kind regards,
AntonioHi @crashtest,
Thanks for the detailed report.
The tricky part is that this kind of behavior isn’t specific to Complianz: most consent management platforms and cookie-blocking tools run into the same issue with privacy/ad-blocking extensions, simply because the file names (cookieblocker, consent-blocker, tracker-blocker, etc.) match the heuristics those extensions use to flag tracking scripts. Chasing whitelisting case-by-case with every browser extension tends to be a moving target, they update their rule sets often, new extensions show up, and renaming our core files would just break compatibility for everyone else.
The most reliable fix on the user side is to whitelist the site locally in Malwarebytes Browser Guard. Once whitelisted, the banner will render normally, including in Incognito.
I hope this helps.
Best,
AntonioHi @mark88008,
Thanks for reaching out. This is the Complianz support forum, so for issues related to how the GTranslate switcher is rendered, the right place to get help is the GTranslate support team. They’ll have full visibility into how their plugin outputs the switcher in different positions on your site.
Best,
Antonio