Project

General

Profile

Actions

Bug #77729

closed

Story #69617: FormEngine bugs

Save Button must be disabled until formengine form is fully loaded

Added by Sascha Egerer over 7 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2016-09-01
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

If your computer is too slow (or you are to fast) you can lock out yourself when editing you usersettings.
The problem is that JavaScript manipulations are done on the password field. If you hit the save button before that javascript stuff is done you'll lock out yourself as a new password is generated using you password hash as password.

Steps to reproduce:

  • Open the backend as admin
  • Go to the backend users module
  • Edit your own user
  • And then be very fast and click the save button
  • Now log out and try to login - that wont work (or just compare the password hash in the database before and after)

A solution could be to disable the save button until everything is initialized.


Related issues 4 (0 open4 closed)

Related to TYPO3 Core - Bug #77942: Double click on save button creates two records.Closed2016-09-14

Actions
Related to TYPO3 Core - Bug #77944: Duplicate FE-Users on save-and-closeClosed2016-09-14

Actions
Related to TYPO3 Core - Bug #77469: Duplicates of new frontend- and backenduser record when using IE11Closed2016-08-10

Actions
Related to TYPO3 Core - Bug #80672: Saving problems in Chrome 57+Closed2017-04-04

Actions
Actions #1

Updated by Sascha Egerer over 7 years ago

  • Complexity set to medium
Actions #2

Updated by Riccardo De Contardi about 7 years ago

  • Parent task set to #69617
Actions #3

Updated by Markus Klein about 7 years ago

It does not suffice to only shed the save buttons. Also typing too early in a text field can already cause troubles as the related issues show.
I would rather say we need to disable the whole frameset.

Actions #4

Updated by Riccardo De Contardi almost 7 years ago

  • Related to Bug #80672: Saving problems in Chrome 57+ added
Actions #5

Updated by Markus Klein almost 7 years ago

  • Status changed from New to Closed
  • Target version deleted (next-patchlevel)

With #80672 we will implement my suggestion from above. Closing this ticket therefore.

Actions

Also available in: Atom PDF