Actions
Feature #13230
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.search.20 should be done with the new FORM mapping
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 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 ??.
Updated by Oliver Hader over 12 years ago
- Project changed from 135 to TYPO3 Core
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
Updated by 
Updated by
Updated by Benni Mack almost 9 years ago
- Status changed from Accepted to Needs Feedback
Patrick, isn't this fixed by now?
Updated by Björn Jacob almost 9 years ago
- Category changed from Form Framework to 1602
Updated by Björn Jacob almost 9 years ago
- Category changed from 1602 to Form Framework
Updated by Benni Mack over 8 years ago
- Status changed from Needs Feedback to Rejected
search is moved into EXT:compatibility6, same as the old mailform. so these two should stick together.
Actions