Bug #16830
closedComment in TYPOSCRIPT can prevent T3 from rendering template
0%
Description
If you create a template with the following code and include it into an other template, T3 might stop rendering all your templates which are linked or link to this template in any way. I guess something's wrong with the CSS comments /* */
{$constantsetempty}temp.css.300 = TEXT {$constantsetempty}temp.css.300.value ( #CssRule { position:relative; /* padding-bottom:999999px; margin-bottom:-999999px;*/ } )
(issue imported from #M4738)
Updated by Alexander Opitz over 11 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0) - PHP Version deleted (
4)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Chris topher over 11 years ago
http://docs.typo3.org/typo3cms/TyposcriptSyntaxReference/Syntax/TypoScriptSyntax/Index.html is the relevant documentation.
The opening CSS comment obviously is treated as a TypoScript comment. This comment is not closed (no "*/" at the start of a new line), so the complete rest of your template is treated as a comment.
The question is:
Should TypoScript do any parsing inside a multiline value? Parsing might be useful for replacing constants.
Updated by Alexander Opitz over 11 years ago
- Status changed from Needs Feedback to Closed
No bug as documented.