Project

General

Profile

Actions

Bug #24512

closed

be_layout setting "none" is not working and be_layout should not be inherited automatically

Added by Jo Hasenau almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2011-01-11
Due date:
% Done:

0%

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

Description

There are still two bugs with the current behaviour of be_layout and be_layout_next_level:

1. be_layout must affect the current page only - currently it affects subpages as well. be_layout_next_level must be used instead
2. be_layout setting "none" will stop the inheritance for the current page
3. be_layout_next_level "none" will stop inheritance for subpages

currently "None" has no effect at all.

Additionally this change will have people easily access the selected be_layout via TS levelfield

The change will affect the function getSelectedBackendLayoutUid only, so no big deal to change it.

Will come up with a patch ASAP.

(issue imported from #M16966)


Files

16966.diff (2.97 KB) 16966.diff Administrator Admin, 2011-01-11 16:59

Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #24234: Backend layout setting "none" is ignoredClosedSteffen Gebert2010-11-29

Actions
Actions #1

Updated by Ernesto Baschny almost 14 years ago

I've added the be_layout_next_level field also to
t3lib_pageSelect::getRootLine, because this is the method which is used
to create the rootline in the frontend (to allow access to it via 'data = levelfield: -1, be_layout_next_level, slide' => works).

Committed Jigal's v2 + the above mentioned change to trunk rev. 10031.

Actions #2

Updated by Susanne Moog over 13 years ago

  • Target version deleted (4.5.0)
Actions

Also available in: Atom PDF