Forum Replies Created

Viewing 15 replies - 46 through 60 (of 769 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    Hi @julisazavala3 ,

    Thank you for reaching out.

    Yes, Complianz runs automatic background scans, so if new cookies are detected on your site they will be added to the cookie policy automatically without requiring you to manually trigger a new scan.

    I hope this helps.

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @griotta ,

    Thank you for reaching out.

    Yes, this is expected behaviour. When Complianz blocks a script prior to consent, it changes the script type from text/javascript to text/plain , this is intentional and is precisely what prevents the script from being executed by the browser before consent is given.

    That said, as a general note, aggressive caching can sometimes cause issues with this mechanism. When using LiteSpeed Cache, we generally recommend excluding our parameters from the cache configuration to ensure Complianz functions correctly. You can find all the relevant parameters to exclude by following this guide: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/

    I hope this helps.

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi Gabriela,

    Thank you for reaching out!

    I just checked your site and I can see the “Manage Consent” tab clearly visible alongside with your 2nd answer. However, if you would like a more prominent and user-friendly option, you can follow this guide to set it up as a floating button, which should give you the visual effect you are looking for:

    https://complianz.io/css-lesson-23-your-manage-consent-button-as-floating-widget/

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @dillhausen ,

    Thank you for reaching out.

    Since the cookie policy page is generated by Complianz, it may not automatically inherit all of your theme’s styling. The best way to address this is by adding custom CSS rules to match your preferences. Here is an example that should bring the text size in line with your Impressum page, feel free to adjust the values to your liking:

    div#cmplz-document h2 {

    font-size: var(--wp--preset--font-size--x-large);
    }

    div#cmplz-document p {

    font-size: var(--wp--preset--font-size--custom-1);
    }


    div#cmplz-document h3 {

    font-size: var(--wp--preset--font-size--large);
    }

    You can add these rules directly in your theme’s stylesheet.

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @dillhausen ,

    Thank you for the detailed follow-up and for testing with the new version.

    I would like to clarify two important points that together explain the behaviour you are observing.

    First, regarding the statistics category: this is actually expected behaviour. By default, the statistics category in Complianz is set to opt-in, meaning it does not require explicit consent from the user. If you would like users to be able to deny consent for statistics cookies, you will need to set the option “Do you want to ask consent for statistics?” to “Yes” in Wizard > Consent > Statistics configuration. Once this is set to “Yes”, the statistics category will become opt-out and users will be able to deny consent for it both in the banner and in chapter 7.1 of the cookie policy.

    Additionally, if the statistics category does not appear at all in the banner after completing the configuration, this means that Complianz has been set up in a way that does not require this category to be displayed to the user.

    Second, regarding the cookie table in your cookie policy, this is purely informational. Its purpose is to show visitors which services and cookies are present on your site, and it updates automatically as services are added or removed. It has no functional role in terms of blocking or allowing scripts. The actual blocking mechanism is handled separately through Complianz’s internal consent cookies (cmplz_functional, cmplz_statistics, cmplz_marketing, cmplz_preferences), which are always created for all four categories regardless of which ones are actively used on your site.

    This also explains why the manually created test cookie you added is visible in the cookie policy table for informational purposes, but unless there is an actual script or service configured under the Statistics category, there is nothing to block or allow in practice.

    Please let us know if you have any further questions.

    Best regards,
    Antonio

    Hi @hebhansen ,

    With the latest update 1.3.0 we have updated our codebase to match the latest WordPress requirements, including a fix for this issue.

    I hope this helps!

    Plugin Support Antonio Candela

    (@antoiub)

    Hi, thank you very much for the update.

    If any issues come up, please feel free to open a new thread and we will look into it.

    Best,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi everyone,

    Thank you all for your patience and for the detailed reports, they were very helpful in identifying the root cause.

    The issue was caused by an unusually high number of requests to cookiedatabase.org, which triggered Cloudflare’s WAF and blocked the sync. This has now been restored and should be working correctly again.

    Could you please try again on your end and let us know if the issue persists? If you are still experiencing any problems, please do not hesitate to report back here and we will look into it further ASAP.

    Sorry for the inconvenience and thank you for your understanding.

    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi everyone,

    Thank you all for your patience and for the detailed reports, they were very helpful in identifying the root cause.

    The issue was caused by an unusually high number of requests to cookiedatabase.org, which triggered Cloudflare’s WAF and blocked the sync. This has now been restored and should be working correctly again.

    Could you please try again on your end and let us know if the issue persists? If you are still experiencing any problems, please do not hesitate to report back here and we will look into it further ASAP.

    Sorry for the inconvenience and thank you for your understanding.

    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @dochara ,

    Thank you for reaching out and we are sorry to hear you are experiencing this issue.

    To help us investigate further, could you please provide us with the following:

    • A video or screenshot showing the issue
    • Your WordPress configuration details (WordPress version, PHP version, active plugins, theme)

    This will allow us to better understand the problem and work towards a solution as quickly as possible.
    Thank you in advance.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @ascrivano ,

    Thank you for reaching out.

    This issue is most likely related to the cookiedatabase.com server, which we are already aware of and currently investigating internally.

    In the meantime, please try again as the issue may have already resolved itself. I had no issues while going through the sign up procedure on my end.

    Thank you for your patience.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @szponix ,

    Thank you for the detailed report and for the thorough testing, it is very much appreciated.

    We are already aware of this issue and have opened an internal task to address it. A fix will be released as soon as possible.

    In the meantime, we recommend staying on version 7.4.4.2 until the fix is available to avoid the cookie translation data being overwritten.

    We apologize for the inconvenience and thank you for your patience!

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @wesleysilvairon ,

    Thank you for reaching out and for the detailed report.

    I am sorry to hear you are experiencing this issue. This type of error is usually related to the cookiedatabase.com server. I have already raised this internally and we will look into it to prevent any further occurrences.

    Could you please let us know if the issue is still appearing? If so, it would be very helpful if you could try clearing your cache and attempting the sync again.

    We will keep you updated as soon as we have more information.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @chengjianping ,

    Thank you for reaching out.

    Looking at the screenshot, the plugin consuming excessive server resources appears to be Elementor and Elementor Pro, not Complianz. We only provide support for Complianz, so for this specific issue we would recommend reaching out directly to the Elementor team or your hosting provider.

    Additionally, please note that Elementor Pro is a paid plugin and cannot be discussed on the WordPress support forum per its guidelines.

    For all the reasons mentioned above, this thread will be closed.

    Best regards,
    Antonio

    Plugin Support Antonio Candela

    (@antoiub)

    Hi @rayeason ,

    Thank you for reaching out and for the explanation.

    The short answer is that there is no functional difference, it is purely about placement. With Complianz WP.org version, the GTM script is injected in the body, whereas with a dedicated plugin like Header and Footer Scripts you have the flexibility to place it wherever you prefer.

    That said, using GTM through Complianz ensures compliance for the applicable jurisdiction, assuming your tags are correctly configured, which would be relevant if you ever need to implement GDPR or similar regulations in the future.

    So if you are happy with the body placement, you can safely remove the manual GTM script from the header and footer and rely on Complianz to handle the injection.

    I hope this helps.
    Best regards,
    Antonio

Viewing 15 replies - 46 through 60 (of 769 total)