Comment to 'logging in token'
Comment to logging in token
  • I'm going to try this too, by doubling the time.  I just turned off CSRF in the meantime and now all my pages dont get expired tokens when editing...
    whats strange is im not taking 86,000 sseconds or longer to edit them. usually about 3 minutes.
    unless thats being parsed as milliseconds... :) or picoseconds ;)
    also, Mergedia , unless you have mod rewrite installed, this error will happen with login, i had noticed that with my installation, and properly adding mod_rewrite to my apache fixed this. Because on login, via the settings in the htaccess file, unless you have re-write enabled, the only way into una is to circumvent the stale page (because re_write isnt working.) you have to reload the page, or click the nav bar and home to get a totally new page re-written, and you will be logged in because una finds the login cookie, but when you have set up re-write correctly within apache (i dont know how the ginx works), ... it will correctly parse the .htaccess files mod_rewrite rules, and load the homepage correctly after you log in.