GDPR/CCPA Cookie Consent Banner Admin

Hi @ablears

Apologies for the delayed response, as @mikeinuk mentioned, robots.txt access is needed for the cookie scanner to function properly. It has to be able to check for scripts and cookies that live across your site in order to categorize and allow/disable based on a user’s interaction with the consent banner.

For more details on how it works, you can click on the link below
https://help.termly.io/support/solutions/articles/69000108859-how-does-the-cookie-scanner-work-

Hi @cywo

Sorry to hear about your frustrations, we had sent out 2 emails detailing the rollout plan approximately 3 months prior and just before the actual cutover of the plugin. The previous version was severely outdated by the time we took it over and was no longer compliant with GDPR and CCPA regulations, therefore it wasn’t offering you any legal protection.

The free version is still available to roll back to if that is your preference. Please note however that we are not responsible for any compliance related issue should you choose to do so.

Thank you

Hi Krissieg,

I just took another look at the new button implemented, it looks like you’re still missing the onclick portion.

Here is a screenshot of the live code on your site.
Preference center code

I would suggest moving the button out of the paragraph tags <p> or other divs. Inserting it into the footer is the most common placement for this feature.

Hi Krissieg,

Thank you for reaching out, after taking a look at your site along with the button code, we’ve identified the issue.

When modifying the preference center button UI, make sure to retain all of the class information. In this case, onclick=”displayPreferenceModal()” was deleted from your preference center button.

You can either regrab the code from the Embed preference center page or copy the default code below.

<button
  class="termly-cookie-preference-button"
  type="button"
  style="background: white; width: 165px; height: 30px; border-radius: 3px; border: 1px solid #5f7d9c; font-family: Roboto, Arial; font-size: 10px; color: #5f7d9c; font-weight: 600; box-sizing: border-box; cursor: pointer; padding: 0; outline: none;"
  onclick="displayPreferenceModal()"
>
    Manage Cookie Preferences
</button>

Thank you,
The Termly Team

Hi Theo,

Thank you for posting this workaround, we’ve notified our teams and they are looking into a more permanent solution as we speak. In the meantime, we will be adding this to our pinned post to inform other customers who are potentially facing the same issue.

– The Termly Team

• This reply was modified 2 years, 8 months ago by GDPR/CCPA Cookie Consent Banner Admin.

Understood – we appreciate you being a user, for however short it may have been.

In the future, if you decide to give our services a try, please let us know and we would be happy to set you up with a meaningful discount.

Best wishes,
The Termly Team

Hola @luisserrano,

Lamentamos escuchar sus frustraciones, como explicamos en el hilo de soporte fijo aquí, se comunicó a todos los usuarios el cronograma para pasar del complemento anterior al nuevo a través de la página de inicio del complemento y por correo electrónico. Además, puede encontrar instrucciones para volver a la versión anterior.

Sin embargo, el complemento anterior no cumplía con los requisitos de GDPR/CCPA, ya que no estuvo sincronizado con los últimos cambios normativos durante varios meses antes de nuestra propiedad.

El servicio de Termly es de uso gratuito, indefinidamente, con opciones pagas adicionales disponibles a su discreción. Esperamos que lo reconsidere y pruebe nuestro servicio antes de irse.

Los mejores deseos,
El Termly trimestral

Hi @fidohh,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hi @bonsaigil,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hi @thchoperpilot,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hi @babybitch1976,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hi @secretja,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

• This reply was modified 3 years, 1 month ago by GDPR/CCPA Cookie Consent Banner Admin.

Hi @jvsteen,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to new was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was and remains non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months prior to our ownership.

Termly’s service is free to use, indefinitely, with additional paid options available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hi @iainpurdie,

We’re sorry to hear about your frustrations, as we’ve explained in the stickied support thread here, the timeline for cutting over from the old plugin to the current was communicated to all users via the plugin’s home page and through email. In addition, you may find instructions for rolling back to the previous version.

However, the previous plugin was already non-GDPR/CCPA compliant as it had been out of sync with the latest regulatory changes for quite a few months.

Our service is free to use with additional paid options, available at your discretion. We hope that you will reconsider and give our service a try before leaving.

Best wishes,
The Termly Team

Hello, sorry to hear about your experience.

Unfortunately the previous version of this plugin was no longer compliant with GDPR. Developments in the law require websites to report what tracking mechanisms they serve and for which purposes, and offer the choice of which they want to receive to their site visitors.

While we don’t expect you to continue using Termly, we hope you take this into account with the new service that you choose.