Actions
Task #69362
closed
Epic #69036: EXT:form - Optimize layout rendering
Forms: allow wrapping of error and message object
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2015-08-27
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
It's possible to have an error or message object as cObject. See example:
error = TEXT
error {
value = The value does not appear to be a hostname
}
The following snippet is not working since the error object seems to be escaped automatically:
error = TEXT
error {
value = <!-- -->
wrap = <span class="fa fa-exclamation-triangle">|</span>
}
The same problem applies to the message object.
Updated by Oliver Hader over 9 years ago
Allowing real cObjects in that place, that can be defined by any non privileged backend user targets again security issues...
Therefore I'd opt to go the Extbase/Fluid way for CMS 7 and ignore these drawbacks for TYPO3 CMS 6.2
Updated by Björn Jacob over 9 years ago
- Status changed from New to On Hold
- Parent task set to #69036
As Olly mentioned this should be done differently using fluid.
Updated by Björn Jacob over 9 years ago
- Status changed from On Hold to Closed
This issue is not longer a problem since v7.5.
Actions