Bug #77469
closedDuplicates of new frontend- and backenduser record when using IE11
0%
Description
Creating an new Website User (fe_user) with IE11 results in two new records.
Web -> List: "new record", entering data -> "save and close"
Tested with IE11 in TYPO3 7.6.0, 7.6.4, 7.6.10 and 8.2.1
Files
Updated by König David about 8 years ago
I can confirm this Bug, and add some more Informations:
If you open the Developer-Console in IE11, the problem no longer occurs, also if you now close the Console.
If you Restart the Browser, the problem occurs again.
Updated by Florian Wessels almost 8 years ago
- Subject changed from Duplicates of new frontenduser record when using IE11 to Duplicates of new frontend- and backenduser record when using IE11
Same behaviour for BE-Users (list and module)...
Updated by Riccardo De Contardi almost 8 years ago
- Category set to Backend User Interface
Updated by Markus Timtner almost 8 years ago
Hi there, I can't confirm this behaviour,
it doesn't occur with me in IE11, or in Edge.
I tested this with single click and double click on save&close.
Updated by Markus Timtner almost 8 years ago
...but I can confirm this behavior when clicking: "save and create a new record"!
Updated by Markus Timtner almost 8 years ago
Now I can cofirm this behavior for "save&close", too.
This behaviour isn't related to #77942, since I tested it with the patch applied :/
Updated by Riccardo De Contardi over 7 years ago
I can confirm the issue with IE11 11.0.9600.18537 on Windows 7 (Save & Close)
Updated by Benjamin Kott over 7 years ago
- Status changed from New to Accepted
- Priority changed from Should have to Must have
- Sprint Focus set to On Location Sprint
Updated by Oliver Hader over 7 years ago
- Status changed from Accepted to In Progress
- Assignee set to Sven Laser
Sven is working on this issue during the next few days...
Updated by Anja Leichsenring about 7 years ago
- Sprint Focus deleted (
On Location Sprint)
Updated by Gregor Schreier over 6 years ago
This issue is still there in LTS 8 latest Release. Annoying bug, especially in the corporate environment if the browser is specified.
Why is there a token for check if an request is valid but not validated against double submit. Double-Submits could be avoided by storing formTokens in BE-Session and Unsetting this tokens after Submits.
This could prevent double submits by design.
gregor
Updated by Riccardo De Contardi over 5 years ago
This issue is no more reproducible on TYPO3 9.5.4
- I tried with both IE11 and Edge on Windows 10
- I tried with both creating a fe_user, click on save and then close; and with creating a fe_user, click close and then choose "save and close
Updated by Julian Hofmann over 5 years ago
Can confirm: this issue is no more reproducible on TYPO3 9.5.4 (Win7, SP1; IE11)
In my opinion, the issue could be closed.
The bug is a little bit annoying, but not security relevant. TYPO3 v8 is already in "Priority bugfixes"-mode, in v9 it is fixed/not reproducible.
Updated by Riccardo De Contardi about 5 years ago
- Status changed from In Progress to Closed
- Assignee deleted (
Sven Laser)
Sorry for my late answer on this one; closing it.
If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions like 9 or 10 please reopen it or ping me.
Thank you.
Updated by Florian Wessels almost 5 years ago
- File Bildschirmfoto 2019-12-11 um 10.06.30.png Bildschirmfoto 2019-12-11 um 10.06.30.png added
- TYPO3 Version changed from 8 to 9
Unfortunately this is still reproducible on Windows 10 and IE 11 (11.476.18362.0) when clicking the save (not the close) button in the "create new" view.
TYPO3 Version is 9.5.11 (not tested with 10.2)
Updated by Riccardo De Contardi almost 5 years ago
- Status changed from Closed to New
Still not able to reproduce it on Windows 10 and IE 11 (11.48.17134.0) - using TYPO3 9.5.11 :(
Could it be some odd race condition?
Updated by Florian Wessels almost 5 years ago
Seems so, as it is not reproducible every time (I have tried to save five users, only one of them was created twice).
However, I am not sure anything should be done here. It appears to occur only in isolated cases.
Updated by Riccardo De Contardi almost 4 years ago
Is this issue still relevant? Next TYPO3 version (11) will only support Edge.
Updated by Florian Wessels almost 4 years ago
This is no longer relevant for me - can therefore be closed.
Updated by Riccardo De Contardi over 3 years ago
- Status changed from New to Closed
I am closing this one for now;
If you think that this is the wrong decision, please reopen it or ping me and I'll do.