1
votes

I scaffolded an extbase extension for Typo3 4.7 with the extension_builder extension (v2.4.0). Everything was included to register a backend module. However, after installing the extension when opening the backend module the following error message is shown:

Sorry, the requested view was not found.
The technical reason is: No template was found. View could not
be resolved for action "list".

After googling for quite a lot of time I found a workaround on the extension_builder mailing list. This requires the user to manually include the folder extension/Configuration/TypoScript into the current template's used TypoScript. Inside the files in this folder, there's the needed configuration to make extbase find the right template path.

While this works, it doesn't sound like the right way to do it and it is definitely not desirable to have someone who wants to install the extension make some changes to his template to get a backend module running.

How can I omit this step and still get it working? I looked at other modules where it seems to work without a problem, but I wasn't able to figure out how they do it.

1

1 Answers

1
votes

I am not 100% sure it I understood your problem.

In TYPO3 6.0 and 6.1, the handling of TypoScript settings has been improved for backend modules. You can now put your mappings into ext_typoscript_setup.txt which gets included automatically without the need of a root template.

For more details, have a look at the related bug report and the commit message.

To resume my answer, a solution would be to upgrade to TYPO3 >=6.0.