A server error occurred during autosaving the current page.

Created on 8 October 2018, over 6 years ago
Updated 26 July 2024, 9 months ago

Autosave Form work only once.

Scenario:
1) I chose some content to edit. I write update of some field. It doesn't matter, if it is field with referenced entity, or just textarea.
2) I leave unsaved node edit form. For example I click to node view tab.
3) I go back to edit form. There is message: "A version of this page you were editing at Oct 08, 2018 07:25 was saved as a draft. Do you want to resume editing or discard it?" . So I click on Resume editing. Immediately i get error "A server error occurred during autosaving the current page."
4) I go to Recent log messages. There is error: "Drupal\Core\Database\IntegrityConstraintViolationException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'node_tipp_edit_form-form-IGJqh2KMEged1CT_8J1A27dQ9LvrE056xlPWvQh' for key 'PRIMARY'"

Module has very strange behaviour. I don't understand, why are in table autosave_form_entity_form all changes. There isn't possible choice older one. Everytime are loaded last changes, so why are stored all changes? For website with one author should be fine, but if you has more authors and more content, than it is suicide.

Module doesn't work proprerly with Expanding Textareas too. But it should be problem inside Expanding Textareas .

🐛 Bug report
Status

Active

Version

1.0

Component

Entity form autosave

Created by

🇨🇿Czech Republic siva01

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom oldspot

    We have the same problem on one of our sites - leaving the node edit form page open results in that modal box opening with a 'server error' message.
    The network tools show 2, 3, 4 or more successful Ajax resuests to "/node/NID/edit?ajax_form=1&_wrapper_format=drupal_ajax" and then suddenly it will respond with a request that lasts 1 minute and a 503 response (that happens to be our timeout).

Production build 0.71.5 2024