• Resolved Martin Blumenfeld

    (@monkeypress)


    We’re still getting the security token errors with V2.0.6 installed. We have tried changing themes and disabling plugins without any success. The weird part is that this works on Safari and Firefox, but not with the latest version of Chrome. Any idea what’s going on here? I even tried disabling all of my Chrome extensions.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Can’t see any errors there with chrome.
    How did you change the appearence of the Privacy Bar ?

    • This reply was modified 6 years, 9 months ago by rcaetano.

    If you manually deleted your cookies from Chrome while logged in, in another tab – you’ll get this error.

    We just restarted Chrome and it was all fine for whatever reason.

    Thread Starter Martin Blumenfeld

    (@monkeypress)

    @rcaetano: We just added some custom styles to override the defaults.
    @patrickthagaard: Thanks! I think that was the issue.

    Hi, I think this bug is not solved.
    I’ve tried with Chrome, Opera and Brave and they all gave me that token error message. I don’t know what to do. I’m setting 10 websites with this plugin but if it does not work with chrome I fear that, for now, I have to switch to something else.
    Any update soon? Thanks in advance.

    Plugin Author Fernando Claussen

    (@fclaussen)

    The only three ways this would fail, as far as I know, is if:

    1- You blocked access to the wp-admin folder, password protecting it the wrong way or some other weird thing some users like to do

    2- The security token expired (less likely, unless you have the screen open for long hours)

    3- If you deleted the cookies while logged in. This creates a weird behavior in WP. It won’t find the auth cookie and will consider you logged out but at the same time, it will consider you logged in (you can access the dashboard). Just get a fresh start and this should be ok.

    Ok, thank you for the reply.

    Now it’s working fine. Thanks again

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘V2.0.6 Chrome Security Token Errors’ is closed to new replies.