Antonio Candela

Hello Gabe,

Thank you so much for your time and trust in looking into this.

AdBlockers like uBlock Origin is one of those content blockers that occasionally interferes with Complianz, though it doesn’t happen consistently across all sites. As you noticed, the best solution in those cases is simply to exclude Complianz from the extension or disable it.

I’m glad it’s all sorted out now, and again, thanks for the follow-ups, they were very helpful.
If you need anything else, feel free to reach out anytime by opening another thread.

Best regards,
Antonio

Hi Gabe @geekayhu ,

Thank you for the detailed report and for sharing the screencast, that’s very helpful.
From what we can see, there seem to be two separate issues at play here:

1. A redirect involving the ?page=complianz&websitescan#settings parameter might be forcing a specific state in the UI, though please note that we removed the forced redirect some time ago, so this behavior is unusual.
2. The app itself not loading properly in the backend is likely the reason you’re seeing a blank or grey screen.

Here are a few suggestions that might help move things forward:

• Could you provide a screenshot with the browser console open? This will help us check for any JavaScript or network errors that could explain why the app isn’t rendering.
• Since you’re using SiteGround, it’s possible that their caching system is interfering with the plugin. Clearing the SiteGround cache might help restore proper backend behavior.
• You mentioned being able to bypass the issue by manually removing the &websitescan part from the URL. In this case, we suggest going to Tools > Data in Complianz and enabling the option “Clear all data from Complianz on uninstall”, then saving. After that, perform a full uninstall and reinstall of the plugin to reset it completely, this may resolve the redirection and loading issues.

Let us know if you’re able to try these steps, and feel free to share any console output. We are here to help.

Best regards,
Antonio

Hello @mahjoubko ,

Thank you for reaching out.

Since you’ve changed the site language, you’re probably missing the translations from WordPress.org.
Could you please check if any translations are available to download under Dashboard > Updates > Translations? There should be some available.

Once the translations are updated, you can reset the consent banner; it will then use the updated strings.

I hope this helps.
Best regards,
Antonio

Hi @ra2or ,

Thank you for reaching out.

Could you clarify what exactly you’d like to achieve with the custom link? If you are trying to open the banner, accept cookies directly, or revoke consent, we do offer some classes that can be used to trigger certain actions via custom links or buttons. Here are the available classes:

• Open/manage consent banner: cmplz-show-banner
• Accept all cookies: cmplz-accept
• Revoke consent: cmplz-deny

If you’re trying to go beyond these actions, we also provide shortcodes for more advanced use cases, you can find them all here: https://complianz.io/used-shortcodes-by-complianz/.

I hope this helps.
Best regards,
Antonio

Hello @umberto69 ,

Thank you for reaching out.

If your goal is to transfer cookie consent, then yes; but please note that this option might not be useful in your specific case. I recommend checking out this article where we explain cross-domain cookie consent in more detail: https://complianz.io/cross-domain-cookie-consent.

There are some limitations with this setting, and keep in mind that if your subdomain serves a different purpose, accepting the cookie banner on the main site may not be considered best practice.

I hope this helps.

Best regards,
Antonio

Hello @anevins ,

Thank you for reaching out and for the detailed points, they’re very helpful :).

We’re currently working on several accessibility-related improvements, and some of the issues that our community helped point out have already been fixed and are ready to be included in the next release. We’re just wrapping things up to make sure we don’t miss anything related to accessibility moving forward. You can find a summary of our efforts on this page: https://complianz.io/accessibility.

If you’d like, you’re welcome to submit your suggestions and fixes via GitHub. In any case, no worries! I’ve already submitted everything to the team for a thorough review.

Thank you again for your feedback!

Best regards,
Antonio

• This reply was modified 10 months, 3 weeks ago by Antonio Candela.

Hi @koupmi,

It appears that you have activated the TCF banner. This typically happens when, during the wizard, you answered “Yes” to the question “Does your website contain scripts for advertising purposes?” and selected one of the TCF framework options under “Choose the appropriate frameworks needed for your configuration.”

When the TCF framework is enabled, the banner is replaced with the TCF consent layer, which is specifically designed for websites displaying ads. The appearance and behavior of this banner are controlled by IAB regulations, which means that certain fields are no longer editable manually.

If your website does not display ads, you can safely choose “No” in that step of the wizard. This will revert the banner to the standard Complianz banner, where you’ll be able to edit the text freely as expected.

Lastly, even though the feature (and its settings) is technically present in the free version, it is not usable unless the premium version is activated. As such, this falls under the category of premium features, and per the WordPress.org forum guidelines, we’re unable to assist you here.

We will therefore close this thread and kindly ask you to read this one: PLEASE READ BEFORE YOU POST AN ISSUE.

I hope this helps.
Best regards,
Antonio