Project

General

Profile

Actions

Bug #53579

closed

Backend layout of subpages is ignored/not inherited to all subpages

Added by Christoph Gross over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
-
Target version:
Start date:
2013-11-13
Due date:
% Done:

80%

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

Description

After selecting a layout on the rootpage for the subpages the layout is not inherited to all the subpages. To test this just create a new be layout and assign it on the rootpage for all subpages.

Surprisingly there are some subpages that have the be layout assign. But there does not seem to be a pattern which will end up with the layout. I have even and uneven page numbers with and without the layout.

I'm using the latest Typo3 6.2 master.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #73133: Wrong behaviour of "backend_layout_next_level"Closed2016-02-04

Actions
Actions #1

Updated by Stefan Froemken about 10 years ago

We have the same problem on 6.2 master (09.01.2014), but only with newly created pages on rootpage. And only when we create new pages within "add new" of pagetree-frame.

Actions #2

Updated by Stefan Froemken about 10 years ago

Interessting. The cols backend_layout and backend_layout_next_level are empty in database. After changing them to 0 it works again. But why is the datatype of these fields VARCHAR?!?! Maybe int(11) would be better.

Actions #3

Updated by Stefan Froemken about 10 years ago

  • % Done changed from 0 to 100

I found it. This issue was solved. Coreteam has added $this->selectedCombinedIdentifier[$pageId] !== '' in addition to $this->selectedCombinedIdentifier[$pageId] !== '0' in BackendLayoutView.php. So update to current master.

Stefan

Actions #4

Updated by Emile Blume over 9 years ago

  • Target version set to next-patchlevel
  • % Done changed from 100 to 80

This does not solve the problem in TYPO3 6.2.9

Actions #5

Updated by Wouter Wolters over 8 years ago

  • Status changed from New to Closed

You should update your TYPO3 to the latest version of 6.2

Actions

Also available in: Atom PDF