Bug #88637
closedTCA setting onChange="reload" can lead to new record duplicates on slow connections
100%
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.
Updated by Susanne Moog over 4 years ago
- Category changed from Backend API to Backend JavaScript
Updated by Gerrit Code Review over 4 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/63623
Updated by Gerrit Code Review over 4 years ago
Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/63624
Updated by Andreas Fernandez over 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset d1bd824b1a98652b25e76efc0f61f101147237b1.