Project

General

Profile

Actions

Feature #13229

closed

Epic #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

Added by Patrick Broens about 13 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Must have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-21
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Tags:
Complexity:
Sprint Focus:

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.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #13230: tt_content.search.20 should be done with the new FORM mappingRejectedPatrick Broens2011-02-21

Actions
Related to TYPO3 Core - Feature #12958: use Form for user registrationClosed2011-02-10

Actions
Actions #1

Updated by Oliver Hader over 12 years ago

  • Tags set to FormWizard
Actions #2

Updated by Oliver Hader over 12 years ago

  • Project changed from 135 to TYPO3 Core
Actions #3

Updated by Oliver Hader over 12 years ago

  • Category set to Form Framework
Actions #4

Updated by Oliver Hader over 12 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
Actions #5

Updated by Steffen Ritter about 12 years ago

  • Target version deleted (4.7.0)
Actions #6

Updated by Felix Kopp over 9 years ago

  • Parent task set to #61842
Actions #7

Updated by Björn Jacob over 8 years ago

  • Category changed from Form Framework to 1602
Actions #8

Updated by Björn Jacob over 8 years ago

  • Category changed from 1602 to Form Framework
Actions #9

Updated by Björn Jacob over 8 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.

Actions #10

Updated by Riccardo De Contardi over 7 years ago

  • Category set to Form Framework
Actions #11

Updated by Björn Jacob over 7 years ago

  • Category deleted (Form Framework)

As said, this has nothing to do with EXT:form ;)

Actions #12

Updated by Benni Mack over 7 years ago

  • Status changed from New to Rejected

not going to happen
=> FORM != felogin

Actions

Also available in: Atom PDF