I have a search-api-view where I use Views Megarow to edit nodes. This works quite well, but I get a warning as soon as I open the node-edit-form inside the Megarow.

"The form has become outdated. Copy any unsaved work in the form below and then reload this page."

The form is saved, everything seems to be ok. But it seems to indicate that there might be s.th. wrong with the submitted form-token ($form['#token']). Maybe it has something to do with my setting, but to me it seems to be more likely connected to Search Api. I have several search-api-views the warning appears on all of them, but I haven’t tested it on a other instance.

I'm trying to dig further into that problem, any hint would be appreciated.

Comments

semanthis created an issue. See original summary.

NWOM’s picture

Title: warning: The form has become outdated on Search Api View » warning: The form has become outdated

I'm having the same issue, but on normal content views.

LeDucDuBleuet’s picture

Same here, as soon as I activate the option "Override the node edit form with Views Megarow ", I get the the error "The form has become outdated...".

I tried with and without Bootstrap theme and with various JQuery versions, always the same error.

I really need to have the view refreshed after saving the form, any hint would be appreciated.

Thank you.

bechtold’s picture

I have the same issue when showing the node edit form in views megarow.
It seems to be working fine, but the message is shown as soon as the form is opened.
Also saving the form does work as expected, it feels like it is just showing the messages for no reason.

It might have todo with this: https://www.drupal.org/node/240828

ravimalviya2000’s picture

I have also find same error " The form has become outdated. Copy any unsaved work in the form below and then reload this page. "

ravimalviya2000’s picture

Please review.

AlfTheCat’s picture

Same issue here.

AlfTheCat’s picture

I managed to make this go away by disabling the */edit overrides at admin/config/user-interface/views_megarow.

However, now I get an ajax 200 error after saving... I'm kind of puzzled why a module with so many installs doesn't work. If I refresh the view manually then the information does appear to be updated.