Feature #13229
closedEpic #61834: Create future proof Content Element with strong default
Task #61836: Reorganize Content Element properties within backend Extension
Task #61842: Refactor CSS-Styled-Content + Content Elements
tt_content.login.20 should be done with the new FORM mapping
0%
Description
Problem:
Currently the standard CSS_Styled_Content login form, tt_content.login.20 is using the old mapping. This should be changed, so it uses the new mapping.
One of the problems with using the new mapping is the prefix is always used in the field names. It should be configurable to turn the prefix off. In the core the login logic is done in the class 't3lib_userAuth'.
Also check how the form handles the situation when somebody is already logged in. It might be we need a preprocessor for this, so the whole form will be skipped when the user is logged in.
Updated by Oliver Hader about 13 years ago
- Project changed from 135 to TYPO3 Core
Updated by Oliver Hader about 13 years ago
- Tracker changed from Bug to Feature
- Target version set to 4.7.0
- PHP Version set to 5.3
- TYPO3 Version set to 4.6
Updated by Björn Jacob over 9 years ago
- Category changed from Form Framework to 1602
Updated by Björn Jacob over 9 years ago
- Category changed from 1602 to Form Framework
Updated by Björn Jacob about 9 years ago
- Category deleted (
Form Framework) - Status changed from Accepted to New
- Assignee deleted (
Patrick Broens)
I don't think that this is a EXT:form issue.
Updated by Riccardo De Contardi over 8 years ago
- Category set to Form Framework
Updated by Björn Jacob over 8 years ago
- Category deleted (
Form Framework)
As said, this has nothing to do with EXT:form ;)
Updated by Benni Mack about 8 years ago
- Status changed from New to Rejected
not going to happen
=> FORM != felogin