Bug #19421
Setting password for a new BE user changes the field value to "undefined"
| Status: | Closed | Start date: | 2008-10-06 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Oliver Hader | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 4.2 | Is Regression: | ||
| PHP Version: | 5.3 | Sprint Focus: | ||
| Complexity: |
Description
While creating and/or editing BE users the value of the password field will always switch to "undefined" after leaving the focus of the input field.
This doesn't seem to change the real value which will be saved to the DB later on at all, but since you can only find out about it by logging in with the specific BE user's data, it's quite annoying.
TYPO3 4.2.2
(issue imported from #M9494)
0009494.patch
(1.2 kB)
Related issues
History
#1 Updated by Oliver Hader almost 7 years ago
The reason for the bug is, that tbe_editor.js was loaded in the HEAD section of the HTML document - what isn't bad in general. However, some parts in the core define a "typoSetup" object and create an instance in the variable TS.
I removed tbe_editor.js from the HEAD section again - thus, it's going to override the typoSetup object. For this case it's how it was before - a better solution would require more changes and thus only for TYPO3 4.3.
Please test and give a short feedback. Thanks!
#2 Updated by Dan Osipov almost 7 years ago
I can confirm the bug, and can confirm that its annoying.
#3 Updated by Frank Weindel almost 7 years ago
typo3\alt_doc.php Lines 467 to 470:
function typoSetup () { //
this.uniqueID = "";
}
var TS = new typoSetup();
are overriding the typoSetup object that is defined in typo3\jsfunc.tbe_editor.js as:
function typoSetup () {
this.passwordDummy = '********';
this.decimalSign = '.';
}
var TS = new typoSetup();
Thus TS.passwordDummy is undefined when the script executes to hide the password field.
#4 Updated by Oliver Hader almost 7 years ago
Frank, exactly - that's why the jsfunc.tbe_editor.js file has to be loaded after that declaration.
#5 Updated by Oliver Hader almost 7 years ago
This problem must be solved in combination with issue #19423 - please look there for patches against Trunk and TYPO3 4.2.2