---
title: "TYPO3 Exception 1313855173"
manual: "TYPO3 Exceptions"
version: "main"
permalink: "https://docs.typo3.org/permalink/t3exceptions:typo3-exception-1313855173"
source: "Exceptions/1313855173.rst"
modified: "2026-09-16T07:39:08+00:00"
---

# 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](https://talk.typo3.org/c/typo3-questions/).
>
> To add your experience, click "Edit on GitHub" above and follow the
> ["Edit on GitHub" workflow](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/EditOnGithub.html#docs-contribute-github-method).
> Also check out
> [our tip on Coding Style and reST](https://docs.typo3.org/permalink/t3exceptions:tip-about-rest-coding-style).

## 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:

1.  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.
1.  If you don't want to add the missing controller to `ext_localconf.php`
    you have the possibility to add following into your TypoScript:

    ```typoscript
    plugin.your_extension.mvc.callDefaultActionIfActionCantBeResolved = 1
    ```
1.  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

```typoscript
module.your_extension {
// ...
}
```