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

# TYPO3 Exception 1540246570

> [!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).

## TYPO3 13.4: No Content Object definition found \[21.10.2024\]

> [!WARNING]
> No Content Object definition found at TypoScript object path "tt_content.text"

This error happens when you did not include the
[Site set "Fluid Styled Content"](https://docs.typo3.org/c/typo3/cms-fluid-styled-content/main/en-us/Configuration/Sets/FluidStyledContent.html#site-set-fluid-styled-content)
but try to use a content element provided by this system extension.

Solution: Require the site set in your site configuration:
[Using a site set as dependency in a site](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSets/Index.html#site-sets-usage) or depend on it from
your site packages site set:
[Defining the site set with a fluid_styled_content dependency](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/SiteHandling/SiteSets/ReusableSets.html#site-sets-example-site-package-set).

## Is there a problem with the plugin ?

It happens when a content element of type plugin is created and then you forget to
choose the specific Plugin from the tab 'Plug-in'

---

Occures if you pass the wrong pluginType to
`TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(...)`.

## TYPO3 12 - General Plugin: No Content Object definition found at TypoScript object path "tt_content.list.20

If your extension is a general plugin, check if it is properly installed (and activated for legacy installations)
and the required TypoScript included.
Otherwise proceed as follows.

`tt_content.php` adds the plugin by

```php
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPlugin()
```

However the tt_content TypoScript for the list type is not added if you look into the Active TypoScript
in the backend.
The extension TypoScript is like this:

**EXT:my_extension/Configuration/Sets/MyExtension/setup.typoscript**

```typoscript
plugin.tx_myextension {
    controller.action = EXTBASEPLUGIN
}
```

### Solution

Always add the TypoScript for the `tt_content` list rendering.

`ext_localconf.php`

**EXT:my_extension/Configuration/Sets/MyExtension/setup.typoscript**

```typoscript
tt_content.list.20 {
    tx_myextension_controllers_action = < plugin.tx_myextension.controller.action
}
```

## You have removed Typoscript by Conditon?

For example you have used this:

```
[globalVar = TSFE:id = {$noLoginPluginOnPids}]

lib.login >

[global]

```

This will lead to this Exception since TYPO3 LTS 9 if you use something
like the next line in your Fluid Template \<f:cObject
typoscriptObjectPath="lib.login" />

### Solution

change typoscript to:

```
[globalVar = TSFE:id = {$noLoginPluginOnPids}]

lib.login =

[global]

```

## Exception is thrown in a fluid template using a view helper

Might be caused by a translation not found in Fluid:

```xml
<f:translate key = "Button_Helpful" />
```

If translation key is not found in the default language file, this error
will be thrown.

### Solution

add a default text to the tag and also fix the language file.

The error does not occur when you use the Fluid lanuage tag with a path:

```xml
<f:translate key = "LLL:EXT:yourExtension/Resources/Private/Language/locallang.xml:Button_Helpful" />
```

## TYPO3 12/13 - General Plugin: No Content Object definition found at TypoScript object path "tt_content.list.20"

This exception could happen because a plugin was registered before using the `list` content element
and the plugin subtype `list_type` and is now registered as `ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT`.

Have a look at [Deprecation: #105076 - Plugin content element and plugin sub types](https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.4/Deprecation-105076-PluginContentElementAndPluginSubTypes.html#deprecation-105076-1726923626).

Either an Upgrade Wizard was not executed for those plugins or may be you need to create one.

If Upgrade Wizard creation is required, you can have a look in TYPO3 core for example, search
Upgrade Wizard extending `AbstractListTypeToCTypeUpdate`, like `final class IndexedSearchCTypeMigration extends AbstractListTypeToCTypeUpdate`.