Project

General

Profile

Actions

Bug #73133

closed

Wrong behaviour of "backend_layout_next_level"

Added by Gerhard Rupp over 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2016-02-04
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Backend layout set in "backend_layout_next_level" is taken for current page if "backend_layout" is not set (inheritace not working).


Files

cattura.png (3.76 KB) cattura.png Riccardo De Contardi, 2016-02-05 14:59
backend_layout_behaviour.png (3.78 KB) backend_layout_behaviour.png Jo Hasenau, 2016-02-05 15:16
Cattura2.PNG (5.05 KB) Cattura2.PNG Riccardo De Contardi, 2017-03-15 10:35

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #53579: Backend layout of subpages is ignored/not inherited to all subpagesClosed2013-11-13

Actions
Has duplicate TYPO3 Core - Bug #78003: Backend Layout (subpages of this page)Rejected2016-09-20

Actions
Actions #1

Updated by Philipp Gampe over 8 years ago

  • Status changed from New to Needs Feedback

I do not understand you problem.

What do you expect and what happens instead?

The backend layout for next level is always taken as fallback and inherited, unless there is an explicit backend layout for the current page.

Actions #2

Updated by Gerhard Rupp over 8 years ago

In my opinion the page should inherit the backend layout of pages of higher levels. Setting for "backend_layout_next_level" should only be taken into account for pages below.

Actions #3

Updated by Riccardo De Contardi over 8 years ago

Let me see if I have understood:

The scenario is similar to the one I wrote on the attached image Cattura.png (the pages are nested, so 2 is child of 1 and so forth)

the expected result for page 3 is "B", but instead you got "C"? Am I right?

Actions #4

Updated by Gerhard Rupp over 8 years ago

Exactly!

Actions #5

Updated by Jo Hasenau over 8 years ago

Just to clarify the intended behaviour:

  1. The field "backend_layout" is not inherited at all but only marks the specific backend layout of a certain page.
  2. The field "backend_layout_next_level" is inherited from parent pages.
  3. Any value > 0 for "backend_layout_next_level" will override possible inherited values of the parent page so pages below will behave differently.
  4. Any value > 0 for "backend_layout" will override the inherited backend_layout_next_level of a parent page, but only for that particular page.

So cattura.png shows the intended behaviour, except 4), which is not in the picture.

Actions #6

Updated by Jo Hasenau over 8 years ago

Added 4 to the scenarios, which is case D for page 2.

Actions #7

Updated by Gerhard Rupp over 8 years ago

Is it reasonable to not inheritate "backend_layout"?
Therefore setting "backend_layout" at the root page would have no effect for all following pages.

Actions #8

Updated by Jo Hasenau over 8 years ago

Yes it is, since this way makes sure you can override inherited values for single pages.
If backend_layout itself would be inherited too, you would have to repeat the actually inherited backend_layout_next_level setting even when it did not change at all.

So if you want all pages to have the same backend layout, you have to set both fields of the root page.
Ohterwise subpages will get the default layout.

Actions #9

Updated by Gerhard Rupp over 8 years ago

OK.

But for TYPO3 6.2.17 page 3 does not behave as expected.

Result is "C" instead of "B".

Actions #10

Updated by Jo Hasenau over 8 years ago

Checked that with 6.2.17 and for me it seems to work.
Could you make a table showing the relevant part of your page tree and the settings for both fields as well as the result?

Actions #11

Updated by Gerhard Rupp over 8 years ago

This is my configuration (backend_layout / backend_layout_next_level) - TYPO3 6.2.17

homepage (layout_1 / layout_1) -> layout_1 (OK)
  level_1_page (<not_set> / <not_set>) -> layout_1 (OK)
    level_2_page (<not_set> / layout_2) -> layout_2 (should be layout_1)
      level_3_page (<not_set> / <not_set>) -> layout_2 (OK)
Actions #12

Updated by Alexander Opitz about 8 years ago

  • Status changed from Needs Feedback to New
  • Target version changed from 6.2.18 to next-patchlevel
Actions #13

Updated by Riccardo De Contardi about 7 years ago

@Gerhard Rupp

I am really sorry for the very late answer!

I tried with both 7.6.16 and 8.7-dev (latest master) with the scenario you described in your last comment, which I summarized in Cattura2.png

I am not able to reproduce anymore the problem: on both versions the results are the ones described in column"expected result"

Therefore, I close this issue;

If you think that this is the wrong decision then please reopen it or open a new issue with a reference to this one.

Thank you

Actions

Also available in: Atom PDF