Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Also get this one when a user tries to edit their own profile: "The form has become outdated. Copy any unsaved work in the form below and then reload this page."
Happens on a fresh edit and you can't get rid of the message.
Just using authcache, no extra caches like filecache, I feel like I've missed something. The user is just an authenticated user and I have authcache turned on for auth users.
Comments
Comment #1
RumpledElf CreditAttribution: RumpledElf commentedJust testing some more and this seems to be an ie thing too, it works fine on chrome but users simply can't edit their profiles on ie8. Big WTF right there. Do I need to give any more details?
Comment #2
simg CreditAttribution: simg commentedThis seems to be a more general issue that all forms don't (didn't) work with Authcache enabled.
I've fixed this (I think) with the following code in authcache_form_alter
Anyone who has any input to the possible implications of doing this would be welcome to chip in.
Comment #3
simg CreditAttribution: simg commentedComment #4
IWasBornToWin CreditAttribution: IWasBornToWin commentedI just installed version 7.x 1.3, and still having this issue. Any role with authcache can't edit or submit form data. They can't even add something to a shopping cart at a product page?
Comment #5
IWasBornToWin CreditAttribution: IWasBornToWin commentedJust tried with another role to see if it would make a difference (auth, was using admin). It didn't. Got these messages;
The form has become outdated. Copy any unsaved work in the form below and then reload this page.
An illegal choice has been detected. Please contact the site administrator.
Comment #6
znerol CreditAttribution: znerol commentedWhen you encounter the "The form has become outdated" error on 1.3 then most probably there is something wrong with your setup. The first thing you should check is whether you have JavaScript errors on your page (use Firebug or Safari/Chrome inspector and check the JavaScript console on the affected pages).
I close this issue now. Please open a new issue if necessary, this one is pretty old and the original problem has been solved long ago.