Project

General

Profile

Actions

Bug #88637

closed

TCA setting onChange="reload" can lead to new record duplicates on slow connections

Added by Christian Eßl over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend JavaScript
Target version:
-
Start date:
2019-06-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Tested with TYPO3 9.5.8 and the "Form" Content Element.

How to reproduce:
  • Throttle your network to a slower connection. (Like 3G in Chromes Performance panel)
  • Go to the Pages module and use the New Content Element wizard to start creating a new "Form" Content Element.
  • Do not save the record yet. Switch to the tab "Plugin" and choose a form definition.
  • TYPO3 will now ask for a confirmation to refresh the form. Click "OK".
  • Now IMMEDIATELY click "Save".

If the connection was slow enough, there should now be 2 identical content elements saved on the page.
This apparently happens, because TYPO3 will automatically save a content element when using a onChange="reload" select field. But because of the slow connection, TYPO3 hasn't finished the ajax request for saving the record in the background yet and when the editor immediately clicked "Save", a second ajax request for creating a new record was triggered.

Actions

Also available in: Atom PDF