Project

General

Profile

Actions

Bug #76447

closed

TypoScript Parse Bug

Added by Kevin Dargel almost 8 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2016-06-03
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.6
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The current TS-Parsing seems to ignore or take in account commented-out sections of TypoScript containing a condition (like PIDinRootline).

Put this at the end of a TS template and the following TS is not getting parsed (even TS code in the same template directly below those lines):

/*
// [PIDinRootline = 0]
[global]*/

It may be reproducible with even less code lines; I'm unsure about the real cause.
I tested this with the following TS on a SUB-PAGE or on the same page, to verify it really isn't getting parsed/handled:

page.headerData.40 = TEXT
page.headerData.40.value = <meta name="test" />

It won't take effect.
(Reproduced with Typo3 6.2.21, 24 and 25)


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Feature #16681: C style TypoScript comments with start and end in one line lead to errorsClosed2006-11-01

Actions
Related to TYPO3 Core - Bug #41327: jsInline removes closing bracketsClosedChristian Kuhn2012-09-24

Actions
Related to TYPO3 Core - Feature #97816: New TypoScript parserClosed2022-06-27

Actions
Actions

Also available in: Atom PDF