Project

General

Profile

Actions

Bug #76919

closed

Flaky references in TypoScript parsing

Added by Oliver Hader over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
TypoScript
Target version:
-
Start date:
2016-07-02
Due date:
% Done:

100%

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

Description

With issue #76323 a mysterious relic from the past has been removed which was about an explicit unserialize(serialize(...)) call during the TypoScript parsing process. In the TYPO3 backend it is possible to trigger some flaky behavior that interferes with those unresolved references.

Expect the following TSconfig as given:

RTE.default.proc.entryHTMLparser_db = 1
RTE.default.proc.entryHTMLparser_db {
    tag {
    }

RTE.default.FE < RTE.default
RTE.default.enableWordClean = 1
RTE.default.enableWordClean.HTMLparser < RTE.default.proc.entryHTMLparser_db

After the TypoScript has been parsed into an array, and the value
$data['RTE.']['default.']['FE.']['proc.']['entryHTMLparser_db.']['tags.'] is set to a different value, also the the value of ['RTE.']['default.']['proc.']['entryHTMLparser_db.']['tags.'] is changed due to the existing reference.

It was not able to reproduce this behavior in a dedicated functional test, but in the backend with BackendUtility::getPagesTSconfig and the accordant parsing part there.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #76323: Obsolete unserialize(serialize())Closed2016-05-27

Actions
Actions

Also available in: Atom PDF