Issue Feature Accepted Orphaned

#96366Stop on additional bad doktypes for ContentObject slide

Stefan Bürk 12/16/21, 10:13 updated 06/21/24, 09:09

Description

Behaviour of ‘slide = -1’ has changed in v9 when doktype filtering
has changed in the frontend to allow doktypes greater then 200 in
the frontend. Since then, sliding do not stop on sysfolders anymore,
which was also a usecase for someone and this was entitled as bugfix.

For other usecases this bugfix is a regression, as it do not work as
before but instances rely on this.

To get all use-cases togheter, a new configuration options is suggested,
so additional doktypes on which sliding should stop can be configured,
so these who needs the stopping can simply add this small option to
the corresponding typoscript, having the sliding over for the others
still in place.

It is suggested to add a new option ‘slide.stopOnDokTypes’ as a comma
sperarated doktype int list.

temp.traversefooter = COA
temp.traversefooter {
    stdWrap.ifEmpty.cObject = CONTENT
    stdWrap.ifEmpty.cObject {
        table = tt_content
        select {
            pidInList = this
            orderBy = sorting
            where = colPos = 1
        }

        # that's the magic for traversing
        slide = -1

        # stop on sysfolders like in v7 (this is the suggested option)
        slide.stopOnDokTypes = 254
    }
}

Reviews 2

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
[FEATURE] Stop on additional bad doktypes for ContentObject slide Resolves: #96366 Releases: main