Project

General

Profile

Actions

Feature #96366

open

Stop on additional bad doktypes for ContentObject slide

Added by Stefan Bürk almost 3 years ago. Updated 5 months ago.

Status:
Accepted
Priority:
Should have
Assignee:
Category:
Content Rendering
Start date:
2021-12-16
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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
    }
}


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #18079: slide of cObj CONTENT stops if sysfolder in rootlineClosed2008-01-30

Actions
Related to TYPO3 Core - Feature #20933: Enable working with SysFolders in CONTENTClosed2009-08-26

Actions
Actions

Also available in: Atom PDF