ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

This form has expired. Please refresh and try again

March 01, 2014 6:35pm

Subscribe [11]
  • #1 / Mar 01, 2014 6:35pm

    djpthurso

    26 posts

    Upgrading from 1.7.3 to 2.8.0 and after the conversion I try to login and get the following message - “An Error Was Encountered This form has expired. Please refresh and try again.”

    I have Googled this and the only reference I can find is on the Developers forum here but obviously I can’t see what was said.

    Any suggestions of a way to sort the error out? Running on a local host with wampserver on Windows 7.

    Thanks

    David

  • #2 / Mar 02, 2014 12:49pm

    Rob Allen

    3108 posts

    First thing to try is clearing the EE cache in /system/expressionengine/cache (remove all the folders inside)

    Also worth deleting browser cookies and browser history (or just the items relating to the site).

  • #3 / Mar 02, 2014 5:31pm

    djpthurso

    26 posts

    Sussed it out, needed to add AcceptPathInfo On to the Apache config. Thanks Rob

    Ignore that, not sorted at all was loging on to the internet based one rather than localhost, it’s been a long day.

    David

  • #4 / Mar 03, 2014 3:53am

    djpthurso

    26 posts

    Just an update, clean install of 2.8 works fine on localhost , upgrade from 1.7.3 to 2.8 works on a remote site ie www but still getting the form expired message on the 1.7.3 upgrade on the localhost.

    David

  • #5 / Mar 03, 2014 11:21am

    djpthurso

    26 posts

    Eventually got sorted, went away back to the beta version that was on the go with 1.7.3, upgraded from that then worked my way up through the releases.

  • #6 / Mar 26, 2014 1:49pm

    leadsuccess

    408 posts

    I have run into this issue also but updating from v.2.1.0 to v2.8.1.  Has anyone else come across this issue and has a fix? I have been at it for hours and have no ideas other than to simply rebuild the site which will take me a solid 2 days to recreate.

  • #7 / Mar 27, 2014 12:39pm

    leadsuccess

    408 posts

    I found a fix, anyone else that needs it can find it here.

  • #8 / May 08, 2014 5:01am

    Giraffentoast

    152 posts

    What the hell, Ellislab…

  • #9 / May 12, 2014 11:44am

    I’m experiencing this same problem on 2.8.1 - the problem with leadsuccess’s fix is that it leads to other issues, like this one:

    http://ellislab.com/forums/viewthread/244337/#1064230

  • #10 / May 15, 2014 8:16pm

    Mr. R. Balboa

    7 posts

    I’m getting “This form has expired. Please refresh and try again” also denying me access to CP after server move - EE281
    Clearing browser cache and cookies doesn’t help or any solutions above. Getting to a stage where I’m afraid to move anything EE related. Also got a #1064 migrating the database. Headaches…..As an aside whats the most stable version of EE that uses the Grid Field? 2.7.X?

    Logged 2 bug reports:

    https://support.ellislab.com/bugs/detail/20367
    https://support.ellislab.com/bugs/detail/20366

  • #11 / May 21, 2014 11:46am

    kelseyads2

    98 posts

    I’m getting this on a client’s site upgrade as well. Getting a blank page on the front-end and had disallowed characters issue on /system, but resolved that with this fix: https://support.ellislab.com/bugs/detail/20192

    Now I’m seeing the login form, but get “This form has expired” error when submitting. Still have a blank screen on front-end.

    Followed upgrade instructions to the letter for upgrading from 2.4.0 and everything appeared to go smoothly, but entire site is broken after the update.

    Frustrating…

  • #12 / May 25, 2014 8:55pm

    cranacsystems

    35 posts

    I ran into this issue as well upgrading from 2.6 to 2.8.1.

    My issue is specific to Solspace Super Search form on the public facing site. So far I got around it by setting GET method for the search query instead of POST.

    Then I tried adding <input type=“hidden” name=“XID” value=”{XID_HASH}” /> to my form with a post method and it works but strangely it seems to turn post method into get method appending a query string to the URL.

    Is that normal? Any hint is appreciated.
    L.

  • #13 / Jun 03, 2014 5:33pm

    amityweb

    162 posts

    Upgraded EE to 2.8.1 and Cartthrob 2.5, and now also get this when processing Sagepay payments

  • #14 / Jun 05, 2014 9:39am

    This works for me on local dev:

      $config[‘cp_session_type’] = “s”;
      $config[‘disable_csrf_protection’] = “y”;

  • #15 / Jun 05, 2014 9:51am

    amityweb

    162 posts

    I added this in the config file:

    if(stripos($_SERVER["REQUEST_URI"],'/themes/third_party/cartthrob/lib/extload.php/sage_s') !== FALSE)
    {
     $config['disable_csrf_protection'] = 'y';
    }

    So it should only disable csrf for this callback URL from Sagepay. Got it from here http://ellislab.com/forums/viewthread/182631/.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases