Issue Bug New Orphaned Good first issue

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

Christian Futterlieb 04/04/20, 16:36 updated 02/05/24, 07:20

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.

Reviews 1

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch

Commit message
[BUGFIX] persistence.storagePid ignores startingpoint (pages), when it is a stdWrap Resolves: #90949 Releases: main