Project

General

Profile

Actions

Bug #80385

closed

INCLUDE_TYPOSCRIPT is using wrong ConditionMatcher when using condition option

Added by Andreas Allacher about 7 years ago. Updated over 5 years ago.

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

100%

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

Description

The INCLUDE_TYPOSCRIPT option does always use the Backend ConditionMatcher.
However, in FE this should be the Frontend ConditionMatcher because otherwise the current page might not be detected correctly.
Furthermore, constants also won't be available etc.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #76236: INCLUDE_TYPOSCRIPT condition PIDinRootline does not work correctyClosed2016-05-19

Actions
Actions

Also available in: Atom PDF