Application Module returns error TYPO3Fluid\Fluid\View\Exception\InvalidSectionException

[zenoussi]

When I select the Application Module, I get the following error message:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Section "content" does not exist. | TYPO3Fluid\Fluid\View\Exception\InvalidSectionException thrown in file /var/www/html/vendor/typo3fluid/fluid/src/View/AbstractTemplateView.php in line 266. Requested URL: https://xxx.ddev.site/typo3/module/jobapplications?token=--AnonymizedToken--

jobapplications 3.0.3 TYPO3 12.4.7 PHP 8.1.13

Greetings Ulli

[ghost]

Did you include the static TypoScript?

[zenoussi]

yes, I included: Jobapplications (jobapplications) Jobapplications: [Optional] Include jQuery (if necessary) for working filters (jobapplications)

[ghost]

Okay, weird. Can you take a look into the "Active TypoScript" Setup Browser, to see if it looks anything like this?

[zenoussi]

[ghost]

Weird, this looks very normal. It seems that it tries to render the Frontend Layout, because that case content written in lowercase. Maybe you can do some debugging to see which template it tries to render and why

[zenoussi]

I have installed the extension again in another TYPO3 instance and the module works there.

The difference is that the current project is a multidomain instance: (1) kunde.de and (2) karriere.kunde.de

The extension or the static Typoscript is required in the root template of (2) karriere.kunde.de and is only integrated there - the module does not work this way. If I add the static typoscript to the root template of (1) kunde.de, the module works. If I then remove the static Typoscript in (2) karriere.kunde.de, the module also works.

Can you confirm the behaviour for a multidomain setup?

[firmenpunkt]

Yes, I can confirm that. The module "Applications" only works if the static typoscript is included in the root, not further down in the tree.

[benjasper]

This seems to be solved