Antonio Candela
Forum Replies Created
-
Hi Matthew,
At this point, I think we can confidently rule out that the issue is on Complianz’s side, since the banner is working correctly across various devices.
The most likely cause now is something specific to the browser or device you’re using on your end. Privacy-focused browsers like Brave, or any installed ad blockers / privacy extensions, are often configured to block consent banners and similar elements automatically, which would explain exactly the behavior you’re seeing.
If you’d like to confirm this, you could try opening the site in a different browser on your phone (e.g. stock Chrome with no extensions) or temporarily disabling any privacy extensions you might have installed.
If you need further help, feel free to open a new thread.
Best,
AntonioHi @james-feaver,
Thanks for reaching out, and apologies for the inconvenience you’re experiencing.
This kind of behavior usually happens when something gets blocked by the consent plugin and the dependency chain between WooCommerce and Complianz breaks. Could you confirm whether consent has been accepted on the page when you encounter the error? That would be the first thing to rule out.
If you need to test the checkout flow specifically from the WP admin area without having to deal with the consent banner each time, you can exclude that page from the banner entirely by following this guide: https://complianz.io/excluding-pages-from-the-cookie-banner/.
This should do the trick for you, since the issue doesn’t occur in the visitor view. As for the debug log information, that’s actually not related to our plugin, it’s coming fromdisable-dashboard-for-woocommerce.
I hope this helps.
Best,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Missing French translationsHi Mitch,
Thank you for reaching out, and apologies for the translation issues you’re experiencing! We’re already aware of this and a fix will be shipped in the next plugin release.
Thanks a lot for your patience in the meantime.
Best,
AntonioHi Matthew,
Thanks a lot for the additional details and observations!
Could you try clearing your mobile browser’s cache and reloading the site? Sometimes mobile browsers can hold on to cached versions for a long time, which would also explain why you’ve never seen the banner appear on your phone.
On my end, I tested the site from desktop using mobile user-agent emulation for both iPhone and Android (Pixel), and the banner appears and works correctly in both cases. I’ve attached a screenshot for reference: https://prnt.sc/j5DfVIfCmc_O.
Once you’ve cleared the cache, please try accessing the site again in a fresh session and let me know if the banner shows up.
BR,
Antonio- This reply was modified 12 hours, 32 minutes ago by Antonio Candela. Reason: typo
Hi @atypiclab ,
Thanks for the detailed report, and please accept our apologies for the late reply on this.
I spent some time trying to reproduce the issue on my end using the Age Gate plugin (https://ww.wp.xz.cn/plugins/age-gate/), but I wasn’t able to replicate the problem you described. On my test setup, the Complianz banner appeared in front of the Age Gate banner without any interaction issues, and I could click the age verification buttons normally.
To dig into this properly, could you kindly help us with a couple of things:
- A short screen recording (via Loom or any similar platform) showing the issue in action, including your Age Gate plugin settings, that would give us a much clearer picture of how everything is configured on your side.
- Information about the theme you’re currently using on the affected site, themes can introduce CSS conflicts that affect the
pointer-eventsbehavior, so this detail is important.
I also had a look at the test link you shared (https://test-domaine-ampelhus.atypic-lab.fr/), but the site appears to be missing most of its content/styling, which makes it hard to use as a reliable test environment. For comparison, when I tested on a clean Gutenberg-based theme, the issue did not appear at all.
Without being able to reproduce the issue on our side, it’s tricky to give you a concrete fix, but with a Loom and the theme details we should be able to make much faster progress.
Looking forward to your reply.
Best,
AntonioForum: Plugins
In reply to: [Complianz - GDPR/CCPA Cookie Consent] Huge cmplz_transientsHi @stekky81 ,
Thanks for the detailed report.
On a site publishing a lot of articles with embedded YouTube videos, this data can build up and start affecting database performance. We’ve logged this internally for our developers to investigate, so we can look at the best way to handle this for high-volume sites.
I’ll keep this thread updated as we make progress.
Thank you again for the report and for your patience.
Best,
AntonioHi @mmk175,
Thanks for the detailed report and apologies for the inconvenience!
To get to the bottom of this, could you kindly share the URL of your site so we can check the mobile view directly on our end? Without seeing the live site it’s quite hard to pinpoint what might be going wrong specifically on mobile.
In the meantime, here are a couple of things worth checking on your side:
1. Exclude Complianz from SG Optimizer cache
The most likely culprit when behavior differs between desktop and mobile is caching, especially with SG Optimizer in the mix. Caching plugins sometimes serve different cached versions for mobile/desktop, and if Complianz scripts are being delayed or stripped out on mobile, the banner can fail to render. Please follow this guide to exclude Complianz properly from your caching setup: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/
2. Clarification on “Show everywhere”
Just to clarify a small but important point: the “Show everywhere” setting you mentioned actually refers to the Manage Consent feature, which controls how users can re-access and modify their consent after it’s been given (i.e. the small icon that lets them revisit their preferences). It does not control the visibility of the initial consent banner itself.
That said, our consent banner doesn’t have any setting that restricts it based on mobile vs desktop user agent, so the banner should appear the same way across all devices unless something external (caching, theme conflict, JS error) is interfering.
Looking forward to the site URL so we can investigate further.
Kind regards,
AntonioHi @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.
[email protected]), 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.ww.wp.xz.cn/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 1 day, 9 hours 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 ww.wp.xz.cn 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,
Antonio