Project

General

Profile

Actions

Bug #104150

closed

Default Form configuration not always loaded for EXT:form

Added by Georg Ringer 5 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
Start date:
2024-06-18
Due date:
% Done:

100%

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

Description

With #103556 the behaviour changed with inclusion of the YAML configuration for EXT:form which leads to the error

 #1681549038 LogicException
Configuration could not be loaded

especially with multiple sites this can occur, e.g when one site is using site sets and does not include the YAML configuration.

possible solutions

a) change inheritNavigationComponentFromMainModule to true. providing a page tree makes it possible to select at leat a root page
b) remove query param id: \TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager::getCurrentPageId uses the give ID as page id, if this is set 0, error doesn't occur as well.

\TYPO3\CMS\Extbase\Configuration\BackendConfigurationManager::getCurrentPageId is code which needs to be changed but now more pressing is the exception


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Task #103556: Provide sets for FSC, felogin and indexed_searchClosedBenjamin Franzke2024-04-07

Actions
Related to TYPO3 Core - Bug #102380: Resolve correct page UID in BackendConfigurationManagerClosed2023-11-16

Actions
Related to TYPO3 Core - Bug #104543: Styleguide Frontend not working when used with Site Sets and missing dependenciesClosedGarvin Hicking2024-08-02

Actions
Actions

Also available in: Atom PDF