Cookie Banner Does not Work

  • Resolved finai

    (@finai)


    2 weeks, 3 days ago

    Hello Complianz Team,

    I am experiencing a severe rendering issue with the Complianz cookie banner on my website. The banner completely loses its styling and layout, rendering as a broken, unstyled HTML list pushed completely to the bottom of the page, below the footer. Additionally, the floating “Manage Consent” button is entirely missing.

    After inspecting the DOM and the page source, I have isolated the conflict to LiteSpeed Cache and QUIC.cloud optimizations.

    Here are the specific findings from my HTML source:

    1. UCSS (Unique CSS) Stripping: QUIC.cloud UCSS is active. Because the Complianz container initially loads with the cmplz-hidden class, UCSS appears to classify the banner’s CSS as “unused” and completely strips it from the critical CSS payload.
    2. JS Delay/Defer: The inline scripts and the main Complianz JS are being intercepted by LiteSpeed’s JS Delay feature. The script tags are being rewritten as <script type="litespeed/javascript">, which freezes the banner’s logic until user interaction.
    3. Browser Inconsistencies: The banner rendering fails entirely on Desktop (all browsers) and Mobile (Chrome/Firefox). However, it ironically works perfectly on Vivaldi Mobile, likely because Vivaldi’s native ad-blocker is blocking LiteSpeed’s JS delay scripts, allowing Complianz to load natively. But even in Vivaldi mobile the floating consent button is missing.

    Environment:

    • Complianz Premium v7.6.0
    • Server: LiteSpeed
    • Caching: LiteSpeed Cache (with QUIC.cloud UCSS and CCSS enabled)

    Troubleshooting attempted: I have already tried adding basic exclusions (e.g., complianz, cmplz) to the LiteSpeed Cache JS/CSS tuning settings, but the aggressive Guest Mode and UCSS features seem to bypass these basic exclusions.

    Since I lack the deep technical expertise to reconfigure the server-side cache architecture without breaking my site’s performance scores, I am requesting your assistance. Could you please provide the exact strict exclusion rules needed for LiteSpeed Cache?

    Thank you for your time and support.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Antonio Candela

    (@antoiub)

    1 week ago

    Hi @finai ,

    Thanks for the breakdown and for reaching out. Two things on how best to help you here:

    First, since you’re on Complianz Premium, and since the WordPress.org forum rules don’t allow us to provide support around paid plugins (including third-party premium tools like LiteSpeed/QUIC.cloud) on this forum, the right place for us to dig into your specific configuration is our own ticketing platform. Please sign up there and open a ticket, you’ll find it on our website. That way we can go through the exact exclusion rules with you directly.

    In the meantime, this guide will help you identify which Complianz scripts and endpoints to exclude from JS delay/defer and CSS optimization. It applies to caching/optimization plugins in general for both versions of Complianz, LiteSpeed included: https://complianz.io/javascript-delay-in-wp-rocket-and-other-caching-and-optimization-plugins/

    For the reasons above, I’ll be closing this thread, but we’ll gladly continue and resolve this with you through our ticketing system.

    Thanks again, and talk soon.

    Best regards,
    Antonio

    Moderator Support Moderator

    (@moderator)

    1 week ago

    For pro or customer support, please contact the developer on their site. This includes pre-sales information.

    As the developer is aware, customers may not be supported on this site.

    https://wordpress.org/support/guidelines/#do-not-post-about-commercial-products

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Cookie Banner Does not Work’ is closed to new replies.