TYPO3 Exception 1313855173

Note

Below, the TYPO3 community may have provided additional information or solutions for this exception. However, these may or may not apply to your particular case. If you can provide more information, you should come back here and add your experience and solution steps to this issue once you have resolved it.

General TYPO3 troubleshooting tips can be found in the Troubleshooting section in the menu. You can also ask questions and receive support in the TYPO3 Questions category on talk.typo3.org.

To add your experience, click "Edit on GitHub" above and follow the "Edit on GitHub" workflow. Also check out our tip on Coding Style and reST.

The controller "..." is not allowed by this plugin.

First of all: Please check, if you have configured your controller in ext_localconf.php

If the problem still comes up:

Maybe you have changed your content element from another plugin to your new extbase plugin. In that case it may be that the previous plugin works with FlexForms (pi_flexform). Extbase will read these FlexForm configurations no matter if your plugin needs them or not. So please delete the current content element, create a new one and choose your plugin OR clear content of column pi_flexform in database of this content element.
If you don't want to add the missing controller to ext_localconf.php you have the possibility to add following into your TypoScript:
```
plugin.your_extension.mvc.callDefaultActionIfActionCantBeResolved = 1
```
Copied!
Your routing configuration contains defaultController: MyPluginController::index. The Controller suffix may not be used in there; the correct configuration would be defaultController: MyPlugin::index.

Another possibility is that you may have the same plugin twice on the same page with different switchable controller actions chosen. If there is one switchable controller action chosen on another plugin that does not allow this controller, you'll have to adapt your page setup or your switchable controller actions.

If the solutions above do not help, please check, if you somewhere in the early bootstrap initialize the configuration manager. This might be in a request middleware or another hook or event early in the bootstrapping process. If the configuration manager is initialized before it is determined, if the request is a frontend or backend request, the backend configuration manager is initialized. As the configuration manager is a singleton, it would not be initialized again, leading to the plugin configuration being read from

module.your_extension {
// ...
}