Issue Bug Closed

#107681Save button remains enabled during onChange=reload, allowing unintended multiple saves

Mikel Wohlschlegel 10/13/25, 09:23 updated 12/02/25, 13:05

Description

When editing and saving pages or content elements in TYPO3, the “Save” button is correctly disabled and a spinner is shown during a regular save operation. However, when the TCA configuration onChange = reload triggers a form reload, the “Save” button remains enabled. If the reload is slow, editors may click “Save” again, which can create multiple content elements unintentionally. This could be prevented by disabling the “Save” button during onChange = reload as well.

Expected Behavior

  • When onChange = reload triggers a form reload, the “Save” button (and related submit actions) should be disabled until the reload completes.
  • Optionally show a loading indicator/spinner, similar to the regular save flow, to provide user feedback.

Actual Behavior

  • With onChange = reload, the “Save” button stays enabled.
  • There is no visual feedback during longer reloads
  • Multiple clicks on “Save” are possible and can lead to multiple entries (e.g., duplicate content elements).

Steps to Reproduce

  1. Configure a TCA field with onChange = reload (e.g., in a content element).
  2. In the backend, open a content element or edit a page.
  3. Change the value of the field so that onChange = reload is triggered.
  4. While the reload is still in progress (e.g., on a slow connection or under server load), click “Save” — multiple clicks are possible.
  5. Result: Multiple records are created and/or the record is saved multiple times.

Reviews 4