Project

General

Profile

Actions

Bug #90949

open

persistence.storagePid ignores startingpoint (pages), when it is a stdWrap

Added by Christian Futterlieb over 4 years ago. Updated 10 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
Start date:
2020-04-04
Due date:
% Done:

0%

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

Description

Consider following situation:

TypoScript setup:

plugin.tx_myext.persistence {
    storagePid.ifEmpty.data = TSFE:id
}

ContentObject:

Array (
    [data] => Array (
        [CType] => list
        [list_type] => myext_myplugin
        [pages] => 123
    )
)

Now, one could expect, that the definitive storagePid would be 123, but it is the value of TSFE:id. This is because ArrayUtility::mergeRecursiveWithOverrule() does not override the storagePid FrontendConfigurationManager::overrideStoragePidIfStartingPointIsSet(), when the storagePid is an array. Which is true, when a config like the one above is used. This leads to the situation, where the value argument passed to stdWrap() would always be the one from TypoScript.

Affected TYPO3 versions: 9.5 and master.

I'll submit a patch in a moment.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #88533: `persistence.classes.*.newRecordStoragePid` does not get `stdWrap` applied (other than `persistence.storagePid`)Rejected2019-06-09

Actions
Actions

Also available in: Atom PDF