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.

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.

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" 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 or depend on it from your site packages site set: Defining the site set with a fluid_styled_content dependency.

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

\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/TypoScript/setup.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/TypoScript/setup.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:

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

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