We could not verify the security token. Please try again.

Where are they accepting it? From the privacy bar?

I accepted it on your site and it worked fine. I did it just now. As a logged out user.

Yes, from the homepage. I’ve seen the same bug logged out with Firefox

I cannot replicate. It is working for me. I just tried.

Same for me right now

Perhaps the new update solved it.

Thanks anyway, and sorry for the inconvenience

Unmarked as resolved then ??

Hi @flashpopstoni,

I introduced a new field in 1.4.3 that I left as text instead of hidden for testing purposes. I forgot to switch it back to hidden before I published.

I just pushed 1.4.4 live now to fix that.

Regarding the error, if you check tracking it works? I’m wondering why that is one of the steps.

Can you list me the plugins you have installed and the versions?
Can you also try disabling your plugins, test if it works and then re-enable one plugin at a time until it fails? That way we can determine what plugin is causing an incompatibility issue and it gets easier to fix.

@flashpopstoni,
Btw, I was also able to save my preferences at your site. I’m wondering if similar to woocommerce I need to take some specific action before saving to trigger the error.

Hi @flashpopstoni

Have you tried disabling the plugins and switching to a default theme and trying again? Then enable one at a time until you find the problem.

1. You can see an example of this here: https://gdpr-wp.com/knowledge-base/enabling-or-disabling-functionality-based-on-consent-and-cookies/.

2. I’m not sure if that is a problem or not, it is particular to your use case.

3. If you use our logic for handling this (like in the sample provided in 1.) the plugin will remove the cookie if it is not allowed.

4. Probably. I wouldn’t know what those differences might be, but for instance, if you wanted to make analytics anonymous instead of removing it entirely, there is a parameter you enter in tag manager that will do that for you. You gotta do some research.