Bug #90479
Updated by Christian Eßl about 4 years ago
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: <pre><code class="php"> Call to a member function getDrawingConfiguration() on null </code></pre> in line: <pre><code class="php"> $configuration = $backendLayout->getDrawingConfiguration(); </code></pre> 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: * be thrown an exception, that the backendLayout can't be resolved * or be a fallback to the "default" backend layout. "default". I think the latter option was the behaviour in the old PageLayoutView.