Feature #13230
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.search.20 should be done with the new FORM mapping
Status: | Needs Feedback | Start date: | 2011-02-21 | |
---|---|---|---|---|
Priority: | Must have | Due date: | ||
Assigned To: | Patrick Broens | % Done: | 0% |
|
Category: | Form Wizard | Spent time: | - | |
Target version: | - | |||
PHP Version: | 5.3 | Sprint Focus: | ||
Complexity: |
Description
Problem:
Currently the standard CSS_Styled_Content search form, tt_content.search.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 search logic is done in the class ??.
Related issues
History
#1 Updated by Oliver Hader almost 4 years ago
- Tags set to FormWizard
#2 Updated by Oliver Hader almost 4 years ago
- Project changed from Form to Core
#3 Updated by Oliver Hader almost 4 years ago
- Category set to Form Wizard
#4 Updated by Oliver Hader almost 4 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
#5 Updated by Steffen Ritter over 3 years ago
- Target version deleted (
4.7.0)
#6 Updated by Felix Kopp 10 months ago
- Parent task set to #61842
#7 Updated by Benjamin Mack 17 days ago
- Status changed from Accepted to Needs Feedback
Patrick, isn't this fixed by now?
#8 Updated by Bjoern Jacob 16 days ago
- Category changed from Form Wizard to PRJ: Forms
#9 Updated by Bjoern Jacob 14 days ago
- Category changed from PRJ: Forms to Form Wizard