Fork me on GitHub

Invalid authkey problems in postnuke  Bottom

Go to page [-1] 1 - 2:

  • It would appear that the 'proper' way to implement constantly changing functionality is via a insert. An insert isn't cached but executed every time - so only the 'static' part of the template is cached.

    So an authkey would look like as follows (assuming we added the function insert_genauthkey somewhere accessable).

    Code

    <input type="hidden" name="authid" value="<!--[insert name="genauthkey" module="Users" ]-->" />


    However, obviously, this isn't backwards compatible.

    -Mark


    --
    Visit My homepage and Zikula themes.
  • Ah, i already wondered Smarty don't avoid the caching by default for that commands.

    Well, i think backwards compatibilty must be skipped here, because in that
    case a explicit warning in the docs can solve the issue. Thats the implicit
    nocache i missed to find.

    The important point is to fix the broken logic with the cache, because the
    cache system itself works like a charm. I have it enabled now for a week and
    the site feels even under load pretty smooth.

    The full cache through theme to pnrender with Smarty on the "end" *is*
    definitly a major part of PN8 feature portfolio.

    I am not sure but ATM i would say with this topic solved it works so far flawless,
    except one thing (sorry to point it out):



    That will also give pretty messy output sometimes because it get cached too.
    How to solve thaT?
  • jami

    i've noticed with RC3 some random Invalid authkey (modification are always taken), but pnRender and Theme caching are not enabled


    Agree.

    I can verify this... an SVN from yesterday (dont have the rev number off hand, but from the 4th)

    pnRender:
    compliation check is true
    Force compilation is false
    Enable caching is false

    I can login from a browser okay, if I log out, I cannot login. I can login from another browser, logout-locked out. et cetera, et cetera.. IE7 FF2 FF3 Opera9 NN9.. xp vista ubuntu7.10






    --
    David Pahl
    Zikula Support Team
  • We got same problems... In any case deleting cookies will help.

    We have the SMF forum sharing the cookie/session, so i was a bit careful
    reporting it by fearing a side effect, but it never happend over weeks with
    a RC2 test site.

    THe strange thing is that you get no error message or warning and often the logout
    is denyed.

    Whatever: I an not sure this is related to a change in RC3 rendering RC2 cookies useless.

    That means: I have the feeling that bug touches people who visit our old RC2 site,
    still having an outdated cookie from the old site. I am not sure about it, but i
    noticed the 2-3 people reporting it was also on the old site.
  • With caching off I can't reproduce a problem. There haven't, that i'm aware of, been any changes in the cookie/session handling code between RC2 and RC3. I've logged in and out multiple times using different browsers to test with and on all occasions the login process has worked fine.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • I have a site where i can't login anymore...

    michtoen

    The strange thing is that you get no error message or warning and often the logout
    is denyed.

    This is because after the first logout, each click on the site is a new session. I see that each click is a new registry in the session_info table, and the error messages are lost as the sessions... checking that table, there are the AuthKey failed error message, but is not showed because the session is lost and a new register is generated (with no messages, obviously).

    I think i can you give the access to this site Mark and debug this issue in this server... i guess that there's some responsability in the server configuration too... but it's strange.

    --
    - Mateo T. -
    Mis principios... son mis fines
  • Mateo,

    Yes please. If you can you let me have access to a site showing the problem that would be great.

    -Mark

    --
    Visit My homepage and Zikula themes.
  • I have had the issue with 2 sites, both SVNs one pre RC3... but close... the other post RC3, I have never actually used the RC3 release.

    I get the error message if I refresh the page then try to login.

    Sending you my creds, Mark.


    --
    David Pahl
    Zikula Support Team
  • Hi, on my page. I am having random Invalid authkey problems even if my users don't press back. It happens when they hang around for too long on pages that need submitting like when they are submitting a news article.

    Is this the same issue as the user above posted?
  • I doubt it, it is probably just a session time out.

    --
    David Pahl
    Zikula Support Team
  • Kenshino

    Hi, on my page. I am having random Invalid authkey problems even if my users don't press back. It happens when they hang around for too long on pages that need submitting like when they are submitting a news article.


    I could also be because they have two windows open - both windows share the same authkey.
  • JørnWildt

    Kenshino

    Hi, on my page. I am having random Invalid authkey problems even if my users don't press back. It happens when they hang around for too long on pages that need submitting like when they are submitting a news article.


    I could also be because they have two windows open - both windows share the same authkey.


    Does the 2 window thing apply to having both windows open the same page or do different pages set it off too?

Go to page [-1] 1 - 2:

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