Project

General

Profile

Actions
Copy link

Bug #90196

closed

Wrong rootline order in backend condition matcher

Added by Daniel Goerz almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-01-24
Due date:
% Done:

100%

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

Description

When the Backend Condition Matcher is instantiated in BackendUtility::getPagesTSconfig() a ksort ist applied to the rootline

$rootLine = self::BEgetRootLine($id, '', true);
// Order correctly
ksort($rootLine);
...
$matcher = GeneralUtility::makeInstance(ConditionMatcher::class, null, $id, $rootLine);

However the ConditionMatcher calls BEgetRootLine when instantiated without a rootline but does not perform a ksort, which leads to an inverted array ordering.

Actions
Copy link

Also available in: Atom PDF