Fork me on GitHub

The dreaded "Sorry! Invalid authorisation key ('authkey')."  Bottom

  • Is there a way to sort this out when it seems to have completely hijacked the site?

    Zk 1.2.7

    There's a couple of threads which address this issue, but I am having no luck at all.

    Following a comment I saw, where can I find the field in the Database that switches on force (re)compilation of Theme or Render in the Admin Settings?

    Although I have had this message pop up occasionally, I have never before had such a dramatic lock out. It's a show stopper and no mistake.

    Need to find a way asap.

    BTW, does the Zikula Recovery Console still exists and is it still functional for Zk 1.2?

    This could cause a great deal of hassle if I can't sort it (yesterday...)

    Cheers.
  • This problem is fixed in 1.3.x where the CSRF protection system has been overhauled and reimplemented. There is no reliable way to get around the problem in 1.2.x without losing the security functionality.

    --
    Guite | ModuleStudio
  • Thanks Guite. There is some comfort in that, but if it means losing some/all security functionality to get access, then so be it.

    Are there any settings which reduce the risk of this behviour (or perhaps more importantly increase the risk). This is a production site where down time could hurt...

    It has never happened to me so ruthlessly before, so I am rather anxious now...

    Cheers.

    p.s. What about the Security Centre Settings which are directly related to sessions etc, and can have a number of different values. I don't pretend to understand them all in detail, but do any of these settings contribute tworads the tendency for Zk to go invalid authkey, and can you minise the time that it takes for it to resolve?
  • 0 users

This list is based on users active over the last 60 minutes.