Forum Replies Created

Viewing 15 replies - 121 through 135 (of 769 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    Hello @kpolljonker ,

    Yes, we have received the email and we are investigating.

    Thank you very much, we will update you as soon as possible.

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @kpolljonker ,

    Thank you for bringing this to our attention.

    We are currently investigating this issue. We take this very seriously, as we want to ensure that these types of emails are not sent, not even by mistake.

    To help us track this down, could you please kindly forward both emails you received (ideally combined in a single message) to support@complianz.io? This would be very appreciated and will allow me to verify if this is a cross-product issue.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @jenomal ,

    The Support Moderator is right. WordPress.org guidelines do not allow sharing or requesting login credentials in any form. This rule is in place for your security as well as ours.

    We did receive your email, and your message is already in our support system. We’ll follow up with you directly via email as soon as possible.

    For this reason, and since further troubleshooting must continue privately, this thread will now be marked as resolved and closed on the forum.

    Thank you for your understanding.

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @jenomal ,

    The best solution would be to send us another email from a different address (domain). This way, you can copy-paste the content, and we avoid exposing your private data on the forum.

    As for the problem itself, I actually tested this setup but was unable to replicate the issue. Here’s a screenshot: https://prnt.sc/CvVD-rxmaePj. I tested with Classic Editor v1.6.7, Complianz 7.4.4, WP 6.8.3, and PHP 8.2.27.

    Please let us know how you would like to proceed.

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @katmacau ,

    It’s correct that you only see the “Accept” button, that’s how the opt-out model works.
    The user gives consent by default, and the withdrawal mechanism is provided through the Opt-out preferences or the Cookie Policy page.

    If you’re using a custom page instead of the one generated by Complianz, you’ll need to add this shortcode: [cmplz-manage-consent] .
    This will display the cookie categories and allow users to revisit and adjust their consent.

    Let me know if that helps.

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @jenomal ,

    Thank you for reaching out.

    I am sorry to hear about the communication issue. Our support email is still available and hasn’t changed. Thank you for sticking with us after all these years.

    If you sent your previous requests using the support form inside the plugin, it is highly likely they were never transmitted. The plugin form relies on wp_mail to send emails to support@complianz.io. Many development environments (staging sites, local setups, etc.) do not support outgoing email, so the messages likely failed to send without showing an error.
    We always send an automated confirmation of receipt; if you didn’t receive that, it confirms the email didn’t go through. Please user another email (eg. a gmail one).

    Regarding the Classic Editor, we are not aware of any conflicts. Could you please share the URL where we can see the issue (both with and without the Classic Editor active)? It would also be helpful to know which theme or page builder you are currently using.

    Please let us know.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @specialconnectionstudio ,

    Thank you for reaching out.

    I checked your site and I do see the banner appearing on every page, whether I accept it or not.
    After reviewing your setup, there are a couple of configuration issues causing this behaviour:

    Cookie expiration is set to 0
    This means the consent cookie expires immediately after being set, so the banner keeps reappearing.
    You can fix this here: Settings → General → Consent banner expiration in days.
    Set it to 365 (the default) or any value ≥ 1.

    Root-domain cookie setting enabled unnecessarily
    You currently have “Set cookiebanner cookies on the root domain” enabled. If your site only uses a single domain, this should be disabled.
    You can disable it here: Settings → General → Set cookiebanner cookies on the root domain
    More details here about the cross-domain consent: https://complianz.io/cross-domain-cookie-consent/.

    Last but not least, you are using WP Rocket, and its optimization can prevent Complianz scripts from working correctly unless properly excluded. Please exclude the Complianz assets as described in this article:https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins.

    After applying all three steps, the consent will be stored correctly and the banner will stop reappearing.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @kpolljonker ,

    Thank you for taking the time to share this, and I’m really sorry to hear that.

    All our product-related emails are meant to be strictly opt-in. If you’ve disabled every marketing toggle in each installation, you should not be receiving marketing messages anymore. That’s why we’d really appreciate it if you could forward one of the emails you believe should not have been sent at support@complianz.io. This will allow us to double-check on our side and see exactly what went wrong.

    We definitely don’t want to overwhelm your inbox, and we take feedback like this seriously.
    Once we identify the source, we’ll make sure it’s corrected.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @rayeason ,

    You can use the following CSS to fix the issue:

    .pix-theme-tone-dark .cmplz-close[role="button"] {
    background-color: unset !important;
    }

    I hope this helps.

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @katmacau ,

    Thank you for reaching out.

    The way cookie rejection works depends on the consent model. For Australia, the model is opt-out, which means cookies are accepted on the first visit, but users can freely opt out through the dedicated page. This is the compliant approach, as we follow the latest regulations.
    The opt-out model applies to CCPA (California) as well, we have an article here about the US & Canada: https://complianz.io/cookie-consent-in-the-us-and-canada-what-you-need-to-know.

    That said, with the WordPress.org version you can only select one region at a time.
    This means you’re limited to the opt-out consent type for your current setup.

    If you’d like to change this behavior, you can create your own custom banner from scratch by following this guide:https://complianz.io/create-your-own-banner-from-scratch.

    I hope this helps.
    Best Regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @rayeason,

    Thank you for reaching out.

    In this case, you can handle it in two ways, depending on what fits your phased approach best:

    1. Configure everything now, but keep blocking disabled.
    You can fully configure the plugin and simply disable the actual script blocker under: Wizard → Finish → Enable cookie and script blocker → No.
    This works perfectly for your phase 1. When you’re ready to start blocking, just switch this back to Yes.

    2. Activate blocking only for specific services when needed.
    Alternatively, you can set up a complete configuration and then enable each service (YouTube, Facebook, etc.) only when you decide it’s time. Until then, Complianz won’t block anything related to those services.

    Both methods allow you to “warm up” your users before fully switching to consent-based blocking.

    I hope this helps.
    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @peopleinside ,

    Thank you for reaching out and for the snippet you’re testing in the meantime.

    Two of us tried to reproduce the issue (both on your site and locally), but we weren’t able to trigger the “Open in YouTube App?” popup on Firefox for Android. On your site the mentioned functionality is disabled at the moment by the above snippet, and in our local tests it didn’t happen.

    Before we escalate this as a possible edge-case bug, could you please run one more check on your side? Can you try switching temporarily to a default theme (e.g. Twenty Twenty-Five)?

    This will help confirm whether the issue is actually coming from Complianz or if a theme script/layout interaction is causing Firefox to misinterpret the embed.

    A theme-level override is a very common cause of unusual iframe behavior, especially on mobile.
    If possible, please also share:

    • the Firefox version you’re using on Android
    • the exact steps to reproduce
    • whether the popup appears before accepting cookies or only after

    This extra detail will help us track down the cause accurately.
    Let me know once you test with the default theme.

    Looking forward to hearing you.
    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hello @rayeason ,

    Thank you for reaching out.

    The reason you can’t find the GTM field is that Google Tag Manager for WordPress (GTM4WP) is currently enabled in Integrations. When this integration is active, Complianz hides the GTM fields to prevent a double installation of the Tag Manager script.

    This is also written on the right side of the UI, inside your video, here’s a screenshot: https://prnt.sc/hUR3MO4rwcum.

    To make the GTM field appear again:

    1. Go to Complianz → Integrations → Plugins
    2. Disable Google Tag Manager for WordPress
    3. Save your settings
    4. Refresh the page, the GTM fields will now be visible again

    After that, you can insert your GTM code normally.

    I hope this helps.
    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @rayeason,

    Both triggers are valid, it just depends on what the tag is doing.

    You can choose the trigger based on the purpose of each tag, but usually the triggers are used in this way:

    • Pure measurement = Statistics
    • Advertising or user profiling = Marketing

    I hope this helps,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @peopleinside ,

    Thanks for the explanation and for reaching out.
    I understand your point about not wanting those thumbnails stored if you’re not using them.

    You can indeed prevent Complianz from downloading and saving video thumbnails while still using placeholders.
    Please use the snippet below and let us know if it fits your needs:

    // Block placeholder image downloads
    add_filter('pre_http_request', function($preempt, $args, $url) {
    $backtrace = debug_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS, 10);
    foreach ($backtrace as $trace) {
    if (isset($trace['function']) && $trace['function'] === 'cmplz_download_to_site') {
    return new WP_Error('complianz_download_blocked', 'Download blocked');
    }
    }
    return $preempt;
    }, 10, 3);

    After adding the snippet, delete the existing files in:wp-content/uploads/complianz/placeholders
    This will remove the thumbnails that were previously generated.

    Once done, please clear any caching (plugin, server, CDN) to ensure the change takes effect.
    From that point on, Complianz will stop generating and saving new screenshot placeholders, and you can continue using your own grey placeholder without filling up your server space.

    Let me know once you’ve added the function so we can confirm everything is working correctly.

    Best,
    Antonio

Viewing 15 replies - 121 through 135 (of 769 total)