Hi efi
This sounds odd. To the best of my knowledge we do not manipulate or remove classes.
Could it be that the classes are added by scripting that is being blocked by Cookiebot, or are the classes in fact on the elements in the raw source, only to disappear when the page renders?
Automatic blocking of cookies relies on our solution successfully scanning your website. This is likely not being done if it’s a staging site unless you have had authentication for the scanner setup by Cookiebot.
I would suggest you a greeting at support@… with more detail and perhaps a way for us to take a look at your dev site.
Thanks!
Thread Starter
efi123
(@efi123)
Hi,
I have escalated this to the support@.. tier.
I will answer your questions here in case someone else gets in a similar situation:
Could it be that the classes are added by scripting that is being blocked by Cookiebot
Yes, I believe this is the case.
Automatic blocking of cookies relies on our solution successfully scanning your website. This is likely not being done if it’s a staging site unless you have had authentication for the scanner setup by Cookiebot.
Yes it is a staging site, but it lies in a subfolder of our original website. And I believe it has had all the needed authentication, successful cookie scans from the Cookiebot service.
I could provide you with a key to review the front-end, but not the back-end of our setup.
Hope that helps.
@efi123 Thanks for the suggestion, but we are not allowed to access login protected sites according to the WordPress rules.
@efi123 any news, or can we mark this as resolved?
Thread Starter
efi123
(@efi123)
Seems to fix this after switching from “automatic” to “manual” mode.
Resolved.