Project

General

Profile

Actions

Bug #90479

closed

New fluidbased PageLayoutView throws error, if backendLayout can no longer be resolved

Added by Christian Eßl about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend API
Target version:
-
Start date:
2020-02-21
Due date:
% Done:

100%

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

Description

How to reproduce:
- Install introduction package on master (which then automatically imports a pagetree)
- deinstall the introduction package in the extension manager
- Go to the page module and open a page.

The new fluidbased page module will now throw an error:

Call to a member function getDrawingConfiguration() on null

in line:

$backendLayout = $this->backendLayouts->getDataProviderCollection()->getBackendLayout(
                $selectedCombinedIdentifier,
                $this->id
            );

$configuration = $backendLayout->getDrawingConfiguration();

which happens in DataProviderCollection::getBackendLayout();

Because the configured backend layout of the previously installed extension is now missing. If a backendLayout cannot be resolved, there should be either:
  • thrown an exception, that the backendLayout can't be resolved
  • or a fallback to the "default" backend layout.

I think the latter option was the behaviour in the old PageLayoutView.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #90348: PageLayoutView and BackendLayout should be refactored to separate rendering, processing and fetching of contentClosed2020-02-10

Actions
Actions

Also available in: Atom PDF