Bug #47985

INCLUDE_TYPOSCRIPT does not resolve TS-Constants

Added by Gabriel Kaufmann / Typoworx NewMedia over 8 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2013-05-06
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

INCLUDE_TYPOSCRIPT does not resolve TS-constants defined before the Include takes place:

<INCLUDE_TYPOSCRIPT: source="FILE:{$myIncludePath}/yetAnotherSetup.txt">

--
Work on this ticket may be related to #47982


Related issues

Related to TYPO3 Core - Feature #47982: INCLUDE_TYPOSCRIPT does not support real relative paths & constantsClosedGabriel Kaufmann / Typoworx NewMedia2013-05-06

Actions
Related to TYPO3 Core - Feature #22896: cannot integrate a constant into <INCLUDE_TYPOSCRIPT: source=/fileadmin/{$myconstant}Closed2010-06-16

Actions
Has duplicate TYPO3 Core - Bug #56304: INCLUDE_TYPOSCRIPT with CONSTANTS Variable within INCLUDE_TYPOSCRIPT file not possibleClosed2014-02-26

Actions
#1

Updated by Markus Klein over 8 years ago

  • Category set to TypoScript
#2

Updated by Thorsten Kahler over 8 years ago

  • Status changed from New to Rejected

This behaviour is documented, see http://docs.typo3.org/typo3cms/TyposcriptSyntaxReference/Syntax/Includes/Index.html
Reason: The final TS constants tree can't be used before all includes are resolved, so this is kind of a hen and egg problem. Otherwise includes could not be used for constants.

#3

Updated by d.ros no-lastname-given over 6 years ago

I mean with "multiple sites in one tree" a common Multidomaintree. root -> Page 1 | root -> Page 2 | root -> Page 3 | etc

Also available in: Atom PDF