TYPO3 Exceptions 

Version

main

Language

en

Author

TYPO3 contributors

License

This document is published under the Open Publication License.

Rendered

Wed, 01 Oct 2025 18:28:42 +0000


These official pages contain distilled community knowledge regarding exceptions of the enterprise content management system TYPO3.


TYPO3 Exceptions 

Each exception has its own subpage.

Here are some tips about writing reStructuredText (reST)

TYPO3 Exception 1 

TYPO3 4.6.0 

I get this error when switching to Web>Template.

Oops, an error occurred!

PHP Catchable Fatal Error: Argument 2 passed to t3lib_div::array_merge_recursive_overrule()
must be an array, null given, called in /home/typo3_src/typo3_src-4.6.0/typo3/sysext/lang/lang.php
on line 554 and defined in /home/typo3_src/typo3_src-4.6.0/t3lib/class.t3lib_div.php line 1867
Copied!

TYPO3 4.6.8 

After a Debian upgrade (apt-get dist-upgrade) the suhosin.so can not be loaded.

The page with the contact form says: "Oops, an error occurred."

apt-get install php5-suhosin shows a broken dependency.

Solution is to drop suhosin.so from apache2 by dpkg -P php5-suhosin.

TYPO3 4.7.10 

Suddenly got this error when logging on to the next.

Oops, an error occurred!

PHP Catchable Fatal Error: Argument 1 passed to t3lib_div::array_merge_recursive_overrule()
must be of the type array, null given, called in /public_html/typo3conf/ext/dam/lib/class.tx_dam_db.php
on line 376 and defined in /public_html/typo3_src-4.7.14/t3lib/class.t3lib_div.php line 1862
Copied!

Read the Ticket for this Bug #31353 and as advised above.

Solution 

In localconf.php do the settings for the output errors:

$TYPO3_CONF_VARS['SYS']['displayErrors'] = '2';
$TYPO3_CONF_VARS['SYS']['devIPmask'] = '123.456.789.123';
//$TYPO3_CONF_VARS['SYS']['devIPmask'] = '*';
$TYPO3_CONF_VARS['SYS']['errorHandler'] = 't3lib_error_ErrorHandler';
$TYPO3_CONF_VARS['SYS']['systemLogLevel'] = '2';
Copied!

then found that in my case, the error was in the file lang/locallang_login.xlf . More precisely - the replacement for my localization: typo3conf/l10n/ru/lang/ru.locallang_login.xlf - just rename the folder typo3conf/l10n/ru/lang/ and cleared the temporary files in the typo3temp. After that, the error disappeared and the site is working again (but without localization :)

None - please edit if you found a solution!

TYPO3 4.7.17 

  • Login to Backend was not possible.
  • Error occurred after changing PHP Binaries (not PHP Version) from 5.4 (Mac OS X Mavericks default Binaries) to 5.4 (Binaries from http://php-osx.liip.ch/).
#1: PHP Catchable Fatal Error:
Argument 1 passed to t3lib_div::array_merge_recursive_overrule()
must be an array, null given, called in
/path/to/documentRoot/typo3/sysext/lang/lang.php on line 529
and defined in
/path/to/documentRoot/t3lib/class.t3lib_div.php line 1862
Copied!

Solution 

Delete content of /typo3temp folder.

TYPO3 4.7.14 

I get this error when uploading files with DAM 1.3.2 for a user that does not have admin rights.

Oops, an error occurred!

PHP Catchable Fatal Error: Argument 1 passed to t3lib_div::array_merge_recursive_overrule()
must be of the type array, null given, called in /public_html/typo3conf/ext/dam/lib/class.tx_dam_db.php
on line 376 and defined in /public_html/typo3_src-4.7.14/t3lib/class.t3lib_div.php line 1862
Copied!

Read the Ticket for this Bug #51969 and Bug #52296.

Solution 

Downgrade to DAM 1.3.1 dam

Update 2013/11/21 Bug is on typo3.forge: https://forge.typo3.org/issues/51969. Patch is here: https://review.typo3.org/#/c/23848/. Tested, working...

TYPO3 6.1.0 

solr_report 

TO COME HERE WE DID:

6. Check the status report in the reports module The reports module has a Solr section in the status report. It will complain about different aspects and give hints to solve them. Most of the time the reasons can be found in different aspects like:

The Solr Server can not be reached. Firewall. DNS. PHP Modules. SELinux and the likes can be reasons for this You are using the wrong schema.xml that is not supported to work with the installed extension. ... If everything is ok, it should look like this:

WE GOT ERROR MESSAGE:

Uncaught TYPO3 Exception

  1. PHP Catchable Fatal Error: Argument 1 passed to
    tx_solr_report_IndexReport::__construct() must be an instance of
    tx_reports_Module, instance of
    TYPO3\CMS\Reports\Controller\ReportController given in
    /.../typo3conf/ext/solr/report/class.tx_solr_report_indexreport.php
    line 47 (More information)
    Copied!
  2. TYPO3\CMS\Core\Error\Exception thrown in file
    /.../typo3_src-6.1.0/typo3/sysext/core/Classes/Error/ErrorHandler.php
    in line 108.
    Copied!

TYPO3 / PHP VERSION

  1. CONST: php_sapi_name: cgi-fcgi
  2. OTHER: TYPO3_VERSION: 6.1.0
  3. OTHER: PHP_VERSION : 5.3.3-7+squeeze15

Solution 

TYPO3 6.2.0 

When clicking on the root page, create content element using flux / fluidpages / fluidcontent.

typo3_src-6.2.0/typo3/sysext/core/Classes/Database/PreparedStatement.php line 311

| -

I got this error after upgrading from 6.1.7 to 6.2.0. occures when the gridelements extension is installed tested with gridelements v2.0.2 and gridelements v3.0.0-dev https://forge.typo3.org/issues/57833

Solution 

Download the new versions from GIT of "view" https://github.com/FluidTYPO3/view [not available anymore]

unfortunately only working partly: typo3_src-6.2.0/typo3/sysext/lang/Classes/LanguageService.php line 250

Solution 

None please post if you have found one! THX

form 

When submitting a very basic form

Solution 

None, please add.

TYPO3 6.2.2 

PHP Warning: touch(): Unable to create file /user_upload/news/aAbB 

Uncaught TYPO3 Exception
#1: PHP Warning: touch(): Unable to create file /user_upload/news/aAbB because No such file or directory in typo3/sysext/core/Classes/Resource/StorageRepository.php line 263 (More information)

TYPO3\CMS\Core\Error\Exception thrown in file
typo3/sysext/core/Classes/Error/ErrorHandler.php in line 111.
Copied!

Reproduction:

  1. have 6.2.0 on your system
  2. install tool: Important actions: check for core updates
  3. accept the upgrade to 6.2.2
  4. repair folders using Folder Structure
  5. click Upgrade Wizard
  6. click Execute under "Migrate existing filemounts to be file abstraction layer compatible."
  7. click "Perform updates!"

Error source code with line#263 = error line:

typo3/sysext/core/Classes/Resource/StorageRepository.php:
00261:   // create test file
00262:   if (!$testFileExists) {
00263:    touch($path);
00264:   }
00265:
Copied!

No solution found yet

sav_library_kickstarter 

#1: PHP Warning: Invalid argument supplied for foreach() in /var/www/.../typo3conf/ext/sav_library_kickstarter/Classes/ViewHelpers/BuildOptionsForViewSelectorboxViewHelper.php line 42
Copied!

temporarily solved by adding if (is_array($views)) to the foreach statement.

tx_cal 

#1: PHP Warning: array_merge(): Argument #2 is not an array in D:\htdocs\typo3_src-6.2.0\typo3conf\ext\cal\service\class.tx_cal_event_service.php line 253
Copied!
TYPO3\CMS\Core\Error\Exception thrown in file D:\htdocs\typo3_src-6.2.2\typo3\sysext\core\Classes\Error\ErrorHandler.php in line 111.
Copied!
41 TYPO3\CMS\Core\Error\ErrorHandler::handleError(2, "array_merge(): Argument #2 is not an array", "D:\htdocs\typo3_src-6.2.0\typo3conf\ext\cal\service\class.tx_cal_event_service.php", 253, array)
Copied!
40 array_merge(array, boolean)
Copied!

Calling the preview or workspace preview, this TYPO3 exception appears!

TYPO 6.2.3 

#1: PHP Warning: Illegal string offset 'uid' in /volume1/web/cms/typo3_src/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php line 1281
Copied!

At 1st initial start of this page on a day, after realod [e.g. pressing F5] this message disappears, and page runs fine...

TYPO3 6.2.4 

#1: PHP Warning: fread(): Length parameter must be greater than 0 in
/var/www/typo3_src-6.2.4/typo3/sysext/impexp/Classes/ImportExport.php line 3042
Copied!

Error description 

This error occurs when exporting content to .t3d (all tables) from TYPO3 4.5.35 and importing this .t3d into TYPO3 6.2.4. The problem comes from typo3_src/typo3/sysext/impexp/Classes/ImportExport.php line 3009

3009        $this->dat['files_fal'] = $this->getNextFilePart($fd, 1, 'files_fal');
Copied!

Fal was not present in TYPO3 4.5.35 export, so $initStr was always empty, when executing typo3_src/typo3/sysext/impexp/Classes/ImportExport.php line 3042.

Solution 

This bugfix did it for me:

3039                 $initStrDat = explode(':', $initStr);
3040
3041                 // fix to prevent error on t3d export, when exported from system without having fal installed.
3042                 if($name === 'files_fal' && empty($initStr)) {
3043                         return('');
3044                 }
3045
3046                 if (strstr($initStrDat[0], 'Warning') == FALSE) {
Copied!
#1: PHP Warning: Illegal string offset 'uid' in D:\___WWW___\_typo3\_PROJECTS\work_6.2.3\typo3\sysext\frontend\Classes\Controller\TypoScriptFrontendController.php line 1281

Last trace:
3 TYPO3\CMS\Core\Error\ErrorHandler::handleError(2, "Illegal string offset 'uid'", "...\typo3\sys…lasses\Controller\TypoScriptFrontendController.php", 1281, array)
Copied!

Solution 

At 1st initial start of this page after clearing the cache, after reload [e.g. pressing F5] this message disappears, and page runs fine... -- David Bruchmann 02:03, 27 August 2014 (CEST)

TYPO3 6.2.4 

#1: PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Backend\View\PageLayoutView::generateTtContentDataArray() must be an array, null given,
called in /var/www/typo3/sysext/backend/Classes/View/PageLayoutView.php on line 475
and defined in /var/www/typo3/sysext/backend/Classes/View/PageLayoutView.php line 1866
Copied!

Error description 

This error occurs when opening a folder while in page module, but only if the folder has a backend layout configured with no columns. This was only possible until at least 4.7

Solution 1 

Got to the list module and switch the folder back to standard, change the backend layout and switch back.

Solution 2 

Edit your empty backend layout: Insert a colPos

TYPO3 6.2.14 

#1: PHP Warning: class_parents(): object or string expected in /srv/www/typo3/typo3_src-6.2.14/typo3/sysext/extbase/Classes/Persistence/Generic/Mapper/DataMapper.php line 221
TYPO3\CMS\Core\Error\Exception thrown in file
/srv/www/typo3/typo3_src-6.2.14/typo3/sysext/core/Classes/Error/ErrorHandler.php in line 101.
Copied!

For background information see Ticket #56603.

Solution 1 

Log into backend and clear the cache.

Solution 2 

Truncate all tables cf_xxx_xxxx.

TYPO3 6.2.14: Argument 1 must implement ObjectManagerInterface 

#1: PHP Catchable Fatal Error: Argument 1 passed to TYPO3\CMS\Extbase\Persistence\Repository::__construct() must implement interface TYPO3\CMS\Extbase\Object\ObjectManagerInterface, none given
Copied!

Solution 1 

You are trying to instantiate a Repository by calling GeneralUtility::makeInstance('MyExtension\MyRepository').

Do not instantiate Extbase classes by using GeneralUtility::makeInstance but use the objectmanager instead - either by injecting the repository or at least by using GeneralUtility::makeInstance to get the objectmanager instance and using $objectManager->get('MyExtension\MyRepository'):

class MyController extends \TYPO3\CMS\Extbase\Mvc\Controller\ActionController
{
    public function fooAction()
    {
        $repo = $this->objectManager->get(MyRepository::class);
        $item = $repo->findByUid(1);
    }
}
Copied!

TYPO3 6.2.15: Argument 1 passed to TYPO3CMSExtbasePropertyPropertyMappingConfiguration::setTypeConverter() must implement interface TYPO3CMSExtbasePropertyTypeConverterInterface, string given 

In the case you would like to implement your own TypeConverter, you need to call setTypeConverter() method, located in TYPO3CMSExtbasePropertyPropertyMappingConfiguration, line 389.

This method expects a \TYPO3CMSExtbasePropertyTypeConverterInterface as argument, which is simply done by calling a new instance of your TypeConverter:

$this->arguments['Model']
               ->getPropertyMappingConfiguration()
               ->forProperty('property')
               ->setTypeConverter(new \<vendor>\<extension>\Property\TypeConverter\<myConverter>())
Copied!

Note: Replace

<vendor>
Copied!

by your vendor name, and

<extension>
Copied!

by your extension name. This is kind of standard here but that's up to you.

Note 2: Replace

<myConverter>
Copied!

by the name of your converter.

The solution to this error is very obvious but it's better written than not.

TYPO3 6.2.18: tx_news:newsadministration: Division by zero in PaginateController 

#1: PHP Warning: Division by zero in /srv/typo3/typo3_src-6.2.18/typo3/sysext/fluid/Classes/ViewHelpers/Be/Widget/Controller/PaginateController.php line 65
Copied!

TYPO3 7.5 

#1: PHP Catchable Fatal Error:
Argument 2 passed to FluidTYPO3\Flux\UserFunction\HtmlOutput::renderField()
must be an instance of TYPO3\CMS\Backend\Form\FormEngine,
instance of TYPO3\CMS\Backend\Form\Element\UserElement given in
/home/seethrou/public_html/new7/typo3conf/ext/flux/Classes/UserFunction/HtmlOutput.php
line 26
Copied!

Getting this error in page view when trying to edited an element carousel from the Fluid Bootstrap Theme (fluidbootstraptheme)

TYPO3 7.6 

#1: PHP Runtime Deprecation Notice:
Non-static method TYPO3\CMS\Extbase\Configuration\FrontendConfigurationManager::getTypoScriptSetup()
should not be called statically, assuming $this from incompatible context in ...
Copied!

I get the following error in the page module with pages containing gridelements (7.0.0-dev) after installing MFC-canonical 2.1.0:

#1: PHP Warning: Invalid argument supplied for foreach() in D:\...\Source\web\typo3conf\ext\gridelements\Classes\Hooks\DrawItem.php line 95 (More information)
Copied!

If you get this error:

PHP Warning:: igbinary_unserialize_header: unsupported version: "a:2:"...,
should begin with a binary version header of "\x00\x00\x00\x01" or
"\x00\x00\x00\x02"
Copied!

Just delete your caches. If you can't login to your backend, delete them from the install tool.


TYPO3 7.6.5 

After login the following error is shown (7.6.5):

PHP Catchable Fatal Error:
Argument 1 passed to TYPO3\CMS\Core\Resource\ResourceStorage::getFileForLocalProcessing()
must implement interface TYPO3\CMS\Core\Resource\FileInterface, null given,
called in .../typo3_src-7.6.5/typo3/sysext/core/Classes/Resource/Processing/LocalImageProcessor.php
on line 118 and defined in .../typo3_src-7.6.5/typo3/sysext/core/Classes/Resource/ResourceStorage.php line 1337
Copied!

In 7.6.5 and 8.0 there is an issue when a sys_file_processed file record is deleted but the processed file is still present https://review.typo3.org/#/c/47783/ . To temporary work around the issue you can delete (if known) the specific processed file in fileadmin/_processed_ folder or delete the complete _processed_ folder (files will get generated automatically).

This regression will be fixed in 7.6.6: https://review.typo3.org/#/c/47783/

TYPO3 7.6.10 

Scheduler results in this error. When scheduler sends mail, this is the content of the mail

PHP Warning: array_shift() expects parameter 1 to be array, null given in
typo3_src-7.6.10/vendor/symfony/console/Input/ArgvInput.php line 61
More information regarding this error might be available online.
Copied!

TYPO3 7.6.16 

Deprecation Notice: mysql_connect() 

PHP Runtime Deprecation Notice:
mysql_connect(): The mysql extension is
deprecated and will be removed in the future: use mysqli or PDO instead
in
/usr/share/typo3/typo3_src-7.6.16/typo3/sysext/adodb/adodb/drivers/adodb-mysql.inc.php
line 462 (More information)

TYPO3\CMS\Core\Error\Exception thrown in file
/usr/share/typo3/typo3_src-7.6.16/typo3/sysext/core/Classes/Error/ErrorHandler.php
in line 111.
Copied!

Solution 

Change mysql to mysqli when calling adodb http://adodb.org/dokuwiki/doku.php?id=v5:database:mysql

php version: PHP 5.6.30-1 dotdeb+7.1 (cli) (built: Jan 21 2017 14:50:59)

ReflectionProperty::getValue() 

PHP Warning: ReflectionProperty::getValue(): Couldn't fetch
mysqli_result in
/usr/share/typo3/typo3_src-7.6.16/typo3/sysext/extbase/Classes/Utility/DebuggerUtility.php
line 349 (More information)
Copied!

This happens when i use

\\TYPO3\CMS\Core\Utility\DebugUtility::debug($GLOBALS,'GLOBALS');
Copied!

For some reason the connection to the database fails.

Warning: phpinfo() has been disabled 

Exception occurs in Install Tool > System environment

Uncaught TYPO3 Exception
PHP Warning: phpinfo() has been disabled
for security reasons in
/var/www/[...]/vendor/typo3/cms/typo3/sysext/install/Classes/ViewHelpers/PhpInfoViewHelper.php
line 73
Copied!

Solution 

Yet unknown.

TYPO3 Exception 40 

Indicates an SQL error has occurred, please check your ext_tables.sql files.

For example:

The column 'columnname' on table 'tablename' already exists
Copied!

This happens for example if the file ext_tables.sql of a TYPO3 extension has the same field twice for a table.:

CREATE TABLE sys_products_fe_users_mm_visited_products (
    uid int(11) NOT NULL auto_increment,
    pid int(11) DEFAULT '0' NOT NULL,
    tstamp int(11) DEFAULT '0' NOT NULL,
    crdate int(11) DEFAULT '0' NOT NULL,
    deleted tinyint(4) DEFAULT '0' NOT NULL,
    hidden tinyint(4) DEFAULT '0' NOT NULL,
    tstamp int(11) unsigned DEFAULT '0' NOT NULL,
    uid_local int(11) DEFAULT '0' NOT NULL,
    uid_foreign int(11) DEFAULT '0' NOT NULL,
    qty int(11) unsigned DEFAULT '0' NOT NULL,
Copied!
    PRIMARY KEY (uid),
    KEY uid_local (uid_local),
    KEY uid_foreign (uid_foreign),
);
Copied!

There are 2 fields tstamp in the table sys_products_fe_users_mm_visited_products

Removing the second line with the field tstamp from table sys_products_fe_users_mm_visited_products fixes the problem in this case.

TYPO3 Exception 550 

May happen if an extension converts a HTTP error code to an exception code.

Oops, an error occurred! Expected response code 250 but got code "550", with message "550 5.7.60 SMTP; Client does not have permissions to send as this sender

In this case, the FE_Manager tries to send a notification to the admin and the sender address or mail server information doesn't match the requirements.

TYPO3 Exception 1166543253 

TYPO3 Exception 1166546734 

#1166546734 TYPO3CMSCorePackageExceptionUnknownPackageException 

Reason 1: 

  • Package does really not exist

Reason 2: 

|Extension Upload screen TER.png|

  • CamelCaseConversion Problem with numbers
  • f.e. vendor_extension_2018 will be converted into VendorExtension2018 and converted back into vendor_extension2018

This will result in the following error message:

Package "vendor_extension2018" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive)

According to the hints in TER these kind of keys are invalid:

Reason 3: 

1/1) #1166546734 TYPO3CMSCorePackageExceptionUnknownPackageException Package "" is not available. Please check if the package exists and that the package key is correct (package keys are case sensitive).

Happened on switching from LTS 9 to 10 as $_EXTKEY is no longer defined. Therefore I called:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
     'VENDOR.' . $extensionKey,
     'Pi1',
     'LLL:EXT:...'
 );
 
Copied!

With an empty $extensionKey

See also 

TYPO3 Exception 1166631889 

TYPO3 Exception 1166631890 

TYPO3 Exception 1166633720 

TYPO3 Exception 1166633721 

\TYPO3\Flow\Package\Exception 

Exception happens while building class files for the class loader in TYPO3 6.2.

TYPO3 Exception 1166633722 

TYPO3 Exception 1166635495 

TYPO3 Exception 1167917198 

TYPO3 Exception 1167917199 

TYPO3 Exception 1167917200 

TYPO3 Exception 1167919564 

TYPO3 Exception 1169047616 

TYPO3 Exception 1169047619 

TYPO3 Exception 1169128255 

RuntimeException('Tag "' . $tagName . '" does not exist.', 1169128255) 

This error happens for example if you mistype a doc comment tag.

A common error is using @param instead of @var for injections.

TYPO3 Exception 1170251400 

TYPO3 Exception 1170251401 

TYPO3 Exception 1170859526 

TYPO3 Exception 1176471352 

TYPO3 Exception 1176475350 

TYPO3 Exception 1176558158 

TYPO3 11.5.21 -03.01.2023 

An argument "site" does not exist for this request.
Copied!

Situation 

This happens when you call the following in an action of an Extbase controller:

$site =  $this->request->getArgument('site');
Copied!

Solution 

You must retrieve the site configuration with getAttribute() not getArgument:

$site =  $this->request->getAttribute('site');
Copied!

TYPO3 12.4.3 - 24.07.23 

Situation 

This error was thrown in the \TYPO3\CMS\Extbase\Mvc\Web\Routing\UriBuilder when calling it from a non-Extbase context

Solution 

Pass the current request object to the UriBuilder:

$uri = $uriBuilder->reset()
        ->setRequest($this->getExtbaseRequest())
        ->setTargetPageUid(188)
        // ...
        ->build();
Copied!

See also URI builder (Extbase).

TYPO3 Exception 1186669086 

TYPO3 Exception 1187176358 

#1187176358: The controller name must be a valid string, integer given. 

\TYPO3\CMS\Extbase\Mvc\Exception\InvalidControllerNameException thrown in file typo3_src/typo3/sysext/extbase/Classes/Mvc/Request.php.

Possible error sources 

configurePlugin: Actions declared incorrectly 

This error happens when the first array does have an integer as key instead of the plugin name:

array('show')
Copied!

The correct solution is this:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'FooExt',
    'PluginName',
    [\Foo\Ext\Controller\PluginController::class => 'show'],
    [\Foo\Ext\Controller\PluginController::class => 'show'] // non-cacheable actions
);
Copied!

TYPO3 Exception 1187176359 

TYPO3 Exception 1187530862 

TYPO3 Exception 1187530869 

TYPO3 Exception 1187701131 

TYPO3 Exception 1187701132 

TYPO3 Exception 1187807099 

TYPO3 Exception 1187807100 

TYPO3 Exception 1187951688 

TYPO3 Exception 1187953786 

TYPO3 Exception 1187953787 

TYPO3 Exception 1190034628 

TYPO3 Exception 1192450280 

TYPO3 Exception 1193315266 

TYPO3 Exception 1193326558 

TYPO3 Exception 1194041104 

TYPO3 Exception 1195039394 

TYPO3 Exception 1195043731 

TYPO3 Exception 1195043965 

$className must implement interface ContentObjectStdWrapHookInterface::class 

Happens if a hook defined in $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/class.tslib_content.php']['stdWrap'] does not implement the necessary interface. Please check all hooks registered.

TYPO3 Exception 1195044480 

TYPO3 Exception 1195114460 

TYPO3 Exception 1195115652 

TYPO3 Exception 1195115653 

TYPO3 Exception 1195125501 

TYPO3 Exception 1195126772 

$toolbarItem must implement interface TYPO3\CMS\Backend\Toolbar\ToolbarItemHookInterface 

  1. Check whether the requested class really implements TYPO3\\CMS\\Backend\\Toolbar\\ToolbarItemHookInterface

Exception on shortcut 

  1. The error might have been caused because the argument to the constructor was not passed by reference as requested by the Interface/Class. In general this causes just a warning but can also lead to serious problems.
  2. There's a bug in PHP 5.5.6+ which causes this Exception: https://forge.typo3.org/issues/53682

TYPO3 Exception 1195129553 

TYPO3 Exception 1195129642 

TYPO3 Exception 1195567840 

TYPO3 Exception 1195567845 

TYPO3 Exception 1195567850 

TYPO3 Exception 1195567855 

TYPO3 Exception 1195815178 

TYPO3 Exception 1195824959 

TYPO3 Exception 1202072000 

TYPO3 Exception 1202921619 

TYPO3 Exception 1203584729 

TYPO3 Exception 1203698223 

TYPO3 Exception 1203699034 

#1203699034: A cache with identifier "IDENTIFIER" does not exist. 

Solution 

Most likely you did not clear cache. You will not be able to do this from backend any more. Instead you have to remove all cache files from your instance manually.

For current TYPO3 versions: Remove typo3temp/var/cache/* or var/cache For TYPO3 6.x: Remove typo3temp/Cache/* folders. For 4.x: Remove all typo3conf/temp_* files.

See caching documentation.


This issue can also occur when you run a code from the Install Tool (e.g. when using upgrade wizard) context and the cache IDENTIFIER is defined in a 3rd party extension. Install tool doesn't load all extensions configuration, thus custom cache definition is not available. Try calling the upgrade wizard from CLI

./typo3cms upgrade:wizard --identifier=DatabaseRowsUpdateWizard
Copied!

In current versions of TYPO3 the Caching Framework is installed by default.

This exception may appear if you just upgraded your TYPO3 Core and have not removed the cache files in typo3conf.

To do so simply remove these files go to your TYPO3 Installation and in the shell type rm typo3conf/temp_CACHED_\* and reload the page.


If you have upgraded from v8.x to v9 or v10 then there is a possibility that cache configuration is defined with

::
$TYPO3_CONF_VARS['SYS']

Replace it with

::
$GLOBALS['TYPO3_CONF_VARS']['SYS']

and maybe you need to compare your datebase scheme again in the admin tools.

TYPO3 Exception 1203965200 

TYPO3 Exception 1204026251 

You probably ran into a race condition which is described in https://forge.typo3.org/issues/46205 and has been fixed in 6.0.5. Try to update to a newer TYPO3 version and clear your /typo3temp/cache/ folder.

Taken from http://stackoverflow.com/questions/16708012/cache-file-could-not-be-written-typo3-6-0-4


Additionally, this error might occur if you are over quota and or the disk is full.

TYPO3 Exception 1204111376 

TYPO3 Exception 1204481674 

TYPO3 Exception 1205414233 

No suitable request handler found. 

This can be caused when config.tx_extbase is not set in TypoScript which happens if extbase/ext_typoscript_setup.txt was not loaded.

The only known cause is that you don't have a TS template with "root template" flag set in your TS hierarchy.

If setting this flag is not an option for you (this may happen with inherited configuration templates such as "Use this template for next level"), then you may included it manually with

<INCLUDE_TYPOSCRIPT: source="FILE:typo3/sysext/extbase/ext_typoscript_setup.txt">
Copied!

TYPO3 Exception 1206031879 

Invalid configuration type 

It is explicit enough to understand that the TYPE can't be found, knowing you have three choices, all set in \\TYPO3\CMS\Extbase\Configuration\ConfigurationManagerInterface

  • 'Framework', which is set by CONFIGURATION_TYPE_FRAMEWORK
  • 'Settings', which is set by CONFIGURATION_TYPE_SETTINGS
  • 'FullTypoScript', which is set by CONFIGURATION_TYPE_FULL_TYPOSCRIPT

First, be sure you use only one of these three possibilities.

Then be sure you call the constant without quotes :

\TYPO3\CMS\Extbase\Configuration\ConfigurationManagerInterface::CONFIGURATION_TYPE_SETTINGS
Copied!

And not

'\TYPO3\CMS\Extbase\Configuration\ConfigurationManagerInterface::CONFIGURATION_TYPE_SETTINGS'
Copied!

TYPO3 Exception 1207020177 

TYPO3 Exception 1207149215 

TYPO3 Exception 1207149231 

TYPO3 Exception 1207253462 

TYPO3 Exception 1210858451 

TYPO3 Exception 1210858767 

Invalid argument name. 

The argument name is not a string (e.g. a number) or it is empty. Make sure the argument name satisfies the is_string method of PHP.

TYPO3 Exception 1210859206 

TYPO3 Exception 1210859212 

TYPO3 Exception 1211372741 

TYPO3 Exception 1212519195 

TYPO3 Exception 1213115903 

TYPO3 Exception 1213987706 

TYPO3 Exception 1216304300 

TYPO3 Exception 1216304301 

TYPO3 Exception 1216909923 

TYPO3 Exception 1217058190 

TYPO3 Exception 1217058192 

TYPO3 Exception 1217058196 

TYPO3 Exception 1217058197 

TYPO3 Exception 1217058198 

TYPO3 Exception 1217058199 

TYPO3 Exception 1217058200 

TYPO3 Exception 1217058202 

TYPO3 Exception 1217058203 

TYPO3 Exception 1217058204 

TYPO3 Exception 1217058205 

TYPO3 Exception 1217058209 

TYPO3 Exception 1217058211 

TYPO3 Exception 1217241834 

TYPO3 Exception 1217244746 

TYPO3 Exception 1217245454 

TYPO3 Exception 1217778382 

TYPO3 Exception 1217839467 

  • Could not ultimately dispatch the request after ' . $dispatchLoopCount . ' iterations. Most probably, a @' . TYPO3CMSExtbaseAnnotationIgnoreValidation::class . ' annotation is missing on re-displaying a form with validation errors.
  • Check if you have named the properties correctly in your fluid form and in your model class. In my case, this exception occurred simply because the property name of the form field in the fluid template did not match the property name in the corresponding model class.
  • Check if you have annotated @ignorevalidation $myObject in your action (or @dontvalidate for older Extbase version < 6.1)
  • Some hints (in German) can be found here: http://www.typo3.net/forum/beitraege/extbase_und_fluid/108844/

TYPO3 Exception 1217846412 

TYPO3 Exception 1217959510 

TYPO3 Exception 1217959511 

TYPO3 Exception 1218473352 

TYPO3 Exception 1218547409 

$className must implement interface PageLayoutViewDrawItemHookInterface::class 

  • Try deleting all caches
  • Older versions: Try deleting all files in typo3temp/autoload through console.

rm -rf typo3temp/autoload/*

Solution TYPO3 8.4.x and higher 

The way registering the hook has changed in ext_localconf.php:

   // Prior TYPO3 8
   // $TYPO3_CONF_VARS['SC_OPTIONS']['cms/layout/class.tx_cms_layout.php']['tt_content_drawItem'][] = 'EXT:extensionkey/Classes/Hooks/PageLayoutViewDrawItemHook.php:&Vendor\\Extensionkey\\Hooks\\PageLayoutViewDrawItemHook';

::

   // TYPO3 8:
   $TYPO3_CONF_VARS['SC_OPTIONS']['cms/layout/class.tx_cms_layout.php']['tt_content_drawItem'][] = 'Vendor\\Extensionkey\\Hooks\\PageLayoutViewDrawItemHook';
Copied!

TYPO3 Exception 1218636383 

TYPO3 Exception 1220526013 

TYPO3 Exception 1220526014 

TYPO3 Exception 1220539734 

TYPO3 Exception 1220539735 

TYPO3 Exception 1220539739 

TYPO3 Exception 1220541963 

TYPO3 Exception 1220722120 

TYPO3 Exception 1220722210 

TYPO3 Exception 1220722873 

TYPO3 Exception 1220884009 

TYPO3 Exception 1222361632 

The cache file could not be written 

#1222361632: The cache file "[...]/typo3temp/Cache/Data/t3lib_l10n/f376fbe33c1512a6e326035c17036b8e" could not be written.
Copied!

Solution 

Manually remove the file and try again.

TYPO3 Exception 1222808333 

TYPO3 Exception 1222871239 

TYPO3 Exception 1224237899 

TYPO3 Exception 1224241246 

TYPO3 Exception 1224254792 

Namespace could not be resolved. This exception should never be thrown! 

  • Most likely, you're using a ViewHelper or something that has its own namespace, but you didn't declare that namespace (e.g: missing {namespace myNamespace=Tx_MyExt_ViewHelpers} or with PHP namespaces: {namespace myNamespace=Vendor\MyExt\ViewHelpers}).
  • The quite common instance is using a VHS View Helper (e.g.``v:extension.path.resources``) without referencing the VHS namespace ({namespace v=Tx_Vhs_ViewHelpers}).
  • Also keep in mind that you may be required to declare namespace(s) in the partial(s) even though they where declared in the parent template.

TYPO3 Exception 1224256186 

TYPO3 Exception 1224479063 

TYPO3 Exception 1224479370 

TYPO3 Exception 1224479372 

TYPO3 Exception 1224485398 

Templating tags not properly nested 

#1224485398: Templating tags not properly nested. Expected: TYPO3\CMS\Fluid\ViewHelpers\Link\ExternalViewHelper;

Actual: TYPO3\CMS\Fluid\ViewHelpers\Link\UriViewHelper
Copied!

This error is triggered when the parser is finding that tags are not properly nested. Consult the manual for the correct nesting possibilities.

Solution 

You have to nest the ViewHelpers correctly, for example:

<f:link.external ..>   needs      </f:link.external>
Copied!

Error in ViewHelper 

If a viewHelper is not properly programmed, any argument might break templates. It's important to register all arguments properly to get the templates parsed correctly. To test a ViewHelper, remove all arguments in the fluid template to check if the nesting is recognized right without arguments. The error message is misleading in this case because the reason is not related to the notation in the template but to faults in the ViewHelper.

TYPO3 Exception 1224485838 

You closed a templating tag which you never opened! 

This error normally occurs, if you have a closing tag that does not match any opening tag.

#1224485838 TYPO3Fluid\Fluid\Core\Parser\Exception
Fluid parse error in template ..., line ... at character .... Error: You closed a templating tag which you never opened! (error code 1224485838). Template source chunk: </f:sometag>
Copied!

This additionally may occur if you try to write <f:sometag attribute_with_underscore="xxx">.

You cannot use underscores in attribute names e.g. for custom ViewHelpers.

TYPO3 Exception 1224592343 

TYPO3 Exception 1225136013 

TYPO3 Exception 1225136014 

TYPO3 Exception 1225418233 

TYPO3 Exception 1225709595 

The Fluid template files "" could not be loaded TYPO3 13.4.0, 2024-11-02 

Happens if you are trying to use a layout within a Fluid template that is included with FLUIDTEMPLATE but did not define any path to the layouts.

Solution:

page = PAGE
page {
 10 = FLUIDTEMPLATE
 10 {
    templateName = Default
    templateRootPaths.10 = EXT:site_package/Resources/Private/Templates/Pages/
+   partialRootPaths.10 = EXT:site_package/Resources/Private/Partials/Pages/
+   layoutRootPaths.10 = EXT:site_package/Resources/Private/Layouts/Pages/
  }
}
Copied!

Or use a PAGEVIEW which automatically configures these paths for you.

See also Troubleshooting TypoScript.

The Fluid template files "" could not be loaded 

Exception message:

#1225709595: The Fluid template files "" could not be loaded.
TYPO3Fluid\Fluid\View\Exception\InvalidTemplateResourceException
thrown in file

/var/www/site/htdocs/typo3_src/vendor/typo3fluid/fluid/src/View/TemplatePaths.php
in line 730.
Copied!

TYPO3 10+ 

This solution might work for most user of TYPO3 6+, though only tested with version 10.

Solution 1 

If you're using a standalone view, be sure to set the controller context. You can then adjust it to your taste if you want to. But at least set it for the view to work properly. Including your controller context will also cure most of your standalone view problems. The controller context already exists in your controller in the $this->controllerContext class field (others call it class property). All you have to do is include it in the $standaloneView->setControllerContext() method like this:

$standaloneView = GeneralUtility::makeInstance(StandaloneView::class);

$standaloneView->setControllerContext($this->controllerContext);

$standaloneView->setTemplatePathAndFilename('EXT:myextension/Resources/Private/Templates/'
. $this->template);

$standaloneView->assignMultiple($this->settings);

Copied!

Solution 2 

If you are running your view away from the Controllers, then make sure to fill in fillDefaultsByPackageName with your extension key:

$standaloneView = GeneralUtility::makeInstance(StandaloneView::class);

$standaloneView->getTemplatePaths()->fillDefaultsByPackageName('myextension');

$standaloneView->setTemplatePathAndFilename('EXT:myextention/Resources/Private/Templates/'
. $this->template); ...
Copied!

Older versions 

#1225709595: The template files ".../typo3conf/ext/blsvsa2013/Resources/Private/Partials/Model/Template.html" could not be loaded.

  • check if the template file exist.
  • If you set the format of our view manually in the controller like this: $this->request->setFormat('xml'); extbase is still looking for a file called youraction.html even if it eventually uses youraction.xml so you need to create both files, the html file can be empty. I think this is a bug and filled a bug report; https://forge.typo3.org/issues/46657

TYPO3 Exception 1225709596 

The template files * could not be loaded. 

The template files "/home/.....t3bootstrap/Resources/Private/Layouts/Content", "/home/....t3bootstrap/Resources/Private/Layouts/Content.html" could not be loaded.
Copied!

Reason 

Might happen when using Flux 7.0.0

Solution 

  • Maybe you have not included the fluidcontent_bootstrap in your template. Just include it.

TYPO3 Exception 1225709597 

The template files "", "" could not be loaded. 

The requested Fluid template (or Partial file linked from within a Template file) is missing. Verify the configured file path/s and any linked Partials, and check the (case-sensitive) filename/s.

In case the following error occurs

Oops, an error occurred!

The template files "", "" could not be loaded.

More information regarding this error might be available online.

make sure you are using a slash but not a backslash.

TYPO3CMS >= 6.2 

Make sure paths to partials DO NOT start with a slash.

  • Working (with ./typo3conf/ext/extension_with_super_cow_powers/Resources/Private/Partials/Product/TabWithGal.html present)
<f:render partial="Product/TabWithGal" arguments="{tab: tab}"/>
Copied!
  • Not Working (but worked in 6.1.x)
<f:render partial="/Product/TabWithGal" arguments="{tab: tab}"/>
Copied!

TYPO3 Exception 1225818110 

TYPO3 Exception 1225818120 

TYPO3 Exception 1227108982 

TYPO3 Exception 1227834741 

TYPO3 Exception 1228262000 

$hookObject must implement interface TYPO3\CMS\Backend\Toolbar\ClearCacheActionsHookInterface 

  • Try clearing the cache (via the Admin/Install Tool)
  • If this happens with your own code, check that $hookObject implements the required interface

TYPO3 Exception 1229531659 

TYPO3 Exception 1231178303 

TYPO3 Exception 1231178878 

TYPO3 Exception 1231259656 

TYPO3 Exception 1231267498 

Invalid cache backend option $optionKey for backend of type static::class 

Most likely your cache configuration and the configured backend do not match the configured options. Change or remove the options and try again.

If you change the backend to NullBackend, make sure you remove the options.

This setup will throw the exception:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_object']['backend'] = 'TYPO3\\CMS\\Core\\Cache\\Backend\\MemcachedBackend';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_object']['options'] = array('servers' => array('localhost:11211'),);
$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_object']['backend'] = 'TYPO3\\CMS\\Core\\Cache\\Backend\\NullBackend';

Copied!

If you want to set it to NullBackend, do it like this:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_object'] = array('backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\NullBackend');
Copied!

or clear the options:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations']['extbase_object']['options'] = array();
Copied!

TYPO3 Exception 1232044696 

TYPO3 Exception 1232044697 

TYPO3 Exception 1232551853 

TYPO3 Exception 1232969508 

TYPO3 Exception 1232985414 

The PHP extension "apc" or "apcu" must be installed and loaded in order to use the APC backend. 

If you've gotten this error message

Oops, an error occurred!

The PHP extension "apc" or "apcu" must be installed and loaded in order to use the APC backend.
Copied!

Then there are two methods, which will work.

  1. Install and configure apc on the server. Maybe APC is installed, but needs more memory.
  2. Goto TYPO3 Install Tool --> Configuration Presets and choose Database cache backend (or: something different then apc) and save.

TYPO3 Exception 1232985415 

TYPO3 Exception 1232985914 

The PHP extension "apcu" must be installed and loaded in order to use the APCu backend. 

  1. Install and configure apc on the server. Maybe APCu is installed, but needs more memory.
  2. Goto TYPO3 Install Tool --> Configuration Presets and choose Database cache backend (or: something different then apcu) and save.
  3. On a Hetzner server: Disable, save and then re-enable APC in Hetzner server management console to get it fixed.

TYPO3 Exception 1232985915 

The APCu backend cannot be used because apcu is disabled on CLI 

[ TYPO3\CMS\Core\Cache\Exception ]
#1232985915: The APCu backend cannot be used because apcu is disabled on CLI.
thrown in file typo3/sysext/core/Classes/Cache/Backend/ApcuBackend.php
in line 84
Copied!

This error occurs if TYPO3 is executed in command line context. The reason is, that typo3conf/LocalConfiguration.php uses TYPO3\\CMS\\Core\\Cache\\Backend\\ApcuBackend as caching backend, which works fine if called using an HTTP-context (e.g. via Apache or nginx) but does not if invoked via CLI (command line interface).

Solutions 

  1. Change Cache Backend: Goto TYPO3 Install Tool --> Configuration Presets and choose Database cache backend (or: something different then apcu) and save.
  2. Adjust PHP CLI configuration to fix this behavior: modify configuration file /etc/php/7.1/cli/conf.d/20-apcu.ini (as an example on Ubuntu 17.10) and add new setting apc.enable_cli=on

TYPO3 Exception 1232986118 

TYPO3 Exception 1232986125 

TYPO3 Exception 1232986277 

TYPO3 Exception 1232986571 

TYPO3 Exception 1232986818 

TYPO3 Exception 1232986825 

TYPO3 Exception 1232986877 

This happened after configuring TYPO3 6.2 to use the APC Backend for Extbase Cache and afterwards disabling the APC Cache module on the server. Solution is to re-enable the APC or delete the cache configuration from LocalConfiguration.php. Don't forget to clear the typo3temp/Cache afterwards.

This error will also occur if your apc cache runs out of memory - either give it more or as a quick temp fix clear out the cache with a minimal script like:

<?php apc_clear_cache();?>
Copied!

TYPO3 Exception 1232986971 

TYPO3 Exception 1233057359 

TYPO3 Exception 1233057360 

TYPO3 Exception 1233057512 

TYPO3 Exception 1233057566 

TYPO3 Exception 1233057752 

TYPO3 Exception 1233057753 

TYPO3 Exception 1233057772 

TYPO3 Exception 1233057773 

TYPO3 Exception 1233058264 

TYPO3 Exception 1233058269 

TYPO3 Exception 1233058294 

TYPO3 Exception 1233058312 

TYPO3 Exception 1233058486 

Invalid chars in identifier for the cache-instance 

Remove or replace the invalid characters from your identifier.

Interface: TYPO3CMSCoreCacheFrontendFrontendInterface 

const PATTERN_ENTRYIDENTIFIER = '/^[a-zA-Z0-9_%\\-&]{1,250}$/';
Copied!

Abstract Class: TYPO3CMSCoreCacheFrontendAbstractFrontend 

public function isValidEntryIdentifier($identifier) {
    return preg_match(self::PATTERN_ENTRYIDENTIFIER, $identifier) === 1;
}
Copied!

file ext_autoload.php 

An invalid character in the file ext_autoload.php causes this error message.

return array(
 'Agency\\TtProductsAgency\\Hooks\\Marker;'
 => $extensionPath . 'Classes/Hooks/Marker.php',
);
Copied!

Here a semicolon is wrong at "Marker;". The error message invents a class name of its own. It does not exist anywhere: ..._hooks_marker

'Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1233058486:
\"agency_ttproductsagency_hooks_marker;\" is not a valid cache entry identifier.
| InvalidArgumentException thrown in file
/usr/www/users/myuser/typo3_src-6.2.14/typo3/sysext/core/Classes
/Cache/Frontend/AbstractFrontend.php in line 85. Requested URL:
Copied!

EXT:be_acl:: Version 1.7.3 and above 

From version 1.7.3 on the cache identifier includes the "usergroup_cached_list" of the backend user object. If there are too many usergroups in the list, the string of the cache identifier gets longer than 250 characters. So the validation fails. (See also the constant in the first paragraph).

TYPO3 Exception 1233058495 

TYPO3 Exception 1233072774 

TYPO3 Exception 1233180480 

The method "yourMethod" is not supported by the repository 

Analysis 

  • check if the method yourMethod is not defined in the repository, also with respect to spelling (lowercase and uppercase).
  • check the visibility of the method (public, protected, private)

Solution 

  • define the method yourMethod or correct the spelling.
  • change the visibility of the method to public if it's called from a controller or somewhere else outside the repository itself. If the method is called from a sub-repository-class the visibility can be either public too or protected but not private.

TYPO3 Exception 1233775407 

TYPO3 Exception 1233863842 

TYPO3 Exception 1234386924 

TYPO3 13.5.9, 2025-05-12 Cannot create empty instance of the class "ObjectStorage"... 

Happened when in an Extbase Model (AbstractEntity) the object Storage was missing information about the type of objects to be saved.

Saved like this:

 class Theme extends AbstractEntity
 {
   protected string $name = '';
+  /** @var ?ObjectStorage<InfoCenter>  */
   protected ?ObjectStorage $infoCenter = null;
Copied!

Error-messages: 

  1. #1234386924: Cannot create empty instance of the class "TYPO3CMSExtbaseDomainRepositoryFrontendUserRepository" because it does not implement the TYPO3CMSExtbaseDomainObjectDomainObjectInterface.
  2. #1234386924: Cannot create empty instance of the class "TYPO3CMSExtbasePersistenceObjectStorage" because it does not implement the TYPO3CMSExtbaseDomainObjectDomainObjectInterface.

Fix 

Assure that all classes in your model files are defined and annotated correctly.

Below is an example for one property of another table:

/**
  * contact
  *
  * @var \Vendor\Extension\Domain\Model\Contact
  */
 protected $contact = NULL;


 /**
  * Returns the contact
  *
  * @return \Vendor\Extension\Domain\Model\Contact $contact
  */
 public function getContact() {
     return $this->contact;
 }

 /**
  * Sets the contact
  *
  * @param \Vendor\Extension\Domain\Model\Contact $contact
  * @return void
  */
 public function setContact(\Vendor\Extension\Domain\Model\Contact $contact) {
     $this->contact = $contact;
 }
Copied!

A more complicated example is when records or files are handled by ObjectStorage, this is an Object where several items can be stored and items can be added and removed from a stack:

/**
 * member
 *
 * @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\Extension\Domain\Model\Member>
 */
 protected $member = NULL;

/**
 * __construct
 */
public function __construct() {
    //Do not remove the next line: It would break the functionality
    $this->initStorageObjects();
}

/**
 * Initializes all ObjectStorage properties
 * Do not modify this method!
 * It will be rewritten on each save in the extension builder
 * You may modify the constructor of this class instead
 *
 * @return void
 */
protected function initStorageObjects() {
    $this->member = new \TYPO3\CMS\Extbase\Persistence\ObjectStorage();
}

/**
 * Adds a member
 *
 * @param \Vendor\Extension\Domain\Model\Member $member
 * @return void
 */
public function addMember(\Vendor\Extension\Domain\Model\Member $member) {
    $this->member->attach($member);
}

/**
 * Removes a member
 *
 * @param $memberToRemove The member to be removed
 * @return void
 */
public function removeMember(\Vendor\Extension\Domain\Model\Member $memberToRemove) {
    $this->member->detach($memberToRemove);
}

/**
 * Returns the member
 *
 * @return \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\Extension\Domain\Model\Member> $member
 */
public function getMember() {
    return $this->member;
}

/**
 * Sets the member
 *
 * @param \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\Extension\Domain\Model\Member> $member
 * @return void
 */
public function setMember(\TYPO3\CMS\Extbase\Persistence\ObjectStorage $member) {
    $this->member = $member;
}
Copied!

TYPO3 Exception 1235225797 

TYPO3 Exception 1235428779 

TYPO3 Exception 1235428780 

TYPO3 Exception 1236080693 

TYPO3 Exception 1236080702 

TYPO3 Exception 1236081302 

TYPO3 Exception 1236518288 

TYPO3 Exception 1236518298 

TYPO3 Exception 1237301367 

TYPO3 Exception 1237301368 

TYPO3 Exception 1237301369 

TYPO3 Exception 1237301370 

TYPO3 Exception 1237305720 

TYPO3 Exception 1237370877 

TYPO3 Exception 1237823695 

General 

Register arguments of viewhelpers describes how to register own Arguments for viewHelpers. Never denying that I might have made a fault I never had success with the simple notation by using several parameters in the render-function. I succeeded with the solution to register the arguments in the function initializeArguments() which is automatically called if present in the viewHelper.

PHPStorm 

The error shown is “Argument "xmlns:f" was not registered”.

PHPStorm sometimes adds a xmlns attribute to the very first tag in a Fluid Template, if you use auto completion (eg. type in »f:comm« and hit enter to autocomplete to »<f:comment></f:comment>«). If the first tag in your template happens to be a Fluid tag, then the Fluid parser will throw the execption, that »xmlns« is in fact not a valid attribute of the current Fluid tag.

Issue on Forge: https://forge.typo3.org/issues/56481

Solution 1 - Remove the attribute 

Just remove the wrong xmlns attribute from your Fluid tag


Wrong (xmlns isn't a valid attribute for this tag):
<f:layout name="Page/Homepage" xmlns:f="http://www.w3.org/1999/html"/>

Right:
<f:layout name="Page/Homepage" />
Copied!

Solution 2 - Register the namespace 

PHPStorm needs to know about the fluid namespace, then it will not add those attributes by itself anymore. Wrap your template into a DIV like this:


<div xmlns="http://www.w3.org/1999/xhtml" lang="en"
     xmlns:f="https://typo3.org/ns/fluid/ViewHelpers"
>

    <!-- Fluid goes here -->

</div>
Copied!

See http://buzz.typo3.org/teams/extbase/article/howto-autocompletion-for-fluid-in-phpstorm/ & https://fluidtypo3.org/documentation/templating-manual/appendix/fluid-autocompletion.html

Fluid 6.1 select ViewHelper 

Argument "prependContent" was not registered

<f:form.select name="formtype" options="{formtype}" optionLabelField="title" prependContent="TRUE">

<option value="0">--please choose--</option>

</f:form.select>

EXT:news 

If you get this problem in the "news" extensions, it might be linked to the viewhelper => "hsc". Try with the original template form the extension.

EXT:roq_newsevent 

After update of roq_newsevent, (or for no apparent reason) the error appears in relation with roq_newsevent template : /Partials/EventList/item.html

The viewhelper linking to single view have to be updated :

Original version : <e:link newsItem="{newsItem}" settings="{settings}" action="eventDetail">{newsItem.title}</e:link>

Updated and working version : <n:link newsItem="{newsItem}" settings="{settings}">{newsItem.title}</n:link>

See on TYPO3 Forge here : https://forge.typo3.org/issues/53921

Upgrade to TYPO3 7.6.2 

The Extension Manager does not work and gives this error message:

Uncaught TYPO3 Exception
#1237823695: Argument "jQueryNamespace" was not registered. (More information)
TYPO3\CMS\Fluid\Core\Parser\Exception thrown in file
/var/www/html/developer/typo3_src-7.6.2/typo3/sysext/fluid/Classes/Core/Parser /TemplateParser.php in line 604.
19 TYPO3\CMS\Fluid\Core\Parser \TemplateParser::abortIfUnregisteredArgumentsExist(array, array)
/var/www/html/developer/typo3_src-7.6.2/typo3/sysext/fluid/Classes/Core/Parser/TemplateParser.php:
00563:         // The following three checks are only done *in an uncached template*, and not needed anymore in the cached version
00564:         $expectedViewHelperArguments = $viewHelper->prepareArguments();
00565:         $this->abortIfUnregisteredArgumentsExist($expectedViewHelperArguments, $argumentsObjectTree);
00566:           $this->abortIfRequiredArgumentsAreMissing($expectedViewHelperArguments, $argumentsObjectTree);
00567:         $this->rewriteBooleanNodesInArgumentsObjectTree($expectedViewHelperArguments, $argumentsObjectTree);
Copied!

Solution: Start the Install Tool and press the button "Clear all cache".

Removal of deprecated code in sysext fluid 

See Breaking: #53542 - Removal of deprecated code in sysext fluid

For example: f:be.container arguments

Error Argument "addCssFile" was not registered

Use includeCssFiles instead of addCssFile and adapt value from string to array

addCssFile="{f:uri.resource(path:'Css/backend.css')}"

includeCssFiles="{0:'{f:uri.resource(path:\'Css/backend.css\')}'}"

TYPO3 Exception 1237823699 

#1237823699: Required argument "controller" was not supplied. 

Just add the parameter controller to the be.menus.actionMenuItem ViewHelper:

<f:be.menus.actionMenuItem controller="YourController" label="YourLabel" action="YourAction" />
Copied!

Required argument "viewHelperArgument" was not supplied. Is thrown if you use a view Helper in your fluid template without a required argument.

#1237823699: Required argument "each" was not supplied. 

<f:for each="{menu}" as="menuEntry" key="table">
...
<f:for>
Copied!

You must add the parameter 'menu' to the call from the PHP side.

$assigns['menu'] = $menu;
$view->assignMultiple($assigns);
Copied!

And you must have the correct syntax of the "f:for"-ViewHelper.

<f:for each="{menu}" as="menuEntry" key="table">
...
</f:for>
Copied!

#1237823699 Error: Required argument "colPos" was not supplied. 

TYPO3 with flux and fluidcontent - Upgraded to version 9.

Issue 1: Fluidcontent needs to be migrated to Flux: https://github.com/FluidTYPO3/fluidcontent/issues/424 → Run SQL Statement https://stackoverflow.com/a/50759394/3894752

Issue 2: Flux now requires colPos attributes for content elements as well: https://github.com/FluidTYPO3/flux/issues/1599 → Add colPos attribute to all grids with numbers from 0 to 99. The Update script of flux will then fix the colPos Value in the database automatically. https://github.com/FluidTYPO3/flux/issues/1594#issuecomment-408886174

#1237823699 Error: Required argument "error" was not supplied. 

Issue: Upgrade of Form Framework from Version 9 to 11. Frontend shows exception about missing error translation argument.

Solution: Compare markup of the original Partial (typo3/sysext/form/Resources/Private/Frontend/Partials/Field/Field.html) to your custom Partial.

Before:

{formvh:translateElementError(element: element, code: error.code, arguments: error.arguments, defaultValue: error.message)}

After:

{formvh:translateElementError(element: element, error: error)}

TYPO3 Exception 1237900529 

News2 

#1237900529: The argument "configuration" was registered with type "array", but is of type "NULL" in view helper "Tx_News2_ViewHelpers_Widget_PaginateViewHelper"
Copied!

You forgot to include the static template for news2. Open your template record and go to Includes-->Include static (from extension). Select news v2 (news) from the list and save your template record. Reload you frontend page.

Fluid Template 

#1237900529: The argument "arguments" was registered with type "array", but is of type "string" in view helper "Tx_Fluid_ViewHelpers_TranslateViewHelper"
Copied!

If you've noted something like this:

<f:for each="{newsItem.author}" as="currentAuthor">
<f:translate key="author" arguments="{currentAuthor.name}" />
</f:for>
Copied!

you can change writing like this:

<f:for each="{newsItem.author}" as="currentAuthor">
<f:translate key="author" arguments="{0: currentAuthor.name}" />
</f:for>
Copied!

Usually for the news-extension this is not the case, but I changed the author field to include several records from fe_users. Therefore {newsItem.author} is an array and has to be looped.

<f:for> 

#1237900529: The argument "each" was registered with type "array", but is of type "string" in view helper "TYPO3\CMS\Fluid\ViewHelpers\ForViewHelper"
Copied!

The above exception is thrown by the following snippet:

<f:for each="{ jobs }" as="job">{job.id}</f:for>
Copied!

Removing the spaces after { and before } is my solution to the problem:

<f:for each="{jobs}" as="job">{job.id}</f:for>
Copied!

Please note the discussion at: https://forge.typo3.org/issues/64317

<f:form.select> 

<f:form.select options="{
                          1: 'Bauhauptgewerbe',
                             Straßenbauer: '- Straßenbauer'}/>
Copied!

Replace all special chars like "ß, ä, ö, ü, ..." by english letters.

<f:form.select options="{
                          1: 'Bauhauptgewerbe',
                             Strassenbauer: '- Straßenbauer'}/>
Copied!

TYPO3 Exception 1237991809 

TYPO3 Exception 1238068475 

TYPO3 Exception 1238070163 

TYPO3 Exception 1238107096 

TYPO3 Exception 1238110957 

TYPO3 Exception 1238169398 

TYPO3 Exception 1238244992 

TYPO3 Exception 1238244993 

TYPO3 Exception 1239853109 

TYPO3 Exception 1239891987 

TYPO3 Exception 1239891988 

TYPO3 Exception 1239891989 

TYPO3 Exception 1239891990 

TYPO3 Exception 1239891991 

TYPO3 Exception 1239896904 

TYPO3 Exception 1240227732 

TYPO3 Exception 1241079561 

TYPO3 Exception 1241079562 

TYPO3 Exception 1241098027 

Invalid validate annotation 

Check the annotation.

#1241098027: Invalid validate annotation in Vnd\Extname\Domain\SomeObj::phone: Could not resolve class name for validator "".
Copied!

TYPO3 Exception 1241099149 

TYPO3 Exception 1241722579 

Error-Message: 

(1/1) #1241722579 TYPO3Fluid\Fluid\Core\ViewHelper\Exception

"@" could not be parsed by \\DateTime constructor:
DateTime::__construct(): Failed to parse time string (@) at position 0
(@): Unexpected character
Copied!

Solution 

Adjust usage of viewHelper to respect the requirements.

Cases where it can happen are beside general faults that an extension is updated and the templates are outdated.

TYPO3 Exception 1242292003 

could not determine type of argument "section" of the render-method in ViewHelper "Tx_Fluid_ViewHelpers_RenderViewHelper" 

This exception is thrown if the PHPDoc @param entry in a Fluid ViewHelper is incorrect or if you are using a PHP optimizer with opcode caching like the builtin Opcache and have disabled the storing of PHPDoc blocks. Fluid ViewHelpers needed the PHPDoc entries to determine the data type (in older TYPO3 versions).

#1242292003: could not determine type of argument "section" of the
  render-method in ViewHelper "Tx_Fluid_ViewHelpers_RenderViewHelper".
Either the methods docComment is invalid or some PHP optimizer strips off
  comments.
Copied!

Solution:

  1. check PHPDoc block, it must start with ** (two stars).
  2. attribute must be mentioned as @param type $variableName.
  3. alternatively use $this->registerArgument() in initializeArguments() method.
  4. If using eAccelerator: compile eAccelerator with option "--with-eaccelerator-doc-comment-inclusion": "If you want eAccelerator to retain doc-comments in internal php structures" (eAccelerator help)
  5. Use another PHP optimizer. I use xCache on Debian Squeeze which seems to work fine.
  6. using the opcode cache of modern PHP versions, you can set opcache.save_comments=1 (and opcache.load_comments=1 in PHP < 7.0).

Links:

TYPO3 Exception 1242668976 

TYPO3 Exception 1242669004 

TYPO3 Exception 1242669031 

TYPO3 Exception 1242816073 

TYPO3 Exception 1242816074 

Unsupported order encountered. 

#1242816074: Unsupported order encountered.
Copied!

Solution: There is something wrong with your query, look at: $query->setOrderings

TYPO3 Exception 1242816075 

TYPO3 Exception 1243258395 

TYPO3 Exception 1243258396 

TYPO3 Exception 1243325768 

TYPO3 Exception 1243352010 

The key "TYPO3CMSFluidViewHelpersFormViewHelper->fieldNamePrefix" was already stored and you cannot override it. 

This exception occurs if a f:form.xxxx viewhelper is used before the f:form VH is used, or if f:form tags are nested.

TYPO3 Exception 1243352249 

TYPO3 Exception 1244201848 

A boolean expression has more than tree parts. 

Exception message:

Oops, an error occurred!

A boolean expression has more than tree parts.
Copied!

The error happens when you have a Fluid f:if tag with a syntax error in the condition attribute.

TYPO3 Exception 1244234398 

TYPO3 Exception 1244465558 

TYPO3 Exception 1245071870 

TYPO3 Exception 1245071872 

TYPO3 Exception 1245071889 

TYPO3 Exception 1245673367 

The given class "Tx_Extname_Classname" is not a registered object. 

I get this error after installing an Extension which tries to use a Class not defined in any of the typical Extbase Autoloader locations.

Oops, an error occurred!

The given class "Tx_Extname_Classname" is not a registered object.
Copied!

Occurs in: typo3/sysext/extbase/Classes/SignalSlot/Dispatcher.php

throw new Tx_Extbase_SignalSlot_Exception_InvalidSlotException(sprintf('Cannot dispatch %s::%s to class %s. The object manager is not yet available in the Signal Slot Dispatcher and therefore it cannot dispatch classes.', $signalClassName, $signalName, $slotInformation['class']), 1298113624);
    }
    if (!$this->objectManager->isRegistered($slotInformation['class'])) {
        throw new Tx_Extbase_SignalSlot_Exception_InvalidSlotException('The given class "' . $slotInformation['class'] . '" is not a registered object.', 1245673367);
    }
    $object = $this->objectManager->get($slotInformation['class']);
}
Copied!
  • caused by mismatch between the classname in the signal slot (in ext_tables.php) and the namespace/classname combination (fully qualified class name) in Classes/Controller/XxxController.php

TYPO3 Exception 1245673368 

Method postFolderCopy() does not exist. 

  1. Logged into the backend as an admin.
  2. Tried to copy & paste a folder with subfolders in the file list module.
  3. When pasting into another folder, this error is displayed in the main window:

    Oops, an error occurred!
    The slot method Causal\FileList\Slots\ResourceStorage->postFolderCopy() does not exist.
    More information regarding this error might be available online.
    Copied!
  4. Extension causal/file_list is installed

TYPO3 Exception 1246892970 

TYPO3 Exception 1246892972 

TYPO3 Exception 1247581135 

TYPO3 Exception 1247602160 

Tx_Extbase_Persistence_Storage_Exception_SqlError 

Tables or Fields missing, database needs to be updated 

#1247602160: Unknown column 'tx_yourext_domain_model_yourmodel.sorting' ...
Copied!

Make sure the Database tables are up to date. Go to the ExtensionManager and deactivate and activate the Extension or choose "Database Update" in the detail-view of an extension. Alternatively you can use the install-Tools "Database Analyser" to update all table definitions, choose "Update required tables COMPARE".

Model mapping incorrect or missing 

--#1247602160: Table 'my_database.tx_extendpages_domain_model_page' doesn't exist:
SELECT tx_extendpages_domain_model_page.* FROM tx_extendpages_domain_model_page
WHERE tx_extendpages_domain_model_page.uid = '56' LIMIT 1
Copied!

can happen if you didn't map the table and model via TypoScript.

To solve this problem map the model to the corresponding database table name. The syntax for the upper example is the following:

plugin.tx_extendpages.persistence.classes.Tx_Extendpages_Domain_Model_Page.mapping.tableName = pages
Copied!

'tx_extbase_domain_model_backenduser' doesn't exist 

--#1247602160: Table 'database.tx_extbase_domain_model_backenduser' doesn't exist:
SELECT tx_extbase_domain_model_backenduser.*
FROM tx_extbase_domain_model_backenduser
WHERE tx_extbase_domain_model_backenduser.uid = '1'
LIMIT 1
Copied!

See also: https://forge.typo3.org/issues/51234

Adding this code to the TypoScript, on all pages where is_siteroot is set, seems to solve this issue:

config.tx_extbase.persistence.classes {
    TYPO3\CMS\Beuser\Domain\Model\BackendUser {
        mapping {
            tableName = be_users
            columns {
                allowed_languages.mapOnProperty = allowedLanguages
                file_mountpoints.mapOnProperty = fileMountPoints
                db_mountpoints.mapOnProperty = dbMountPoints
                usergroup.mapOnProperty = backendUserGroups
            }
        }
    }
    TYPO3\CMS\Beuser\Domain\Model\BackendUserGroup {
        mapping {
            tableName = be_groups
            columns {
                subgroup.mapOnProperty = subGroups
            }
        }
    }
}
Copied!

'tx_staticinfotables_domain_model_language' doesn't exist 

Oops, an error occurred!
Table '[DB_NAME.tx_staticinfotables_domain_model_language' doesn't exist.
More information regarding this error might be available online.
Copied!

No good solution found so far, will report in if solution is found.

Temporary solution would be to create table with 608 empty records, to be able to create and edit records in backend on page [0],

otherwise TYPO3 will display error message and you can not edit anything on page [0].

CREATE TABLE `tx_staticinfotables_domain_model_language` (
  `uid` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `constructed_language` varchar(255) DEFAULT NULL,
  `sacred_language` varchar(255) DEFAULT NULL,
  `iso_code_a2` varchar(5) DEFAULT NULL,
  `country_iso_code_a2` varchar(5) DEFAULT NULL,
  PRIMARY KEY (`uid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Copied!

Try inserting the extbase mapping typoscript in the setup of your General Record Storage Page:

<INCLUDE_TYPOSCRIPT: source="FILE:EXT:static_info_tables/Configuration/TypoScript/Extbase/setup.txt">
Copied!

'tx_srlanguagemenu_domain_model_systemlanguage' doesn't exist 

This occurs when the sr_language_menu extension is installed, but not configured right.

Please make sure, that you include the "Language Menu Setup (sr_language_menu)" in

Templates->Edit the whole template record->Includes: Language Menu Setup (sr_language_menu)!

Secondly take a look a the static info tables extension and make sure that you have installed the infotables for all required languages!

'tx_news_domain_model_filereference' doesn't exist 

See https://forge.typo3.org/issues/58925 and https://forge.typo3.org/issues/58784 I actually had the current version already (merging an upgraded dev instance with the live site), but I had to include the static templates and clear all caches, also truncate cf_ tables manually. Now it works.

MySQL max_allowed_packet 

If only one Plugin/Site stops with "MySQL server has gone away" and all other are working..

Increase the MySQL max_allowed_packet value.

Powermail 2 formconverter: Unknown column 'fs.class' in 'field list' 

Error encountered using formconverter after updating powermail from v1.4.x. Intermediate versions (1.6 to 2.0?) used to have field "class" in tables "tx_powermail_fieldsets" and "tx_powermail_fields". Add it manually to both tables, and formconverter will work (remove fields via DB COMPARE when done):

alter table tx_powermail_fieldsets add column class text NOT NULL;
alter table tx_powermail_fields add column class text NOT NULL;
Copied!

SQL Mode not compatible 

In some cases the query is okay, but not compatible with the current sql_mode of the MySQL Database.

Check your sql_mode

mysql> SELECT @@sql_mode;
+-------------------------------------------------------------------------------------------------------------------------------------------+
| @@sql_mode                                                                                                                                |
+-------------------------------------------------------------------------------------------------------------------------------------------+
| ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION |
+-------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0,00 sec)
Copied!

Try to remove some of these modes in »/etc/mysql/my.conf«

> [mysqld]
> sql_mode=NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
Copied!

TYPO3 Exception 1247826696 

TYPO3 Exception 1247827244 

TYPO3 Exception 1247827245 

TYPO3 Exception 1247827428 

TYPO3 Exception 1247827553 

TYPO3 Exception 1248261038 

TYPO3 Exception 1248356140 

TYPO3 Exception 1248363335 

TYPO3 Exception 1248363336 

TYPO3 Exception 1248363434 

TYPO3 Exception 1248363439 

TYPO3 Exception 1248689115 

TYPO3 Exception 1248701951 

TYPO3 Exception 1248710426 

TYPO3 Exception 1248728393 

TYPO3 Exception 1248728394 

TYPO3 Exception 1249479625 

TYPO3 Exception 1249479819 

Persistence 

You need to make sure that your object is already persisted before calling Repository->update($o); Add it first with Repository->add($o);

Usage of (new) property mapper / t3extblog 

I encountered this exception when trying to install/use t3extblog with TYPO3 6.2.10. Check your code for correct usage of (new) property mapper, this should give you a hint (taken from https://forge.typo3.org/issues/51330):

old property mapper is not supported anymore and removed from the Core after 6.2. Use the new one instead.

For those who do not know how to fix it, I will show how I have fixed it.

Old code:

$persistenceManager =
\\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('Tx_Extbase_Persistence_Manager');
Copied!

New code:

$objectManager =
\\TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(\TYPO3\CMS\Extbase\Object\ObjectManager::class);
$persistenceManager =
$objectManager->get(\TYPO3\CMS\Extbase\Persistence\Generic\PersistenceManager::class);
Copied!

Object retrieved by property mapper can't get updated via persistence manager 

If you try to ->update() an object which has been retrieved from the property mapper by mapping GET/POST parameters, so if you pass the object as argument of your controller action, this issue may occur.

For me the solution was to re-retrieve the object using the repository and ->findByUid() method and then persist/update the retrieved object. It seems the repository needs to "know" about the object.

function yourAction(\Some\Model $item)
{
    $updateItem = $this->itemRepository->findByUid($item->getUid());
    /**
     *  something with $updateItem ...
     */
    $this->itemRepository->update($updateItem);
}
Copied!

TYPO3 Exception 1249755131 

TYPO3 Exception 1250596541 

TYPO3 Exception 1250715528 

TYPO3 Exception 1250715544 

#1250715544: Task is past end date 

OutOfBoundsException thrown in file typo3/sysext/scheduler/Classes/Execution.php.

This happens if you try to forcefully execute a task that has the endtime set before now. Make sure that the endtime is set properly before running a task.

It might also happen if you try to save a "single" task with the an enddate set, e.g. if you convert a recurring task to a single task.

TYPO3 Exception 1251232849 

TYPO3 Exception 1251315965 

TYPO3 Exception 1251315966 

TYPO3 Exception 1251315967 

This exception rose in one installation (TYPO3 4.6.9-15) after changing direction of relations in the Extension Builder between two models after having already inserted some entries to the list-view in the backend.

Deleting the files typo3conf/temp_CACHED_\* and truncating the caching-framework-tables beginning with cf\_ helped for me.

// Additional Situations, observed in TYPO3 6.1.2, Extbase 6 This exception is also thrown when, in the course of development:

  • a variable is changed, e.g. from CamelCase to non-CamelCase:

    protected $pressReview
    protected $pressreview
    Copied!
  • a variable annotation is changed, e.g. from CamelCase to Non-CamelCase:

    /**
     * @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\MyExtension\Domain\Model\PressReviews>
     */
    
    /**
     * @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Vendor\MyExtension\Domain\Model\Pressreviews>
     */
    Copied!

(Working in the files directly, not using the Extension Builder [anymore]) In my case, the truncating of the cf_-tables was sufficient.

Extension Builder bug 

In another case, this occurred in the Extension Builder v6.2.0 after the modification of an extension via the Extension Builder to add a new model object and relate it in a 1:n relation. The previously created model, which was meant to hold a set (n) of the new model, was missing the new model in the new dependency injections. The code generated was missing the new model's extbase path.

To fix this:

  • Find all sections where the new model path is missing and add it

    • e.g. from \TYPO3CMSExtbasePersistenceObjectStorage<> to \TYPO3CMSExtbasePersistenceObjectStorage<{VendorName}{Ext}DomainModel{NewModel}> in the protected variable
    • in the get/set/add/edit functions in the body, e.g. the 'add' function
/**
* Adds a {newModel}
*
* @param ${newModel}
* @return void
*/

 Change to

/**
* Adds a {newModel}
 *
* @param \{VendorName}\{Ext}\Domain\Model\{NewModel} ${newModel}
* @return void
*/

Copied!
  • Clear TYPO3 Caches
  • Delete typo3temp/*
  • As stated before, truncating the cf_-tables was needed before the error stopped.
  • May also be caused by incorrectly formatted comments - a missing * on the first line (only having one star) will stop the parser finding the definitions.
  • The error occurs also if you have missing annotation in your model.

TYPO3 Exception 1251476766 

TYPO3 Exception 1251730701 

TYPO3 Exception 1251730702 

TYPO3 Exception 1251814355 

TYPO3 Exception 1251892472 

TYPO3 Exception 1252502725 

TYPO3 Exception 1252514486 

TYPO3 Exception 1253036401 

argument "path" was already defined and should not be defined again 

This error ( argument "path" was already defined and should not be
defined again ) is caused by an extension viewhelper registering its' arguments differently after an upgrade. Clear the cache from install tool solves it.

This error occurred, after upgrading from TYPO3 CMS 7 to 8 having a custom view helper extending TYPO3\CMS\Fluid\ViewHelpers\ImageViewHelper. The registering of arguments changed from CMS 7 to 8. In 7 most of the arguments where defined in the signature of the render() method. That changed in CMS 8. In my view helper the arguments were still in the signature causing this error.

TYPO3 Exception 1253108907 

TYPO3 Exception 1253120365 

TYPO3 Exception 1253172726 

TYPO3 Exception 1253175643 

The argument type for parameter $parameter of method ... could not be detected. 

1253175643: The argument type for parameter $parameter of method Tx_yourExtensionKey_Controller_yourController->yourAction() could not be detected.

The GET/POST vars to action parameter mapping works only for objects or arrays and not for strings.

To get an string argument you have to fetch it by your own from the request object in your action method:

if ($this->request->hasArgument('parameter')) {

    $keyword = $this->request->getArgument('parameter');

}
Copied!

TYPO3 Exception 1253191023 

TypoScript object path "tt_content.list.20.your_extension" does not exist 

Missing content rendering definition 

Using fluid_styled_content: had to add a list entry for my current plugin. fluid_styled_content needs you to override its default if you change the templateRootPaths. Meaning that when overriding lib.fluidContent, you need to add something like this:

lib.fluidContent {
    templateName = YourTemplateName
    templateRootPaths {
        30 = EXT:myext/Resources/Private/Templates
    }
    layoutRootPaths {
        30 = EXT:myext/Resources/Private/Layouts
    }
    partialRootPaths {
        30 = EXT:myext/Resources/Private/Partials
    }
    list {
        templateName = YourListTemplateName
    }
}

Copied!

Removed/inactive extension 

TYPO3Fluid\Fluid\Core\ViewHelper\Exception
TypoScript object path "tt_content.list.your_extension." does not exist
Copied!

This could be cause by a frontend plugin from an extension which has been removed/deactivated in the meantime.

A possible fix is hiding/removing the plugin or installing/activating the related extension again.

TypoScript object path "tt_content..20" does not exist 

TYPO3 12.4.20, 27.09.2024

See https://forge.typo3.org/issues/105135

TYPO3 Exception 1253191060 

Could not get image resource for ... 

A ViewHelper tries to load an non-existing image.

The exception is thrown in VHS package.

Try the find the Content Element with the missing file and replace it.

Sometimes a ViewHelper tries to generate an image and pass it to the image ViewHelper. For example the vhs/Classes/ViewHelpers/Media/PdfThumbnailViewHelper.php class tries to generate a file in typo3temp/assets/.... Due to wrong access right it was not able to save the file, passed it to the Image ViewHelper which then raised the exception.

TYPO3 Exception 1253191784 

TYPO3 Exception 1253208523 

TYPO3 Exception 1254325546 

Occurrence in Frontend 

The page is shown without the common template but just with brown background and the typical TYPO3 Error-Message: "Oops an Error occurred" This happens even without realUrl. After deactivating a content element with powermail the page worked again, but the desired powermail-form was surly missing.

Occurrence in Backend 

Going in the Powermail-Module (Web -> Mails) and choosing Function-Check I got the brown background with another Error-Message shown:

Cookie was not set since HTTPS was forced in $TYPO3_CONF_VARS[SYS][cookieSecure].

Steps without Success 

  • Changing the version of Powermail is NOT fixing the Errors.
  • Uninstalling or deactivating realUrl is NOT fixing the Errors.

Fixing the Errors and Misbehavior 

In the Admin-Tool set $TYPO3_CONF_VARS[SYS][cookieSecure]=2 or $TYPO3_CONF_VARS[SYS][cookieSecure]=0

TYPO3 Exception 1255069587 

TYPO3 Exception 1255069597 

Go to TYPO3 Install tool -> All Configurations -> [encryptionKey] and add an encryptionKey.

http://blog.joergboesche.de/typo3-cms-encryption-key-was-empty-exception

TYPO3 Exception 1255072196 

TYPO3 Exception 1255072197 

TYPO3 Exception 1255072587 

TYPO3 Exception 1255072588 

TYPO3 Exception 1255072832 

The form field "[items][][]" is invalid. 

The form field "[items][][]" is invalid. Reason: "[]" used not as last argument, but somewhere in the middle (like foo[][bar]).

The value of "name" is missing in the form field.

For example at the selecting field:

<f:form.select '''name="paymentOptions"''' options="{payPal: 'PayPal International Services', visa: 'VISA Card'}" value="visa" />

Copied!

The error also occurs having a Fluid template like

<f:for each="{collection}" as="item" key="key">
  <f:form.checkbox name="items[]"  value="{key}"  />
  <label for="item-{key}">{item.name}</label>
</f:for>
Copied!

When you select a checkbox and submit the from, you will receive the error message.

Solution: Adding a counter/id in the brackets of the name attribute solves the problem:

<f:form.checkbox name="items[{key}]"  value="{key}"  />.
Copied!

Since in the form.checkbox documentation the examples are given with empty brackets, I consider this a bug.1

Better solution (since TYPO3 7): Do not add yourself [] to the name of the checkbox. Simply add multiple="1" and Fluid will adds automatically the [] to all the checkbox of the group.

<f:for each="{collection}" as="item" key="key">
  <f:form.checkbox name="items" multiple="1"  value="{key}"  />
  <label for="item-{key}">{item.name}</label>
</f:for>
Copied!

TYPO3 Exception 1255072833 

TYPO3 Exception 1255082824 

TYPO3 Exception 1255083671 

TYPO3 Exception 1255089361 

TYPO3 Exception 1256067130 

TYPO3 Exception 1256475113 

The argument "arguments" was registered with type "array", but is of type "string" in view helper 

This problem is related to the use of an extended Fluid syntax like this:

<a href="{be:moduleLink(route:'system_reports',arguments:{action:'detail', extension:extensionKey, report:reportName})}">
Copied!

In some versions of PHP, there is a PCRE bug with the underlying readline library: https://github.com/TYPO3/Fluid/commit/865890c3cffaf8d5f6aa44295d42a84a103895ec

A possible fix (for the example above) is to enclose the array arguments with single quotes like that:

<a href="{be:moduleLink(route:'system_reports',arguments:'{action:\'detail\', extension:extensionKey, report:reportName}')}">
Copied!

This effectively forces Fluid to extract the content of the single quotes with a simpler regular expression instead of a recursive one.

The argument does not follow the Fluid array syntax.

<f:render section="someSection" arguments="foo: {someVariable}" />
Copied!

Solution:

<f:render section="someSection" arguments="{foo: someVariable}" />

Copied!

Another possible cause of this error may be a PHP-configuration problem: PHP 7.3.14:

pcre.jit = 1
Copied!

jit (Just in time compiler) had to be enabled in my installation.

TYPO3 Exception 1256475114 

The argument "..." was registered with type "...", but is of type ... 

1256475114: The argument "newsItem" was registered with type "Tx_News_Domain_Model_News", but is of type "TYPO3CMSExtbasePersistenceGenericLazyObjectStorage" in view helper "Tx_News_ViewHelpers_LinkViewHelper". (More information)

TYPO3 Exception 1256661045 

TYPO3 Exception 1256730379 

TYPO3 Exception 1257146403 

Happened with invalid values for <switchableControllerActions>. Code looked like this:

<numIndex index="1" type="array">
    <numIndex index="0">My Data</numIndex>
    <numIndex index="1">Member->myInvestmentData;Member->show;Member->edit;Member-update;Investment->list;Investment->show;Investment->new;Investment->create;Investment->edit;Investment->update;Investment->delete</numIndex>
</numIndex>
Copied!

Notice the missing > for Member-update (should be Member->update). Have a look at FrontendConfigurationManager to see what values are expected.

TYPO3 Exception 1257246929 

Tried resolving a template file for controller action "..." in format ".html", ... 

Error message:

#1257246929: Tried resolving a template file for controller action "Page->render" in format ".html",
but none of the paths contained the expected template file ().
The following paths were checked: .../typo3conf/ext/fluidpages/Resources/Private/Templates/
Copied!

Source:

TYPO3Fluid\Fluid\View\Exception\InvalidTemplateResourceException thrown in file
.../typo3_src/vendor/typo3fluid/fluid/src/View/TemplatePaths.php in line 590.
Copied!

Problem: No page templates 

We had this error when no fluidpage templates were available and thus not selected in the backend.

Problem: Extension containing templates not installed 

We had this error when site package extension which contained templates was not installed, thus TYPO3 couldn't resolve EXT:extensionname/... paths.

Problem: sitepackage not added in resources 

We had this error because the sitepackage was not added on root -> edit page -> resources -> include pagetsconfig

Problem: TYPO3 9.5 Install Tool 

This error happens after an upgrade from TYPO3 8.7. Then the TYPO3 9.5 Install Tool is stuck in this error message. All the caches must be deleted. And the file index.php must be checked. This should be a link and not a php file. Activate the systemLogLevel' => 0, 'devIPmask' and 'displayErrors' => 1 in the file LocalConfiguration.php.

TYPO3 Exception 1257246930 

TYPO3 Exception 1257246931 

TYPO3 Exception 1257246932 

TYPO3 Exception 1259515600 

TYPO3 Exception 1259515601 

TYPO3 Exception 1259530751 

TYPO3 Exception 1259530791 

TYPO3 Exception 1259576985 

TYPO3 Exception 1259828920 

TYPO3 Exception 1259828921 

TYPO3 Exception 1260881688 

The error occurs if there is a newly created Domain Object where the attribute uid is not set. This happens because newly created Domain Objects were not persisted directly after adding them to a repository. You have to get an instance of the PersistenceManager:

$persistenceManager = $this->objectManager->get('TYPO3\\CMS\\Extbase\\Persistence\\Generic\\PersistenceManager')
Copied!

and persist it by hand with $persistenceManager->persistAll().

TYPO3 Exception 1263391473 

News 

Exception in news detail view:

#1263391473: The property "falMediaNonPreviews" on the subject was not accessible.
TYPO3\CMS\Extbase\Reflection\Exception\PropertyNotAccessibleException thrown in file /srv/www/typo3/typo3_src-6.2.3/typo3/sysext/extbase/Classes/Reflection/ObjectAccess.php in line 77.

TYPO3\CMS\Extbase\Reflection\ObjectAccess::getProperty(Tx_News_Domain_Model_NewsDefault, "falMediaNonPreviews")
Copied!

Solution:

Ensure that plugin.tx_news.features.rewrittenPropertyMapper is not set to 0.

Flux 

Error:

> The property "options.Fluidcontent.sorting" on the subject was not accessible.
Copied!

Reason:

> Form now supports sorting as a global option that can be used by any implementation; previously fluidcontent added its own but can now delegate this to Flux. This means that from now on you should define options="{sorting: 10}" instead of wrapping the sorting value in a scope like {Fluidcontent: {sorting: 10}}.
> https://github.com/FluidTYPO3/flux/blob/3840921670676f6ca5a8141bee640eeeb3865708/Documentation/Changelog/7.2.2.md
Copied!

Solution:

Update the extension.

TYPO3 Exception 1264022994 

TYPO3 Exception 1264023823 

TYPO3 Exception 1264023824 

TYPO3 Exception 1264023825 

TYPO3 Exception 1264093630 

This error can be caused by a misspelled vendor name.

The vendor name (first part of the namespaced class name) must start with a capital letter to work correctly with Extbase. Otherwise PHP class names start with a small letter while the Extbase types start with a capital letter what will cause problems.

Make sure the type of each variable is defined in your model: extensionname/Classes/Domain/Model/* Set the @var in the header

/**
* aString
*
* @var string
*/
protected $aString;
Copied!

TYPO3 Exception 1264093642 

Found an invalid element type declaration in %s 

1264093642: Found an invalid element type declaration in %s. Type
"ObjectStorage" must not have an element type hint
(vendor\yourExtension\Domain\Model\yourModel)
Copied!

Solution 

In annotations use statement do not work in older TYPO3 versions.

Use:

use TYPO3\CMS\Extbase\Persistence\ObjectStorage

// ...

/**
* @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\vendor\yourExtension\Domain\Model\yourModel
* ...
*/
Copied!

instead of

use TYPO3\CMS\Extbase\Persistence\ObjectStorage

// ...

/**
* @var ObjectStorage<\vendor\yourExtension\Domain\Model\yourModel>
* ...
*/
Copied!

Running Rector for TYPO3 v8 and below 

If you are running Rector on TYPO3 v8 and below you should exclude Domain/Model paths from TYPO3 Option Typo3Option::PATHS_FULL_QUALIFIED_NAMESPACES.

$parameters->set(Typo3Option::PATHS_FULL_QUALIFIED_NAMESPACES, [
    // If you are targeting TYPO3 Version 11 use can now use Short namespace
    // @see namespace https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ExtensionArchitecture/BestPractises/ConfigurationFiles.html
    'ext_localconf.php',
    'ext_tables.php',
    'ClassAliasMap.php',
    __DIR__ . '/**/Domain/Model/*',
    __DIR__ . '/**/Configuration/*.php',
    __DIR__ . '/**/Configuration/**/*.php',
]);
Copied!

TYPO3 Exception 1264678095 

The "in" operator must be given a multivalued operand 

Error-Message:

1264678095: The "in" operator must be given a multivalued operand (array, ArrayAccess, Traversable).

TYPO3 Exception 1265203124 

TYPO3 Exception 1265367590 

TYPO3 Exception 1267700868 

TYPO3 Exception 1267700870 

TYPO3 Exception 1267832524 

TYPO3 Exception 1268056288 

TYPO3 Exception 1268056289 

TYPO3 Exception 1268734872 

TYPO3 Exception 1268817963 

TYPO3 Exception 1269877402 

TYPO3 Exception 1269878881 

TYPO3 Exception 1269881658 

TYPO3 Exception 1269881659 

TYPO3 Exception 1270853878 

TYPO3 Fatal Error: Extension key "..." is NOT loaded! 

#1270853878: TYPO3 Fatal Error: Extension key "adodb" is NOT loaded!
Copied!

Please check, whether you have downloaded and installed the called extension (in this case "adodb") in the backend extension manager.

Additionally, clearing the complete Cache via the admin tool can help solve the problem.

In general the error can be thrown if a dependency is not met (means: a required extension is missing).

Non-supported versions 

If the extension is only for BE and depends on another extension such as scheduler, one has to set in the ext_localconf.php of that extension the variable doNotLoadInFE to 1.

TYPO3 Exception 1270853879 

TYPO3 Fatal Error: Extension key "..." is NOT loaded! 

This error appears in TYPO3 6+ when you uninstall or manually delete a required extension. Clear all caches and reinstall the necessary extension.

TYPO3 Exception 1270853880 

TYPO3 Exception 1270853881 

TYPO3 Exception 1270853882 

TYPO3 Fatal Error: No database selected! 

typo3conf/LocalConfiguration.php misses the database configuration.

If you've just updated from a version below TYPO3 8.7 , you are most probably missing new configuration in your AdditionalConfiguration.php file. Since TYPO3 8.7 the structure of the db connection configuration has changed.

Something like that will work in AdditionalConfiguration.php:

$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['dbname'] = 'dbname';
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['host'] = '127.0.0.1';
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['user'] = 'username';
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['password'] = 'passwordtodb';
Copied!

Read more here:

https://docs.typo3.org/typo3cms/CoreApiReference/8.7/ApiOverview/Database/Configuration/Index.html

TYPO3 Exception 1270853883 

TYPO3 Exception 1270853884 

The current username, password or host was not accepted ... 

TYPO3 Fatal Error: The current username, password or host
was not accepted when the connection to the database was
attempted to be established!
Copied!

Correct the database settings 

Check your LocalConfiguration.php or AdditionalConfiguration.php files and verify that the database connection settings are correct.

Restart the MySQL daemon. 

  1. Login as root on your system if you have shell access, or start a console from the server panel.
  2. type: /etc/init.d/mysql restart On Mac OSX 10.10 (Yosemite) type: sudo /usr/local/mysql/support-files/mysql.server stop
  3. If you get this error:

    ERROR! The server quit without updating PID file (/usr/local/mysql/data/<SERVERNAME>.pid)
    
    Copied!

    Then your next option is to kill the mysql process manually by following this instructions: http://stackoverflow.com/questions/26263889/starting-mysql-error-the-server-quit-without-updating-pid-file/26266079#26266079

  4. Then restart mysql daemon again. This time it should work. On Mac OSX 10.10 (Yosemite) type: sudo /usr/local/mysql/support-files/mysql.server start

TYPO3 6.2 - modify your MySQL configuration file 

The problem could depend on recent PHP update from v. 5.3/5.4 to 5.5; a new module is installed: php-mysqlnd. So your TYPO3 attempt to establish a db connect but mysql do not use more your old encryption method for the password.

Proceed as follows:

  1. edit /etc/my.cnf
  2. remove the old_passwords=1 statement
  3. login as root in your server
  4. login to mysql as admin/root (mysql -u root -p)
  5. select database, type: use mysql;
  6. just switched to mysql db change the password of the user:

    update mysql.user set password=PASSWORD('password') where user='db-username'
    
    Copied!

    obviously substitute db-username with the 'username' and 'password' with the right (old or new password) used to access your db, stored in: typo3conf/LocalConfiguration.php

  7. restart your mysql daemon: /etc/init.d/mysqld restart
  8. eventually remove all site cache: rm -rif typo3temp/Cache*

TYPO3 Exception 1270853885 

TYPO3 Exception 1270853886 

TYPO3 Exception 1270853887 

TYPO3 Exception 1270853900 

TYPO3 Exception 1270853903 

TYPO3 Exception 1270853910 

TYPO3 Exception 1270853912 

TYPO3 Exception 1270853920 

TYPO3 Exception 1270853921 

TYPO3 Exception 1270853922 

TYPO3 Exception 1270853930 

TYPO3 Exception 1270853931 

TYPO3 Exception 1270853950 

TYPO3 Exception 1270853952 

TYPO3 Exception 1270853953 

TYPO3 Exception 1270853954 

TYPO3 Exception 1270853961 

TYPO3 Exception 1270853980 

TYPO3 Exception 1270853981 

TYPO3 Exception 1270853982 

TYPO3 Exception 1270853983 

TYPO3 Exception 1270853984 

TYPO3 Exception 1271492606 

TYPO3 Exception 1271492607 

TYPO3 Exception 1273753083 

Cannot cast object of type "..." to string. 

The error message basically means that you are trying to directly render an object that has no __toString() method. Check your templates.

For example: Instead of just using {myObject.myDateProperty}, wrap it with f:format.date: {myObject.myDateProperty -> f:format.date(format: 'd.m.Y')}. See https://forge.typo3.org/issues/38294

TYPO3 Exception 1274563549 

TYPO3 Exception 1274799932 

TYPO3 Exception 1274799934 

An object of class "..." could not be converted to a plain value. 

TYPO3 Exception 1275830266 

TYPO3 Exception 1277367645 

TYPO3 Exception 1277367648 

TYPO3 Exception 1278155986 

TYPO3 Exception 1278155987 

The path provided does not point to existing and accessible well-formed XML file. 

Check the XML file mentioned for formatting errors (for example with an XML Validator). Occurs when a tag name is not well closed (example: <label></labe>).

This error might also occur if the file has the wrong encoding. Try to use UTF-8 (without BOM). If the file is a language file, also check all other language versions. For example, if the error is shown for locallang_db.xlf, in fact, the error might be caused by de.locallang_db.xlf.

TYPO3 Exception 1278155988 

Broken character in locallang files 

This exception happens if you have invalid characters in a locallang.xlf file.

_Example_

Bad:

<trans-unit>
   <source>Bootstrap Package: Left & normal, 2 Columns</source>
</trans-unit>
Copied!

Good:

Wrap with CDATA to escape special characters.

<trans-unit>
   <source><![CDATA[Bootstrap Package: Left & normal, 2 Columns]]></source>
</trans-unit>
Copied!

TYPO3 Exception 1278450972 

#1278450972: Class ... does not exist. Reflection failed. TYPO3 9.5 

We had a whitespace at the beginning of the filename of the file containing the class.

When switching over from working with TYPO3 v10+ back to TYPO3 v9.5, remember that you have to specify the fully qualified name for parameters, as opposed to TYPO3 v10+ where you can import the class name.

#1278450972: Class ... does not exist. Reflection failed. After updating to TYPO3 11 

We missed the required update in the registration of plugins and modules to use the full class name.

See Breaking: #92609 - Use controller classes when registering plugins/modules.

#1278450972: Class ... does not exist. Reflection failed. in TYPO3 11 

Running composer update fixes the problem in a Composer based installation of TYPO3.

#1278450972: The classname "..." was not found and thus can not be reflected. 

This (extbase) error can occur if you have annotated a (controller action) method using @param but have not given it a type hint. If the annotation is wrong this error will occur.

Example:

/**
 * A test action
 *
 * @param \MyVendor\MyExtension\Domain\Motel\InvalidName $myVariable
 */
public function testAction($myVariable) {
Copied!

As you see the @param annotation is wrong. Because you usually have not any Domain\Motel namespace and there is no type hint for $myVariable in the function header.

So either correct the annotation, clear all caches:

/**
 * A test action
 *
 * @param \MyVendor\MyExtension\Domain\Model\ValidName $myVariable
 */
public function testAction($myVariable) {
Copied!

Or try to add a type hint:

/**
 * A test action
 *
 * @param \MyVendor\MyExtension\Domain\Model\ValidName $myVariable
 */
public function testAction(\MyVendor\MyExtension\Domain\Model\ValidName $myVariable) {
Copied!

I had a Composer based Installation. And i have to add my ext. to the psr4 autoload in copmposer.json:

"autoload": {
     "psr-4": {
             "MyVendor\\MyExtension\\":"web/typo3conf/ext/MyExtension/Classes"
     }
 },
Copied!

#1278450972 TYPO3CMSExtbaseReflectionExceptionUnknownClassException 

Class Boolean does not exist. Reflection failed.

at TYPO3\CMS\Extbase\Reflection\ReflectionService->buildClassSchema('Vendorname\\Extensionname\\Domain\\Model\\MyModel')
Copied!

Got this error because in MyModel was a setter with a wrong typehint, in my case it was something like

public function setFreeShipping(\Boolean $freeShipping)
Copied!

Solution was to change \\Boolean to bool.

TYPO3 Exception 1279212461 

TYPO3 Exception 1279462933 

TYPO3 Exception 1279469941 

TYPO3 Exception 1279470252 

TYPO3 Exception 1279470253 

TYPO3 Exception 1279470254 

TYPO3 Exception 1279470255 

TYPO3 Exception 1279487573 

TYPO3 Exception 1279488008 

TYPO3 Exception 1279569759 

TYPO3 Exception 1279578078 

TYPO3 Exception 1279719168 

TYPO3 Exception 1279763057 

TYPO3 Exception 1279763534 

TYPO3 Exception 1279765134 

TYPO3 Exception 1279765144 

TYPO3 Exception 1279808078 

TYPO3 Exception 1279962349 

TYPO3 Exception 1280773643 

TYPO3 Exception 1280825466 

TYPO3 Exception 1281646455 

TYPO3 Exception 1281859196 

TYPO3 Exception 1281868686 

TYPO3 Exception 1281868687 

TYPO3 Exception 1281875340 

TYPO3 Exception 1281962564 

TYPO3 Exception 1282073032 

TYPO3 Exception 1282073033 

TYPO3 Exception 1282073034 

TYPO3 Exception 1282073035 

TYPO3 Exception 1282073036 

TYPO3 Exception 1282073037 

TYPO3 Exception 1282348825 

TYPO3 Exception 1282489834 

TYPO3 Exception 1283790586 

There is no entry in the $TCA array for the table "your_unknown_table" 

Exception 1283790586 'There is no entry in the $TCA array for the table "your_unknown_table". This means that the function enableFields() is called with an invalid table name as argument.'

This exception is thrown in TYPO3\CMS\Frontend\Page\PageRepository::enableFields when the table (as mentioned in the error) is not found in the TCA.

Possible causes 

Your project uses:

  • PHP-code with enableFields('your_unknown_table').
  • TypoScript-code with an unknown table in a CONTENT-object. There might be an indication of this in the backtrace, f.e. TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::cObjGetSingle("CONTENT", array, "30") indicates that an unknown table is used in a CONTENT element with the name '30'.
  • Backtrace is the detailed error output when dev mode is enabled in the install tool. I searched it for "array" and found this: TypoScript Code TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::cObjGetSingle("TEMPLATE", array, "100"). Now I searched my templates for the string "100". It was the main page template, and I found some temp. objects that were defined as temp.myobject = CONTENT, but due to some conditions, in some cases, had no further definition. TYPO3 4.5 could live with that, 6.2 threw an error.

Bad:

temp.item = CONTENT
[globalVar = LIT:1 = {$constant}]
temp.item {
}
[global]
Copied!

Less bad:

temp.item =
[globalVar = LIT:1 = {$constant}]
temp.item =CONTENT
temp.item {
}
[global]
Copied!

TYPO3 Exception 1284401632 

TYPO3 Exception 1284793775 

No widget context was found for the Ajax Widget Identifier "..." 

TYPO3 Exception 1284906026 

Language and character encoding are not set. 

Error is thrown by the page renderer if language or charset configuration are missing. Please check your page renderer usage.

TYPO3 Exception 1284986120 

TYPO3 Exception 1284986604 

TYPO3 Exception 1285022360 

TYPO3 Exception 1285067843 

A back-end form protection may only be instantiated if there is an active back-end session. 

\TYPO3\CMS\Core\FormProtection\BackendFormProtection may only be used with a backend user that is logged in.

TYPO3 Exception 1285352962 

TYPO3 Exception 1285353026 

TYPO3 Exception 1287059709 

TYPO3 Exception 1288085266 

Possible Reasons for this Exception 

  • You've created a Template using css_styled_content methods, but haven't included it inside your template
  • You've created a FLUID Template and forgot to include a template file (see example below)
  • You've installed an extension that has a Static Include and you forgot to add the Static Include (from extension)

Example 

page.10 = FLUIDTEMPLATE
page.10 {
  # this line is important!
  file = fileadmin/templates/file.html
  # Set the Template Pathes
  partialRootPath = fileadmin/templates/partials/
  layoutRootPath = fileadmin/templates/layouts/
  variables {
    # Assign the main column with our {content}-destination
    content < styles.content.get
    content.select.where = colPos = 1
  }
}
Copied!

TYPO3 Exception 1288087061 

Template could not be found at "..." 

In the example below, the error is: Template could not be found at "fileadmin/templates/RS1.html".

To fix this error, correct the path of the included file.

page.10.file.stdWrap.cObject = CASE
page.10.file.stdWrap.cObject {
    key.data = levelfield:-1, backend_layout_next_level, slide
    key.override.field = backend_layout

    default = TEXT
    default.value = fileadmin/templates/RS1.html
}
Copied!

TYPO3 Exception 1288091419 

TYPO3 Exception 1288092521 

TYPO3 Exception 1288092555 

Could not load file layout. Tried Following paths: "..." 

Check whether the correct layout file is referenced. A common mistake is to use lowercase instead of uppercase for the first letter.

TYPO3 Exception 1288092556 

TYPO3 Exception 1288094511 

TYPO3 Exception 1288094648 

TYPO3 Exception 1288095720 

TYPO3 Exception 1288215888 

TYPO3 Exception 1288215889 

TYPO3 Exception 1288215890 

TYPO3 Exception 1288215891 

TYPO3 Exception 1288215892 

TYPO3 Exception 1288418476 

TYPO3 Exception 1288965219 

Error: $className must be a non empty string. 

Error has occurred on calling findAll(). The mistake was, that one property in the model missed the type in the @var annotation.

TYPO3 Exception 1288967479 

TYPO3 Exception 1288967686 

TYPO3 Exception 1288969325 

TYPO3 Exception 1289318609 

TYPO3 Exception 1289342187 

TYPO3 Exception 1289386765 

Could not analyse class: "..." maybe not loaded or no autoloader? 

Message:

Oops, an error occurred!

Could not analyse class: Vendor\Extension\Controller\SomeController maybe not loaded or no autoloader?

More information regarding this error might be available online.
Copied!

General 

  • The class cache in TYPO3 7.6 does not get cleared when pressing the "Clear System Cache" button, so you have to empty typo3temp/* yourself to get around this issue:
$ rm -rf typo3temp/*
Copied!
  • The errorHandler turns E_STRICT into exceptions. This can break the autoloading in some TYPO3 versions (ie. 6.2.30). Excluding E_STRICT errors can help.

If you got the error while migrating your extension to use namespaces 

If you're migrating to namespaces, you need to put the vendor name inside your *ext_localconf.php* and your **ext_tables.php**, otherwise extbase tries to look up names in the old fashioned way.

ext_localconf.php

// Wrong
TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    $_EXTKEY,
    'Plugin',
    array('Controller' => 'action')
);

// Correct in older TYPO3 versions:
TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'MyVendorName.' . $_EXTKEY,
    'Plugin',
    array('Controller' => 'action')
);

// Correct in newer TYPO3 versions:
TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'MyExtension',
    'Plugin',
    [\MyVendor\MyExtensionName\Controlle\MyPluginController::class => 'action']
);
Copied!

ext_tables.php

// Wrong
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
    $_EXTKEY,
    'Plugin',
    'PluginTitle',
);;

// Right
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::registerPlugin(
    'MyVendorName.' . $_EXTKEY,
    'Plugin',
    'PluginTitle',
);
Copied!

More here: Extbase Reference

Error message concerning Fluid View Helper 

#1289386765: Could not analyse class:TYPO3\CMS\Fluid\ViewHelpers\Form\TextViewHelper maybe

not loaded or no autoloader?
Copied!

solutions 

  • it could be, that you have misspelled the name of the viewhelper, for example
"<f:form.textbox ..." instead of   "<f:form.textfield ..."
Copied!
  • to be more specific for the requested extension blog_example, change all occurrences in templates under

typo3conf/ext/blog_example/Resources/Private/Backend/Layouts/Templates e.g.: Templates/Blog/New.html Line 14

<f:form.textbox property ="title" />
Copied!

to

<f:form.textfield property ="title" />
Copied!
  • also check if the extension itself is loaded
  • The RenderFlashMessagesViewHelper was deprecated for a long time and finally removed in 6.0.

So, please use FlashMessagesViewHelper instead:

<f:renderFlashMessages/>
Copied!

becomes

<f:flashMessages/>
Copied!
  • You must also check the Fluid template for upper and lower case writing. For example f:link.typoLink... will throw an exception because the class cannot be found. But this will occur only on case-sensitive file systems. Solution: change f:link.typoLink to f:link.typolink

error message concerning DamViewHelper (from ext:news) 

I got this error while updating ext:news from 2.3.1 to 3.0.1 after an TYPO3 upgrade from 6.1.12 to 6.2.6

#1289386765: Could not analyse class:Tx_News_ViewHelpers_Format_DamViewHelper maybe not loaded or no autoloader?

Copied!

Solution 

so the viewhelper format.dam got removed news 3.0.1 has other HTML-templates than 2.3.1 as the copied and individualized templates stayed through the upgrade calls to the old viewhelper stay in place and throw an error with the new version. Solution: clean up your copied templates

Error in own extension 

If you got the error using your own extension: Maybe your extension name uses underscores. If your extension is named my_extension:

//wrong
/**
 * Misc Functions
*
* @var \Myvendor\Myextension\Utility\Div
* @inject
*/
protected $div;

//right
/**
 * Misc Functions
*
* @var \Myvendor\MyExtension\Utility\Div
* @inject
*/
protected $div;
Copied!

In your own extension: If you add the namespace after the extension had already been installed, intensive clearing of caches is needed. May even be needed to empty typo3temp.

If you got the error while in composer mode 

And you are adding your own extension or added some extension without composer. Then you must either load the extension with composer or handle the class loading with your composer.json:

{
  "name": "my-vendor/my-typo3-cms-distribution",
  "require": {
    "typo3/cms": "7.x-dev"
  },
  "autoload": {
    "psr-4": {
      "MyVendor\\MySitePackage\\": "typo3conf/ext/my_site_package/Classes"
    }
  }
}
Copied!

Note if your installation "web-dir" in composer.json is "Web":

...
"psr-4": {
      "MyVendor\\MySitePackage\\": "Web/typo3conf/ext/my_site_package/Classes"
}
...

Copied!

If you got the error while updating from TYPO3 4.x to 6.2 

Then your migration process was broken. For me it helped to redo it entirely and uninstall "extension news" completely (without deleting files) and updating it after the upgrade. The error message provided here doesn't tell you where exactly the issue occurs because you only see the result of a problem at a very later stage that some classes could not be loaded. The root cause is a broken autoload-process that unfortunately doesn't create any errors.

If you got the error while adding a new namespace in TYPO3 7.4.0 or 7.5.0 

Adding a new file with namespace in v7.4.0 or v7.5.0 can trigger this error. In my case it happens to be a weird caching issue. Actually hitting the "Clear cache" button in the install tool should solve that, but somehow that alone won't work.

Solution 

- Go to the Extension Manager and uninstall your extension
- Go to the Install Tool and hit the 'Clear cache' button. On the same page hit the 'Clear PHP opcode cache' button
- Go back to the Extension Manager and reinstall your extension
Copied!

If you got the error while updating FluidTYPO3 

If you upgrade old versions of flux/fluidpages and get this error, then you'll need to switch to proper namespaces (legacy namespaces got removed in version 7.2.0, see Changelog → https://github.com/FluidTYPO3/flux/blob/7.2.0/CHANGELOG.md)

Examples:

  • In PHP Code Tx_Fluidpages_Controller_PageController to \FluidTYPO3\Fluidpages\Controller\PageController
  • In ViewHelpers {namespace v=Tx_Vhs_ViewHelpers} to {namespace v=FluidTYPO3\Vhs\ViewHelpers}
  • In TypoScript (if not loaded automatically)
5 = USER
5.userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
5.extensionName = Fluidpages
### the following line is new and required:
5.vendorName = FluidTYPO3
5.pluginName = Page
Copied!

If you got the error with EXT:fluidcontent_bootstrap 

Could not analyse class:Tx_Vhs_ViewHelpers_Extension_Path_ResourcesViewHelper maybe not loaded or no autoloader?

The extension throws this error after updating https://extensions.typo3.org/extension/vhs/ to v2.4.0 (which is the last version to work with TYPO3 6.2). The extension fluidcontent_bootstrap itself isn't 7.6 compatible. So either replace it or fix the problematic places and set the extension to excludeFromUpdates.

  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Accordion.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Alert.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/ButtonGroup.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/ButtonLink.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Carousel.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Jumbotron.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/NavigationList.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/PageHeader.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Row.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Tabs.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Thumbnails.html
  • fluidcontent_bootstrap/Resources/Private/Templates/Content/Well.html

A more elegant way could be to change the template path to fileadmin and copy the resources (and alter only these files).

If you got the error with Flux 

Error:

Could not analyse class: "FluidTYPO3\Flux\ViewHelpers\Widget\GridViewHelper" maybe not loaded or no autoloader? Class FluidTYPO3\Flux\ViewHelpers\Widget\GridViewHelper does not exist
Copied!

Reason:

> https://github.com/FluidTYPO3/flux/commit/3b65374429f579a39ece2d23568abb12ae110b29
> DEPRECATED
> - * Grid Widget for rendering a grid in previews of BE elements
> New behaviour:
> Renders a Grid as content element container in the page module if your template defines one, regardless of whether or not you have a Preview section (https://fluidtypo3.org/blog/news/coming-changes-in-flux-72.html)
Copied!

Fix:

Just remove <flux:widget.grid /> completely.

if you got this error while updating via git 

  • If you update your installation via git it is possible that Class caches are not up to date
  • The caches will not be cleared in BE neither in install tool
  • To clear the caches uninstall and re-install the extension
  • Alternatively use terminal: typo3/cli_dispatch.phpsh extbase extension:dumpclassloadinginformation

TYPO3 Exception 1289386945 

TYPO3 Exception 1289391048 

TYPO3 Exception 1289422564 

TYPO3 Exception 1289679153 

The specified compression of type "" but a boolean is expected. 

The error happens when your cache configuration is invalid. Check typo3conf/LocalConfiguration.php and typo3conf/AdditionalConfiguration.php looking for something like:

'pages' => [
    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\RedisBackend',
    'options' => [
        'compression' => 1,
    ],
],
Copied!

and change it to

'pages' => [
    'backend' => 'TYPO3\\CMS\\Core\\Cache\\Backend\\RedisBackend',
    'options' => [
        'compression' => true,
    ],
],
Copied!

TYPO3 Exception 1289679154 

TYPO3 Exception 1289679155 

TYPO3 Exception 1289843275 

TYPO3 Exception 1289843277 

TYPO3 Exception 1289852422 

TYPO3 Exception 1289858856 

TYPO3 Exception 1289917924 

You don't have access to this page 

typo3/sysext/extbase/Classes/Core/Bootstrap.php

This error can occur, when the current page is deleted and the user selects a module in the web menu. It has also been logged in the TYPO3 issue tracker: Issue 66449

Another reason might be permission problems: For example, if access to a page is restricted by permissions or the current user does not have permissions to access any page in the page tree.

TYPO3 Exception 1289918325 

#1289918325: Module 'my_module' is not configured. 

This message appears when trying to load a module from BE context menu. The module was configured in Route.php and loaded via BackendControllerHook.

This problem appears when changing a module name or when old module names are still cached (for example when upgrading the TYPO3 core or extensions).

The solution is to clear all caches (either via the install tool or if that does not help via manually removing the files in typo3temp).

TYPO3 Exception 1290167704 

TYPO3 Exception 1290628113 

TYPO3 Exception 1290697924 

TYPO3 Exception 1290944650 

TYPO3 Exception 1291064151 

Could not write to file "typo3temp/mail.mbox" when sending an email to debug transport 

The filepath given in [MAIL][transport_mbox_file] needs to be absolute and writeable.

In the example above is was enough to use /var/www/typo3temp/mail.mbox as path.

TYPO3 Exception 1291068569 

TYPO3 Exception 1291068606 

TYPO3 Exception 1291068620 

TYPO3 Exception 1291083486 

TYPO3 Exception 1291109987 

TYPO3 Exception 1291163589 

TYPO3 Exception 1291227373 

TYPO3 Exception 1291234985 

TYPO3 Exception 1291234986 

TYPO3 Exception 1291234987 

TYPO3 Exception 1291237145 

TYPO3 Exception 1291237668 

TYPO3 Exception 1291242168 

TYPO3 Exception 1291414955 

TYPO3 Exception 1291414956 

TYPO3 Exception 1291414957 

TYPO3 Exception 1291414958 

TYPO3 Exception 1291414959 

TYPO3 Exception 1291422012 

TYPO3 Exception 1291429389 

TYPO3 Exception 1291470084 

TYPO3 Exception 1291470170 

TYPO3 Exception 1291494126 

TYPO3 Exception 1291501280 

TYPO3 Exception 1292857934 

TYPO3 Exception 1292858051 

TYPO3 Exception 1293617736 

TYPO3 Exception 1293617741 

TYPO3 Exception 1294062286 

TYPO3 Exception 1294430950 

TYPO3 Exception 1294430951 

TYPO3 Exception 1294585070 

No module "tools_txreportsM1" could be found. 

Please try clearing all caches via the install tool.

TYPO3 Exception 1294585190 

TYPO3 Exception 1294585191 

TYPO3 Exception 1294585192 

ADMCMD command could not be executed 

See also: https://forge.typo3.org/issues/18761

Happens in TYPO3 versions below 9 when the client side preview cookie expires. Removing the cookie ADMCMD_prev solves the problem.

TYPO3 Exception 1294585193 

TYPO3 Exception 1294585194 

TYPO3 Exception 1294585195 

TYPO3 Exception 1294585196 

TYPO3 Exception 1294585200 

TYPO3 Exception 1294585668 

TYPO3 Exception 1294585669 

TYPO3 Exception 1294585670 

TYPO3 Exception 1294585788 

TYPO3 Exception 1294585860 

TYPO3 is in maintenance mode 

Non-admins get this message when trying to login to a TYPO3 installation in maintenance mode.

To disable this behaviour, login as an admin and set [BE][adminOnly] = 0 in the Install Tool.

TYPO3 Exception 1294585861 

TYPO3 Exception 1294585862 

TYPO3 Exception 1294585865 

TYPO3 Exception 1294585866 

No class named "..." 

Check your source code for occurrences of that class name. Usually happens if a hook is registered with a wrong class name/reference.

Possible solution:

Legacy installation:

  • Try to use the Admin Tools > Maintenance backend module: Rebuild PHP Autoload Information

Composer-based installation:

  • composer dump-autoload

TYPO3 Exception 1294585867 

TYPO3 Exception 1294586096 

TYPO3 Exception 1294586097 

TYPO3 Exception 1294586098 

Lock file could not be created 

This may happen because

  • disk is full
  • the deprecation log or other log files are unusually large
  • the location for lock files is read-only

To solve this error, make sure enough disk space is available and the location for lock files is writable by the server. If the deprecation log is the problem, disable the deprecation log temporarily until you have fixed the errors.

TYPO3 Exception 1294586099 

TYPO3 Exception 1294586100 

TYPO3 Exception 1294586333 

TYPO3 Exception 1294586383 

TYPO3 Exception 1294586441 

Oops, an error occurred! "..." is not writable. 

This happens when your file permissions (Unix) are not correct while including TypoScript from a file and trying to edit it in the backend.

Solution: Change file permissions to make the file writeable by the webserver, for example chgrp www-data your/error/message/file && chmod g+w www-data or move the TypoScript to a location that can be written.

TYPO3 Exception 1294586442 

Template is not writeable 

Happens when your file permissions (Unix) are not correct if you include TypoScript from a file and try to edit it in the backend.

Solution: Change file permissions to make the file writeable by the webserver or move the file to a writable location. For example, if you need to make changes on TypoScript of an extension you should not do it in the extension directly but in your own template files.

TYPO3 Exception 1294586443 

TYPO3 Exception 1294586444 

TYPO3 Exception 1294586445 

TYPO3 Exception 1294586446 

Fatal Error: This module "..." is not enabled in TBE_MODULES 

Happens when a module cannot be found in the global module array for example after installing or updating an extension.

Possible solutions:

  • Clear all caches
  • Reload the whole Page (not only the ContentFrame)

TYPO3 Exception 1294586447 

TYPO3 Exception 1294586448 

You don't have access to this module. 

When an editor (a backend user that is not an administrator) tries to access a module to where they have no access to an exception like this will be thrown:

Core: Exception handler (WEB):
Uncaught TYPO3 Exception: #1294586448: Access Error: You don't have access to this module.
RuntimeException thrown in file /var/www/html/vendor/typo3/cms/typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php in line 448.
Copied!

In the media extension this happens for example if the access to the modules is not configured properly.

Check the following access: A backend user with access to File>Media must also granted to User tools > Media Extra (hidden module, required for non admin).

|Media Extra Module in Access List for Backend usergroup.png|

TYPO3 Exception 1294586450 

TYPO3 Exception 1294586451 

TYPO3 Exception 1294586643 

TYPO3 Exception 1294586645 

TYPO3 Exception 1294586646 

TYPO3 Exception 1294586647 

TYPO3 Exception 1294586840 

TYPO3 Exception 1294586841 

TYPO3 Exception 1294586842 

TYPO3 Exception 1294586843 

TYPO3 Exception 1294586844 

TYPO3 Exception 1294586845 

TYPO3 Exception 1294586846 

TYPO3 Exception 1294586847 

TYPO3 Exception 1294586848 

TYPO3 Exception 1294587021 

TYPO3 Exception 1294587022 

TYPO3 Exception 1294587023 

Your browser version looks incompatible with this TYPO3 version! 

You are using a browser that is not supported by TYPO3. Please use a supported browser (for example Firefox or Chrome in an up-to-date version).

TYPO3 Exception 1294587124 

TYPO3 Exception 1294587125 

TYPO3 Exception 1294587207 

TYPO3 Exception 1294587210 

TYPO3 Exception 1294587211 

TYPO3 Exception 1294587212 

TYPO3 Exception 1294587214 

TYPO3 Exception 1294587215 

RealURL-Error "ID was outside the domain" 

You have to set your root page id inside your realurl_conf file: $TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT']['pagePath']['rootpage_id'] = 1;

or if using multiple domains in tree: $TYPO3_CONF_VARS['EXTCONF']['realurl']['www.website.org']['pagePath']['rootpage_id'] = 25;

TYPO3 Exception 1294587217 

The page is not configured! [type=x][]. 

No PAGE object defined for type=x 

This happens if you forget the line

page = PAGE
Copied!

(for typeNum = x from the error message, with 0 being the default)

in the Setup field of your TypoScript record.

When you see this error, a TypoScript template is already there. In the backend go to the page with that TypoScript template. Most probably it is on the root page of your website; that is the one directly below the very first page, below the one with the TYPO3 logo next to it. Use the "Template" module to have a look at the template located at that page.

Use the Template module to modify that template: Select the "Info/Modify" screen from the drop-down box at the top. Then click on the pencil icon next to the word "Setup" and replace what you have in the Setup field with the following lines:

# Default PAGE object:
page = PAGE
# Define output for typeNum=0, the default type.
page.typeNum = 0
page.10 = TEXT
page.10.value = HELLO WORLD!
Copied!

Save the template and open the page in the frontend. You should see the words "HELLO WORLD!".

Another possibility is that you are trying to access a page with an undefined page type. E.g. https://example.org/?type=123, but you do not have a (page).typeNum = 123 defined in your TypoScript template.

Using broken TypoScript 

#. Default PAGE object:
page = PAGE page. 10 = TEXT page. 10.value = HELLO WORLD!
Copied!

Removing the spaces and adding line breaks leads to a page running fine without the error.

Using Bootstrap_package 

You forgot to include the bootstrap_package static template.

TYPO3 Exception 1294587218 

ServiceUnavailable: TypoScriptFrontendController 

TypoScript is the language, in which the internal object structure in TYPO3 CMS is described (not the HTML DOM). Each page needs at least one TypoScript template either in its own properties or in an upward page.

So you need at least one page and a "root level" template record with some content.

If you have both, go through the following:

First, check wether the page you don't see or at least one of the pages in root-direction has a TypoScript template which works, is active and has root-level property. To achieve this, go to the following window:

Template Module in the left column > page is selected in middle column > info/edit in top selection field > edit complete template record > "General" - tab

  • check the template TypoScript code in the "Setup" - text field
  • The "inactive" field must be unchecked.
  • Check, whether root-level property is set in the "Options" tab: the "root level" field must be checked.

If all this is o.k., but the error occurs nonetheless, you may delete and re-create the root template.

Delete the root template with the little trash bin on top of template edit page.

Then create a new template by clicking "Create template for new website". This button has appeared after deleting the root template.

Additionally, you find many information in the docs on TYPO3.org

SOLUTION 1 (Tested with TYPO3 7+) 

  1. In the backend, click on 'Template' menu under web module.
  2. Click on the main page (usually id 1)
  3. Select Info/Modify in the dropdown menu on the header section of the content pane.
  4. Click on the Edit the whole template record button.
  5. Click on the Options tab.
  6. Make sure to select Rootlevel checkbox. Problem solved.

TYPO3 Exception 1294587219 

TYPO3 Exception 1294587482 

This exception occurs when TYPO3 misses any mandatory PHP modules (i.e. gd, mysql, openssl, fileinfo).

To fix this modify your php.ini file and activate the proper extension(s) there.

TYPO3 Exception 1294587483 

TYPO3 Exception 1294587484 

TYPO3 Exception 1294587485 

TYPO3 Exception 1294587486 

TYPO3 9.5.23 and the extension phpmyadmin 5.6.4 result in error message

Session already started by session_start(). Make sure no installed extension is starting a session in its :file:`ext_localconf.php` or :file:`ext_tables.php`.
Copied!

when logging in to Admin Tools (Maintenance, Settings, Update, Environment) in Backend.

Solution: uninstall phpmyadmin, delete cookies, re-login

TYPO3 Exception 1294587487 

TYPO3 Exception 1294587694 

TYPO3 Exception 1294587706 

TYPO3 Exception 1294681466 

TYPO3 Exception 1294681467 

This error shows up if email addresses could not be validated successfully. Correct format would be something like My Group: "Richard" <richard@localhost> (A comment), ted@example.com (Ted Bloggs), Barney;

Not all components are required but if there is a name, it must be wrapped in some way. See this RFC for details: http://www.ietf.org/rfc/rfc822.txt

TYPO3 Exception 1295012802 

TYPO3 Exception 1295193026 

TYPO3 Exception 1295476760 

TYPO3 Exception 1295476808 

TYPO3 Exception 1295476821 

TYPO3 Exception 1295476972 

TYPO3 Exception 1295476989 

TYPO3 Exception 1295479650 

TYPO3 Exception 1295479651 

The default action can not be determined for controller "Foo" 

#1295479651: The default action can not be determined for controller "Foo". Please check TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.

This may happen if the third parameter to \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() is wrong.

Invalid:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'Ext',
    'Foo',
    [FooController::class => ['show']],
    []
);
Copied!

Valid:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'Ext',
    'Foo',
    [FooController::class => 'show'],
    []
);
Copied!

TYPO3 Exception 1295611406 

Cyclic dependency in prototype object, for class "..." 

Happens if the extbase dependency injection is unable to resolve the dependencies as a dependency cycle has been detected (A requires B which requires A).

TYPO3 Exception 1295705938 

TYPO3 Exception 1296062830 

TYPO3 Exception 1296062831 

TYPO3 Exception 1296062832 

TYPO3 Exception 1296805368 

TYPO3 Exception 1297645190 

TYPO3 Exception 1297759968 

When using Extbase FileUpload, TYPO3 13.4.17 

The import for the PHP Attribute was missing

packages/MyExtension/Classes/Domain/Model/MyModel.php
+use TYPO3\CMS\Extbase\Annotation\FileUpload;

 #[FileUpload([
     'validation' => [
         'minFiles' => 0,
         'maxFiles' => 1,
         'mimeType' => ['allowedMimeTypes' => ['application/pdf']],
     ],
     'uploadFolder' => '2:/documents/',
 ])]
 protected ?FileReference $documents = null;
Copied!

Adding the proper import to properly utilize the attribute will then also properly allow introspection of the PropertyMapper later on.

Exception while property mapping at property path "":Object with identity "1" not found. 

This error is thrown when a link to a hidden record is called.

Exception while property mapping at property path "":Method::__construct() does not exist 

The ReflectionService tries to get the constructor arguments of your model class, which in this case seem not to exist.

As a work around you can put an empty __construct method in your model class

/**
 *
 */
public function __construct() {
}
Copied!

Exception while property mapping at property path "":Could not find a suitable type converter for "array|null" because no such class or interface exists 

See https://forge.typo3.org/issues/48172

Try updating the relevant extensions and TYPO3. If everything is up-to-date and the error still occurs setting the TypoScript option plugin.tx_news.features.rewrittenPropertyMapper = 0 may help.

Exception while property mapping at property path "": Could not find a suitable type converter for "..." because no such class or interface exists. 

After adding an new model and clearing the caches (BE -> Flush system caches, rm -rf typo3temp/Cache/), the new class still was not found. Deactivating and reactivating the extension was solution.

Background: the autoload information (typo3temp/autoload/) wasn't flushed/updated. Since TYPO3 v8 there's a option in the install-tool for regenerating the autoconfiguration files.

Exception while property mapping at property path "...": Could not determine the child object type. 

Try clearing all caches.

Try to truncate the cf_extbase_reflection table after you modified the model.

Exception while property mapping at property path "Property 0" was not found in target object of type "..." 

When using extended models you need to set the base class variables to protected instead of private.

Another solution could be to truncate the "cf_extbase_reflection" table

This error is also displayed if a property in a fluid-form is wrong. In my case I had property="{object.propertyName}" instead of property="propertyName"

Exception while property mapping at property path "...":No converter found which can be used to convert from "array" to "string". 

The solution is there: http://stackoverflow.com/questions/16405963/typo3-how-to-use-file-upload-with-extbase

Exception while property mapping at property path "It is not allowed to map property "badproperty". ..." 

If badProperty is an ObjectStorage that holds references to other models and you want to edit this relation in a Fluid form with a multiselect or checkboxes, don't let Fluid convert your objects. So instead of doing this:

<f:form.checkbox property="yourProperty" value="{someObject}" />
Copied!

assign only the uid integers to the viewhelper, like this:

<f:form.checkbox property="yourProperty" value="{someObject.uid}" />
Copied!

Exception while property mapping at property path "":The target type was no string, but of type "NULL" 

See https://forge.typo3.org/issues/66049

This issue concerning passing an array of objects to a controller action should have been resolved in 7.x because the old property mapper has been removed completely.

Exception while property mapping at property path "": Path does not exist in array 

When resetting options in YAML config files for EXT:form write

formEditor:
  editors:
    700: null
Copied!

instead of

formEditor:
  editors:
    700:
      identifier: null
      templateName: null
      
      
Copied!

Exception while property mapping at property path "propertyname": The identity property "" is no UID. 

TYPO3 expects a relation as a property and can't find it. Check if a related database record exists (here: at "propertyname") and make sure to catch the error if no relation is present.

This can also happen if an extbase form has an object with a file upload element (and involved TypeConverters): If a bot maliciously spams your form, it might submit a POST/GET request with that type=file upload element, but uses type=text instead. This will lead into a structure, where the property will not contain the expected array data (tmp_name, name, errors, size, ... from $_FILES), and lead to this exception. In this case the error would say The Identity property "a2vsd3fs" is no UID, where a2vsd3fs is the actual random spam string submitted by the bot, even though it reads like a TYPO3 internal UID placeholder.

You can silence that error by using an initializeAction and checking if the mentioned properties actually are submitted as an array, or only as a string. But in fact, this exception would not be "wrong", because the actual bot request was faulty. But we wanted this recurring error not to flood our sys_log entries.

(TODO: This might also be fixable with better property mapping configuration and/or TypeConverter checks catching this error; the UploadedFileReferenceTypeConverter from Helmut Hummel was used in this case, which provoked the error above)

Exception while property mapping at property path "filter": No delimiter configured for TYPO3CMSExtbasePropertyTypeConverterArrayConverter and non-empty value given. 

This could happen if your Fluid ViewHelper for a checkbox is like this and filter is an array:

<f:form action="myAction" objectName="MyDto" object="MyDto">
    <f:form.checkbox property="filter" value="TYPO3" />
</f:form>
Copied!

You have to add multiple="1" in the Fluid ViewHelper:

<f:form action="myAction" objectName="MyDto" object="MyDto">
    <f:form.checkbox property="filter" value="TYPO3" multiple="1" />
</f:form>
Copied!

TYPO3 Exception 1297773150 

TYPO3 Exception 1297931020 

TYPO3 Exception 1297932028 

TYPO3 Exception 1297933823 

Object with identity "1234" not found. 

Error like that is thrown when you have an Extbase plugin on a page with a "single view" action, and the object with id 1234 can not be retrieved. E.g. because it is hidden or deleted.

Example for TYPO3 8.7:

/**
  * @param \TYPO3\CMS\Extbase\Mvc\RequestInterface $request
  * @param \TYPO3\CMS\Extbase\Mvc\ResponseInterface $response
  * @throws \Exception|\TYPO3\CMS\Extbase\Property\Exception
  */
 public function processRequest(\TYPO3\CMS\Extbase\Mvc\RequestInterface $request, \TYPO3\CMS\Extbase\Mvc\ResponseInterface $response)
 {
     try {
         parent::processRequest($request, $response);
     }
     catch(\TYPO3\CMS\Extbase\Property\Exception\TargetNotFoundException $e) {
         if ($e instanceof \TYPO3\CMS\Extbase\Property\Exception\TargetNotFoundException) {
             $GLOBALS['TSFE']->pageNotFoundAndExit('The given id could not be mapped to an object.');
         } else {
             throw $e;
         }
     }
 }
Copied!

In TYPO3 9.5, you can switch out the (now deprecated) pageNotfoundAndExit()-code with this:

return GeneralUtility::makeInstance(ErrorController::class)->pageNotFoundAction(
  $this->request,
  'The requested page does not exist',
  ['code' => PageAccessFailureReasons::PAGE_NOT_FOUND]
);
Copied!

TYPO3 Exception 1297935345 

TYPO3 Exception 1297941727 

TYPO3 Exception 1297948764 

TYPO3 Exception 1297951338 

TYPO3 Exception 1297951378 

TYPO3 Exception 1297978366 

TYPO3 Exception 1298012500 

Required argument "argumentName" is not set for SomeController->methodName. 

This happens when an action method requires a parameter (e.g. domain object), but the POST request did not contain that data.

This may happen when a form is submitted without filling any values.

Make sure the objectName parameter matches the method parameter name in your action:

<f:form action="someAction" objectName="argumentName" object="{someObjectName}">
Copied!

TYPO3 Exception 1298113624 

TYPO3 Exception 1298114279 

TYPO3 Exception 1298114280 

TYPO3 Exception 1298121373 

TYPO3 Exception 1298121573 

TYPO3 Exception 1298273089 

regularExpression "^[2356]$" in RegularExpressionValidator contained an error. 

#1298273089: regularExpression "^[2356]$" in RegularExpressionValidator contained an error. TYPO3\CMS\Extbase\Validation\Exception\InvalidValidationOptionsException thrown in file typo3/sysext/extbase/Classes/Validation/Validator/RegularExpressionValidator.php in line 50.

This happens when no regular expression delimiter is used.

Correct usage:

/**
 * @validate RegularExpression(regularExpression="/^[2356]$/")
 */
public $someOption;
Copied!

TYPO3 Exception 1299158548 

TYPO3 Exception 1299233097 

TYPO3 Exception 1299514081 

TYPO3 Exception 1299514082 

TYPO3 Exception 1299514083 

TYPO3 Exception 1299514084 

TYPO3 Exception 1300086584 

TYPO3 Exception 1300096564 

TYPO3 Exception 1300098528 

Incorrect reference to original file given for FileReference. 

Observed in TYPO3 7.6 & 8.7: This error occurs, when TCA media field configuration is missing --palette--;;filePalette entry in showitem, which is required. This often happens, if you manipulate showitem configuration, to hide sys_file_reference fields.

TYPO3 Exception 1300098529 

TYPO3 Exception 1300694875 

TYPO3 Exception 1300782487 

TYPO3 Exception 1300782488 

TYPO3 Exception 1300787096 

TYPO3 Exception 1300893885 

TYPO3 Exception 1300893886 

TYPO3 Exception 1300902143 

TYPO3 Exception 1301491089 

TYPO3 Exception 1301579637 

TYPO3 Exception 1301614535 

TYPO3 Exception 1301614537 

TYPO3 Exception 1301648167 

ServiceUnavailableException: TypoScriptFrontendController 

addRootLineFields which are not available 

Happens if you have set some additional fields in $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields'] which do not exist in the database table pages. Try to do a DB COMPARE. If you got this error, check if you have defined non-existent fields in your $GLOBALS['TYPO3_CONF_VARS']['FE']['addRootLineFields'] configuration.

TypoScript PAGE cObject is missing 

In certain cases, it is possible that this error occurs, when the necessary PAGE cObject (e.g. page = PAGE) isn't available with the requested typeNum. Check if your TypoScript setup is completely loaded.

TYPO3 4.7.x 

Mountpoints and Shortcut Pages 

https://forge.typo3.org/issues/14351

If you have a shortcut page which links to "first subpage" and the first subpage is a mountpoint, than you will run into this error.

Do not use "first subpage" if the first visible(!) subpage is a mountpage. You can select the mountpage as shortcut target - just do not use the automatic functions ("first subpage", "random subpage"...)

Realurl and Mountpoints 

If you use realurl and mountpoints. It seems that RealUrl cannot/does not remove the cache entries, if you change a mountpage to a normal page. If you got this error, go to the mountpoint itself and remove all cacheentries.

TYPO3 4.7.4, realurl 1.12.3

TYPO3 Exception 1301648234 

TYPO3 Exception 1301648328 

This page is of type "Shortcut" and configured to redirect to a subpage. However, this page has no accessible subpages. 

The shortcut must be changed in the Page Properties to point to a valid page.

TYPO3 Exception 1301648358 

TYPO3 Exception 1301648404 

This page is of type "Shortcut" and configured to redirect to a page, which is not accessible. 

This exception is thrown when a shortcut page with id X is pointing to a page with id Y which is not accessible for some reason (example: if page with id Y is hidden).

The message of this exception is: This page (ID X) is of type "Shortcut" and configured to redirect to a page, which is not accessible (ID Y).

TYPO3 also sends a 404 header in this case, that should be handled by the Page Not Found Handler.

Likely reasons how this could happen:

  • The editor has created a page as shortcut and did not define where the shortcut should go to.
  • The page the shortcut pointed to was hidden or removed.

In each case, editing the given page (last parameter of getPageShortcut) and setting the correct (new) page to shortcut too should solve the issue.

TYPO3 Exception 1301648780 

PageNotFoundException 

Wrong Site Configuration 

In LTS 9 this exception occurs when the rootPageId in the site config (config/sites/domainname/config.yaml) does not match the pageId of the page that is set as root page.

Wrong preview/extension configuration 

The Exception occurred after updating to 6.2.9. When editing a tx_cal_event (/typo3/alt_doc.php?edit[tx_cal_event][135]=edit) and using any of the "Save"-Links, the Error "Page Not Found (404) The requested page does not exist!" is shown and nothing is saved. The resulting URL is /typo3/alt_doc.php?&edit[tx_cal_event][135]=edit&returnUrl=dummy.php which might hold two hints: dummy.php and the missing key/value in the query string directly after the question mark.

SOLUTION The solution was, that the SysFolder had a Page TSconfig entry options.tx_cal_controller.pageIDForPlugin = 419. The page 419 had been deleted. After removing the option cal worked again. So be sure to check the page TSconfig for wrong entries

TYPO3 Exception 1301648781 

PageNotFoundException 

Happens when a page cannot be accessed for any reason. Please check the given error message for further hints.

TYPO3 Exception 1301648782 

ServiceUnavailableException 

May happen any time TYPO3 is unable to respond correctly, for example:

  • Granted privileges to the database user on the wrong database
  • Used the wrong database credentials

TYPO3 Exception 1301648945 

Database Error 

Database Error: The current username, password or host was not accepted when the connection to the database was attempted to be established!

This means, you have to add / check the credentials TYPO3 uses for database connections. Edit them via the Install Tool or in the typo3conf/localconf.php file.

TYPO3 Exception 1301648975 

ServiceUnavailableException 

Can happen for many different reasons, for example

  • No pages in page tree: calling the frontend will result in this error (depending on your TYPO3 version)

TYPO3 Exception 1301654458 

Parser for plain old PHP array is not yet implemented. 

Check your system for extensions that still use the old format for language resources (locallang.php). Remove them or update them to locallang.xlf format.

TYPO3 Exception 1301827270 

TYPO3 Exception 1302855001 

TYPO3 Exception 1303236963 

TYPO3 Exception 1303236964 

TYPO3 Exception 1303236965 

TYPO3 Exception 1303236966 

TYPO3 Exception 1303236967 

TYPO3 Exception 1303237468 

TYPO3 12.4.5 - 16.08.23 

The Issue 

This error happens when calling \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTcaSelectItem() on an item that is not a valid select item or does not have an items array.

Solution 

My select item did not have an items array, adding an empty items array fixed it:

EXT:my_sitepackage/Configuration/TCA/tx_my_sitepackage_table.php
'type' => [
    'label' => 'Typ',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'items' => [],
    ],
],
Copied!

TYPO3 Exception 1303379126 

TYPO3 Exception 1303379158 

TYPO3 Exception 1303662955 

TYPO3 Exception 1303662956 

TYPO3 Exception 1303669848 

The directory "..." cannot be created. 

This error is thrown by the TYPO3 Cache SimpleFileBackend when trying to create the cache directory.

If the directory already exists, make sure that the correct file permissions are set and the web server is allowed to write files there.

TYPO3 Exception 1304538165 

TYPO3 Exception 1304950007 

TYPO3 Exception 1304964032 

TYPO3 Exception 1305059666 

TYPO3 Exception 1305100019 

TYPO3 Exception 1305111499 

TYPO3 Exception 1305111513 

TYPO3 Exception 1305438528 

TYPO3 Exception 1305630314 

TYPO3 Exception 1306332397 

TYPO3 Exception 1306410755 

TYPO3 Exception 1306424308 

TYPO3 Exception 1306755296 

TYPO3 Exception 1306755520 

TYPO3 Exception 1306866845 

TYPO3 Exception 1307190365 

TYPO3 Exception 1307293692 

TYPO3 Exception 1307293693 

TYPO3 Exception 1307719569 

TYPO3 Exception 1307719788 

TYPO3 Exception 1308003914 

TYPO3 Exception 1308240974 

TYPO3 Exception 1308255491 

TYPO3 Exception 1308270454 

TYPO3 Exception 1308354399 

TYPO3 Exception 1308355095 

TYPO3 Exception 1308355268 

TYPO3 Exception 1308662891 

TYPO3 Exception 1308898491 

TYPO3 Exception 1308898501 

TYPO3 Exception 1308957498 

TYPO3 Exception 1309245002 

TYPO3 Exception 1309255650 

TYPO3 Exception 1309255651 

Invalid type encountered: "..." 

The provided phpdoc annotation contains a type that is not recognized.

This can e.g. happen if you model contains properties of the type Date instead of DateTime - edit the model and make sure that only known and valid types are used.

Known and valid types are PHP simple types (like int or float) or class names.

Take care af annotations in getters, setters and class-property declarations.

TYPO3 Exception 1309971820 

TYPO3 Exception 1309971821 

TYPO3 Exception 1310027337 

TYPO3 Exception 1310027383 

TYPO3 Exception 1310027408 

TYPO3 Exception 1310027427 

TYPO3 Exception 1310027490 

TYPO3 Exception 1310027511 

TYPO3 Exception 1310027655 

TYPO3 Exception 1310027685 

TYPO3 Exception 1310027716 

TYPO3 Exception 1310027740 

TYPO3 Exception 1310027793 

ERROR: Query could not be parsed: "..." 

This error happens in TYPO3 versions below 8 when a database query could not be parsed. Take note of the query and:

  • if you are a developer: check your code for valid SQL
  • if you are an administrator: try executing the failing query manually via a SQL client

TYPO3 Exception 1310027833 

TYPO3 Exception 1310027933 

DBAL fatal error: No handler found in handler_getFromTableList() 

see https://forge.typo3.org/issues/59829 for a hint towards the cause and/or workaround.

TYPO3 Exception 1310027975 

TYPO3 Exception 1310027995 

TYPO3 Exception 1310028018 

TYPO3 Exception 1310028048 

TYPO3 Exception 1310203812 

TYPO3 Exception 1310203813 

TYPO3 Exception 1310203814 

TYPO3 Exception 1310203815 

TYPO3 Exception 1310556663 

TYPO3 Exception 1310557169 

TYPO3 Exception 1310931362 

TYPO3 Exception 1311942539 

TYPO3 Exception 1312140064 

(This exception happens only on very old TYPO3 versions - please consider updating your system to a secure version.)

You should use the following hook

$GLOBALS['TYPO3_CONF_VARS']['typo3/backend.php']['additionalBackendItems'][] = filepath
Copied!

and execute t3lib_extMgm::addModuleJsFile in the above file.

TYPO3 Exception 1312140065 

(This exception happens only on very old TYPO3 versions - please consider updating your system to a secure version.)

You should use the following hook

$GLOBALS['TYPO3_CONF_VARS']['typo3/backend.php']['additionalBackendItems'][] = filepath
Copied!

and execute t3lib_extMgm::addModuleCssFile in the above file.

TYPO3 Exception 1312215888 

TYPO3 Exception 1312222064 

TYPO3 Exception 1312223779 

TYPO3 Exception 1312830504 

TYPO3 Exception 1313185906 

TYPO3 Exception 1313185907 

TYPO3 Exception 1313185908 

TYPO3 Exception 1313828196 

TYPO3 Exception 1313855173 

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.
  2. 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!
  3. 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 {
// ...
}
Copied!

TYPO3 Exception 1313855175 

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

  • Check your configurePlugin() configuration
  • Check if you have a Resources/Private/Templates/{controller}/{action}.html For details, please see https://forge.typo3.org/issues/31322
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    '<ExtensionName>,
    '<PluginName>',
    [
        \Vendor\ExtensionName\Controller\YourController::class => 'yourAction',
    ],
    // non-cacheable actions
    [

    ]
);



Copied!

or as of extbase 4.7 you need to update your FlexForm with all necessary actions (semicolon separated) in case you use switchableControllerActions:

<switchableControllerActions>
  <TCEforms>
    <label>LLL:EXT:kofomi/Resources/Private/Language/locallang_be.xml:flexforms_general.mode</label>
    <onChange>reload</onChange>
    <config>
      <type>select</type>
      <items>
        <numIndex index="0">
          <numIndex index="0">LLL:EXT:kofomi/Resources/Private/Language/locallang_be.xml:flexforms_general.mode.eventgroups</numIndex>
          <numIndex index="1">Events->list;Events->show</numIndex>
        </numIndex>
        <numIndex index="1">
          <numIndex index="0">LLL:EXT:kofomi/Resources/Private/Language/locallang_be.xml:flexforms_general.mode.persons</numIndex>
          <numIndex index="1">Persons->list;Persons->show</numIndex>
        </numIndex>
      </items>
    </config>
  </TCEforms>
</switchableControllerActions>
Copied!

or

If you tried using FlexForms with switchableControllerAction this overwrites your ext_localconf.php even if you delete the Flexform and the link in your ext_tables.php. To work with your extension again edit the table tt_content and search for switchableControllerAction in the column pi_flexform and delete the content of this field and everything works fine again without FlexForm.

Another issue that can occur is an issue with realurl configuration. It may pass action params as uppercase e.g. 'Show' instead of 'show'. Either fix the realurl configuration or allow actions in uppercase.

Also, as developer if you changed the FlexForm above, remember to change the plugin configuration on the referencing page as well. The page configuration overrides the plugin configuration and will still have the old (now invalid) value stored.

TYPO3 Exception 1313857897 

TYPO3 Exception 1313857898 

TYPO3 Exception 1314085990 

Desired storage "..." is not in the list of available storages. 

See also:

TYPO3 Exception 1314085991 

TYPO3 Exception 1314085992 

TYPO3 Exception 1314085999 

TYPO3 Exception 1314226805 

Property "..." was not found in file reference or original file 

Happens if the field is missing in database. Go to Database Analyzer in Install Tool and add the field.

Property "width" was not found in file reference or original file 

Happens if the file metadata is missing in database. This might happen if the file record was imported. To fix it run FileStorageIndexingTask via ext:scheduler or restore the metadata.

TYPO3 Exception 1314349666 

TYPO3 Exception 1314354065 

TYPO3 Exception 1314354066 

TYPO3 Exception 1314390127 

TYPO3 Exception 1314455642 

Error during file indexing: "..." 

Exception in TYPO3 6.1 Backend show content in fileadmin folder 

After upload a broken image the following error occurred:

Error during file indexing: "Column 'height' cannot be null".

Solution: Find the broken image and delete it.

ERROR during Upgrade TYPO3 4.5 to 6.1 

During using the Upgrade Wizard at step Migrate all file relations from `tt_content.image` and `pages.media` the following error occurred:

Oops, an error occurred! Error during file indexing: "Unknown column 'creation_date' in 'field list'"

Solution: You have to run compare' first. Then the Upgrade Wizard worked fine

TYPO3 Exception 1314516809 

File "..." does not exist 

Check case sensitivity setting in `File storage` record 

Most problems arise when you are migrating from a case-insensitive to a case-sensitive file system, or when an auto-generated File Storage didn't recognize case-sensitivity correctly.

In such a situation the created File storage saves file identifiers with lower-case in the database and can't find files which have mixed-case file names.

Solution 

Find all File Storages via module List on page zero and on tab Configuration check the Uses case sensitive identifiers checkbox.

Other possibilities 

  • This error occurs when a media resource (image, PDF) is deleted from the server but remains linked via the "media" extension and FAL.
  • The message appears when the file is in the directory, but not the record in the DB.
  • It happens when you upload a file with the name in uppercase. The file has been uploaded, but the reference record is not created. Solution: delete the file from the directory and upload the file in lowercase (and check if setting "case sensitivity" in File Storage record is set correctly).

Situation: Entering Upgrade Wizard after upgrading to 8.7 

Exception gets thrown when entering Upgrade Wizard:

Uncaught TYPO3 Exception
#1314516809: File /user_upload//foto_ba\'s.JPG does not exist. (More information)

Copied!

The file does exist but is still referenced.

Important Set configuration presets to "Debug" to see where problem occurs (You should not do this in production system though).

Workaround:

For this specific case: (the exception may be caused by other things, though)

  • "Fix" the filename.
  • Mark FormFileExtensionUpdate as done

See also: https://forge.typo3.org/issues/85685

Situation: Upgrade from 6.1 to 6.2 

This error occurs at this step of the upgrade process :

Migrate all RTE magic images from uploads/RTEmagicC_\* to fileadmin/_migrated/RTE/

The solution is to update the general reference index ( sys_refindex) via the TYPO3 Backend:

TYPO3 backend, ADMIN TOOLS > DB check > Manage Reference Index

Situation: Upgrading from very old DAM versions 

DAM versions up to 1.1.7 allowed users to circumvent TYPO3's file and folder name sanitization, so users could enter files containing e.g. space characters. While that may not have caused any issues on TYPO3 4.x, it will result in various obscure errors in 6.x, not just this exception.

DAM 1.1.8 added sanitization but still failed to sanitize folder names when renaming existing folders. This issue has been fixed later (at latest on 1.2.4, exact release not identified yet).

As 1.1.8 fixed most of these issues and was released just one day (25 January 2011) before TYPO3 4.5 you should only encounter this issue on very old TYPO3/DAM installations.

Solution: Identify all file paths containing spaces which are currently in use (to keep amount of work low) via database and rename them manually. Warn your editors to check file names if currently unused files are affected (simply remove the number_of_references condition below). Assuming reference index is reliable:

SELECT * FROM sys_file WHERE identifier LIKE "% %" AND number_of_references > 0;
Copied!

TYPO3 Exception 1314516810 

File "..." does not exist. 

In general: the mentioned file or folder does not exist, check if the file or folder is available and has the correct file permissions.

Introduction Package 

A logo file is missing when the introduction is installed.

Workaround 1 

A workaround is to edit the TypoScript template on the root page and comment the first line //page.logo.file = fileadmin/introduction/images/theme/IntroductionPackage.png

Workaround 2 

Another solution is to go to the web root of your TYPO3 installation (e.g. /home/typo3/www/ or /home/typo3/htdocs/) and execute the following shell commands which will copy the missing file to where it is supposed to be:

mkdir fileadmin/introduction/images/theme/

cp typo3conf/ext/introduction/Initialisation/Files/images/theme/IntroductionPackage.png fileadmin/introduction/images/theme/
Copied!

TYPO3 Exception 1314778269 

Cannot add a file that is already part of this storage. 

FAL: addFile() 

Error when adding a sys_file to a FAL storage via $this->storage->addFile($localFilePath, $targetFolder, $targetFileName):

The exception is thrown when the $localFilePath (the source file) is already located anywhere inside of the target's FAL local storage path. For example, inside of fileadmin/ when using the default local storage.

TYPO3 Exception 1314803096 

TYPO3 Exception 1314979197 

TYPO3 Exception 1314979451 

TYPO3 Exception 1315314711 

TYPO3 Exception 1315314712 

TYPO3 Exception 1315554770 

TYPO3 Exception 1315564744 

TYPO3 Exception 1316000297 

TYPO3 Exception 1316000298 

TYPO3 Exception 1316104317 

#1316104317 TYPO3\CMS\Extbase\Mvc\Exception 
The default controller for extension "..." and plugin "..." can not be determined.`
Copied!

If this happens for your own extensions: 

Basic requirements 

This basically means that you need to define a controller in your ext_localconf.php. Usually the first entry is taken as default controller/action. Here's an example:

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
  //assuming your extension is in typo3conf/ext/your_ext folder
  'YourExt',

  // Plugin name
  'Pi1',

  // An array of controller-action combinations. The first one found is the default one.
  [
    \YourVendor\YourExt\Controller\YourController::class => 'index,new,create,edit,update'
  ],

  // An array of non-cacheable controller-action-combinations (they must already be enabled)
  [
    \YourVendor\YourExt\Controller\YourController::class => 'new,create,edit,update'
  ],
);
Copied!

Situation: Adding your plugin via TypoScript 

This error can appear if you got your TypoScript wrong. Make sure that you write your settings with the first letter in uppercase and double-check your ext_localconf.php.

lib.test = USER_INT
lib.test {
  # Calling the extbase bootstrapper
  userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run

  # Upper camel case!
  extensionName = YourExt
  vendorName = YourVendor

  # As you set it in \TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin
  pluginName = Pi1
}
Copied!

Situation: Adding the Plugin via FlexForm Plugin 

Extbase has the possibility to override internal configuration from FlexForms. This error might appear if you change a plugin from different types.

Try deleting the plugin instance and add a new one, or clear tt_content.pi_flexform field for current plugin, to avoid wrong switchableControllerActions from FlexForm.

If this still isn't resolved, or happens for 3rd party extensions: 

Broken routing configuration: 

If you got this error for e.g. EXT:news which probably shouldn't be badly configured, it can be a broken routing configuration. So check your site yaml (includes) for

routeEnhancers:
  News:
    type: Extbase
    extension: News
Copied!

And replace the lines following that with a default solution from the docs.

Bad redirects: 

If you have a httpd redirect, custom early middleware redirect, or a TYPO3 redirect configured for the URL, even a simple one like redirecting /paths to variants with trailing slash /paths/ then this can happen, too. Although that is more common with POST scenarios. Removing that redirect could resolve that problem.

TYPO3 Exception 1316504665 

TYPO3 Exception 1316779798 

TYPO3 Exception 1316789798 

TYPO3 Exception 1316889798 

TYPO3 Exception 1317048056 

TYPO3 Exception 1317050430 

TYPO3 Exception 1317178604 

No file found for given UID. 

TYPO3 CMS 6.1.2: Error while uploading previously deleted file 

Having deleted a specific file before at the fileadmin it's not possible to upload the same file again without error "No file found for given UID.". You can't open the fileadmin folder containing the file once again uploaded afterwards. At the sys_file table the misbehaving file's entry shows "deleted = 1" before and after upload. Workaround: Deleting the sys_file entry of that file via phpMyadmin. This is forcing TYPO3 fileadmin to create a new sys_file entry with a different uid. Now the folder and it´s content are available again.

Related to Bug #50508

TYPO3 CMS 6.2.x - happened when a tt_news entry had an non-existing image in the bodytext 

For some reason the preview did still exist and was shown in BE when editing the news record. But in FE this lead to the exception, because the sys_file record was not there anymore.

EXT:solr + EXT:solrfal 

The exception happened when initializing fileadmin/ queue. File record was missing in sys_file but existed in sys_file_reference and sys_file_processedfile. The following SQL helped:

delete from sys_file_reference where uid_local not in (select uid from
sys_file); truncate sys_file_processedfile;
Copied!

The exception can also happen when there are non-existing files for indexing in tx_solr_indexqueue_file and the the records are not deleted with "Clear Index Queue" for unknown reasons. This SQL helped:

truncate tx_solr_indexqueue_file;
Copied!

TYPO3 Exception 1317178794 

No file usage (sys_file_reference) found for given UID. 

After adding a file mount 

You'll probably get this error if you add a file mount after creating content containing images or links to files. (Using FAL.)

Solution 

Check the Upgrade Wizard in the Install Tool to make sure that there are no outstanding FAL migration actions required.

If the error appears on every page, the issue may be that a content element or resource is being inherited from a different page (higher up the tree structure.)

Workaround 

There is a bug in TYPO3 6.2.15 which leads to a wrong SQL query. That will raise this exception.

SELECT * FROM sys_file_reference WHERE uid=1 AND sys_file_reference.deleted=0
Copied!

Just make sure that your first several (maximum number of assigned file references to your extension table) records of the table sys_file_reference are not marked as deleted. If this SQL query executes successfully, then it will work.

From a eID script 

This problem may happen if you are in the context of a eID script and you forgot to load the TCA from EXT:core (namely the TCA for sys_file and sys_file_reference.

TYPO3 Exception 1318283565 

Login into TYPO3 is not possible anymore, as no OpenSSL backend for rsaauth is available. 

  • Activate and configure (on Windows) the PHP module openssl
  • Configure rsaauth to use the openssl executable inside localconf.php

    • Set $TYPO3_CONF_VARS['SYS']['binSetup'] to the executable. E.g. 'openssl=C:/ ... /openssl.exe'
    • If your path to openssl.exe contains blanks, make sure to quote the openssl parameter, e.g. 'openssl="C:/ ... /openssl.exe"'
  • Set $TYPO3_CONF_VARS[TYPO3_mode]['loginSecurityLevel'] to 'normal' instead of 'rsa' (replace TYPO3_mode with BE or FE) and set the hash of your user account's password to the md5 hashed value of your password. This way you can at least access your installation. Please be aware that this is a bad idea and disabling rsaauth/saltedpasswords results in all your passwords being unusable, until openssl is available.

Windows 7 and Xampp 

Assuming you installed Xampp into C:\xampp:

  • Activate the PHP module openssl in C:\xampp\php\php.ini. Look for this line:
;extension=php_openssl.dll
Copied!
  • Load fileinfo module as well. Look for this line and uncomment it:
;extension=php_fileinfo.dll
Copied!
  • Add an environment variable "OPENSSL_CONF" with value C:\xampp\apache\conf\openssl.cnf. Press "Win + PAUSE" to go to the System window. In the left sidebar are the system settings.
  • Either set $TYPO3_CONF_VARS['SYS']['binSetup'] to 'openssl=C:\xampp\apache\bin\openssl.exe' or append C:\xampp\apache\bin to the environment variable PATH (will work for every PHP script not only TYPO3)

    • If your path to openssl.exe contains blanks, make sure to quote the openssl parameter, e.g. 'openssl="C:/ ... /openssl.exe"'
  • Restart Apache
  • If Apache won't start, deactivate the apache ssl module (php has its own) in C:\xampp\apache\conf\httpd.conf like so:
#LoadModule ssl_module modules/mod_ssl.so
Copied!

and near the end of the file:

#Include conf/extra/httpd-ssl.conf
Copied!
  • Copy libeay32.ddl and ssleay32.dll from C:\xampp\php\\ to C:\xampp\apache\bin\\

Solution for Windows 10 with XAMPP 

I have a 64-bit Windows 10 laptop upon which I installed XAMPP and TYPO3 v8.7.10. For days I struggled with the following message during TYPO3 install cited as a catastrophic failure under "System Environment" evaluations:

PHP OpenSSL extension not working Something went wrong while trying to create a new private key for testing. Please check the integration of the PHP OpenSSL extension and if it is installed correctly.

Finally, after trying all kind of OpenSSL-related installation verifications, I found a solution at this link ... https://stackoverflow.com/questions/4719939/xampp-openssl-errors-when-calling-openssl-pkey-new?rq=1 ...

At the bottom it said; "...start apache using the xampp/apache_start.bat NOT THE XAMPP CONTROL PANEL (its strange that when started from the control panel it doesn't work [maybe a current directory problem])".

After launching apache with xampp/apache_start.bat, I could launch everything else (esp. MySQL) using the XAMPP Control Panel, which did detect Apache was already running. Next, I returned to TYPO3 8.7.10 install checks, and the OpenSSL problem was gone!

I do not know what is the difference (directory spec or what?) between XAMPP Control Panel and xampp/apache_start.bat.

TYPO3 Exception 1319217244 

TYPO3 Exception 1319219349 

TYPO3 Exception 1319219350 

TYPO3 Exception 1319219351 

TYPO3 Exception 1319219352 

TYPO3 Exception 1319455097 

Error while fetching permissions for "..." 

Issue occurs because of offline filestorage 

Go to page 0 and check your file storage records. If they are offline at the moment, set them online. After saving check whether they are still offline. If this is the case, check whether the defined file path exists on the system. TYPO3 will set file storages offline if they can't be "mounted" because they are not there.

After the folder exists and the record is set to online, the issue should be solved in most cases.

Unicode files 

It maybe connected to unicode file names handling - it can happen with names like Økonomi.jpg. If you have such file in folder then you can have following error message:

In this case check 2 things:

  1. Settings in config should contain: [SYS][UTF8filesystem] = true [SYS][systemLocale] = 'en_US.utf8'
  2. See in server's shell whether your file system supports unicode/utf-8 names, using for example command 'locale'

UTF-8 problems 

UTF-8 named files may become damaged/mangled upon transferring them via (S)FTP. For example using Transmit/Coda between OS X and a linux server. Use scp, rsync or lftp to transfer such files. Alternatively, also compressing them in a tar.gz for the move may help.

Default storage setting missing 

Problem occurred for me after updating from TYPO3 6.2.10 to 6.2.11 and 6.2.12 – contrary to https://forge.typo3.org/issues/58403#note-3 I re-created a file storage for /, but without setting it as default (fileadmin/ is still the default storage).

Migrate all RTE magic images 

Got this exception during update 4.5.40 to 6.2.12 at "Migrate all RTE magic images from uploads/RTEmagicC_\* to fileadmin/_migrated/RTE/".

Solution: Delete unwanted entries from sys_file_storage.

Remove /uploads from filemounts 

Remove the uploads-folder from filemounts, log out and log in.

TYPO3 Exception 1319488194 

TYPO3 Exception 1319488195 

TYPO3 Exception 1319550405 

TYPO3 Exception 1319550415 

TYPO3 Exception 1319550425 

You are not allowed to delete the file "..." 

FAL checks for sufficient user rights. The user is not allowed to see the folder or file or has no permissions to delete files in the given folder.

Solution:

  • Add a file mount for this folder and give it to the user/usergroup. This however means that the user may see *all* files in the folder, not only his own.
  • Make sure the user has sufficient access permissions to that folder.

TYPO3 Exception 1319550426 

TYPO3 Exception 1319550435 

TYPO3 Exception 1319552745 

TYPO3 Exception 1319552746 

TYPO3 Exception 1319553317 

TYPO3 Exception 1320122453 

TYPO3 Exception 1320286857 

File "..." is not valid (".." and "//" is not allowed in path). 

File Record Wizard 

This error occurs e.g. when a file-name contains an umlaut. By removing the umlaut this can fix this issue. However, if it doesn't check the other posted solutions in this entry.

RTE// CKEditor with Core v9+ 

This issue occurred to me by misusing the softref config within the bodytext TCA configuration in an override. (in my concrete example)

This bug behaved like the following with the relevant content in line 1 of the bodytext editor input:

  • Saving 'test test' -> works
  • Saving 'testtest' -> error
  • Saving 'test' -> error

When 'softref' is set to e.g. the bodytext field, the DataHandler calls updateRefIndexTable of the ReferenceIndex. The Stacktrace leads through the SoftReferenceIndex and its getTypoLinkParts function. There the TypoLinkCodecService is called with ->decode(...) This functionality is used to resolve links, while it splits on spaces. This is the reason why 'testtest' fails and 'test test' does not. 'testtest' gets wrapped with it's p-Tags and results in invalid linkhandling while 'test test' gets split into '< p > test' which is not correct, but does not throw an exception.

RTE 

I noticed this issue when RTE had an incorrect link:

<link ../fileadmin/user_upload/documents/myhomeplan.pdf>

TYPO3 specifically reported that the file path is incorrect and that ".." and "//" are not allowed in the beginning of file path.

This happened for us after we migrated from 4.5.x to 4.6.x.

  • Solution: Remove the invalid link via phpmyadmin or similar tools
  • Can affect: Any table, ex: news, tt_news etc...
  • Sometimes, we may even get into this situation when the file in question has been renamed/moved/missing.

TYPO3 Exception 1320288991 

TYPO3 Exception 1320291063 

TYPO3 Exception 1320291064 

TYPO3 Exception 1320375115 

TYPO3 Exception 1320375116 

TYPO3 Exception 1320381534 

TYPO3 Exception 1320569854 

Creating file "..." failed. 

http://lists.typo3.org/pipermail/typo3-dev/2012-July/045668.html

TYPO3 Exception 1320572272 

TYPO3 Exception 1320575630 

Folder does not exist. 

See also: forge.typo3.org/issues/51808 forge.typo3.org/issues/51747

TYPO3 Exception 1320577649 

TYPO3 Exception 1320585902 

$hookObject must implement interface TYPO3\CMS\Core\Database\TableConfigurationPostProcessingHookInterface 

The $hookObject registered does not implement the interface.

Related bug reports are 67933: TYPO3 Core - compatibility6 crashes TYPO3 BE [Closed] and 68480: TYPO3 Core - compatibility6 crashes TYPO3 BE - part 2 [Closed; assigned to Helmut Hummel]. Both are marked as resolved though.

TYPO3 Exception 1320711817 

TYPO3 Exception 1320829762 

TYPO3 Exception 1320830018 

TYPO3 Exception 1320830276 

TYPO3 Exception 1320833203 

TYPO3 Exception 1320855304 

Deletion of file "..." failed. 

Check the File-Permissions of this file. To solve this issue: either delete the mentioned file or change it's permissions.

Example of problem resolution on Linux 

chown -R www-data:www-data /path/to/site/
chmod -R 775 /path/to/site/
Copied!

TYPO3 Exception 1321023156 

InvalidArgumentException 

https://forge.typo3.org/issues/52972

TYPO3 Exception 1321113658 

TYPO3 Exception 1321288316 

TYPO3 Exception 1321637121 

TYPO3 Exception 1321696151 

TYPO3 Exception 1321696152 

TYPO3 Exception 1321722682 

TYPO3 Exception 1321804422 

Could not open log file "..." 

  • Check file permissions of the mentioned file.
  • Try deleting the file and let TYPO3 recreate it.

TYPO3 Exception 1321860519 

TYPO3 Exception 1321862231 

TYPO3 Exception 1322110041 

TYPO3 Exception 1322110455 

TYPO3 Exception 1322112430 

TYPO3 Exception 1322120271 

TYPO3 Exception 1322120356 

TYPO3 Exception 1322121068 

TYPO3 Exception 1322287600 

TYPO3 Exception 1322415256 

TYPO3 Exception 1322545589 

TYPO3 Exception 1322545626 

TYPO3 Exception 1323006478 

TYPO3 Exception 1323059807 

You are not allowed to create directories in the folder "..." 

Related bugs:

Possible solution: Remove the default File Storage Item that the migration tool has created and set to /.

TYPO3 Exception 1323344192 

TYPO3 Exception 1323344193 

TYPO3 Exception 1323353176 

TYPO3 Exception 1323423953 

TYPO3 Exception 1323697654 

TYPO3 Exception 1323961907 

TYPO3 Exception 1325191178 

TYPO3 Exception 1325194291 

TYPO3 Exception 1325418870 

TYPO3 Exception 1325419305 

TYPO3 Exception 1325663761 

TYPO3 Exception 1325665144 

TYPO3 Exception 1325689164 

Parent folder "..." does not exist. 

A file storage with an unreachable base path has been accessed. This might happen after importing a database.

Check the filemount entries with the list module.

Are the folder paths in the field "base path" correct?

TYPO3 Exception 1325689855 

TYPO3 Exception 1325697085 

TYPO3 Exception 1325777289 

TYPO3 Exception 1325842622 

TYPO3 Exception 1325861239 

TYPO3 Exception 1325862240 

TYPO3 Exception 1325862241 

TYPO3 Exception 1325938973 

TYPO3 Exception 1325952534 

TYPO3 Exception 1326089744 

TYPO3 Exception 1326090127 

TYPO3 Exception 1326095912 

TYPO3 Exception 1326096024 

TYPO3 Exception 1326277369 

TYPO3 Exception 1326406447 

TYPO3 Exception 1326411176 

TYPO3 Exception 1326803398 

TYPO3 Exception 1327058829 

TYPO3 Exception 1327060200 

[11.5.12] - [02.07.2022] 

Situation 

Error on sending the form:

(1/1) #1327060200 TYPO3\CMS\Form\Domain\Finishers\Exception\FinisherException
The option "recipients" must be set for the EmailFinisher.
Copied!

Solution 

There was a leading white space in the recipient's email address:

Wrong yaml
finishers:
-
  options:
    recipients:
      ' info@example.org': 'Name'
      
      
Copied!
Correct yaml
finishers:
-
  options:
    recipients:
      'info@example.org': 'Name'
Copied!

[v11.5.12] - [08-07-2022] 

Solution 2 

Older versions of EXT:form used 'recipientAddress' and 'recipientName', they are now replaced by 'recipients'. Either simply open and directly save the form in the Form backend module, the backend module will automatically rewrite the old options to the new one, or make the adjustments manually:

Old yaml, no longer working in v11
finishers:
-
  options:
    recipientAddress: email@example.com
    recipientName: '{text-1}'
      
      
Copied!
New yaml
finishers:
-
  options:
    recipients:
      email@example.com: '{text-1}'
Copied!

TYPO3 Exception 1327060210 

TYPO3 Exception 1327060320 

TYPO3 Exception 1327065745 

Unsupported or non-existing property name "..." used in relation matching 

Changed Caching 

Caching TCA information changed in TYPO3 v8.

Solution: 

From the core API docs:

The second way is to call \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::makeCategorizable(). This method adds a new entry into the registry managed by \TYPO3\CMS\Core\Category\CategoryRegistry. The registry will take care of adding the relevant $TCA definition to create a field for making relations to the system categories. The call to makeCategorizable() must be located in an extension's Configuration/TCA/Overrides folder (or ext_tables.php file before TYPO3 CMS 6.2.1).

Wrong Relation 

Use of 1:1 relation in domain model but querying it as a n:m relation.

Solution: 

The query must use equals() for 1:1 relation. If you use contains() extbase will expects a 1:n or n:m relation.

TYPO3 Exception 1327318156 

TYPO3 Exception 1327587091 

TYPO3 Exception 1327587092 

TYPO3 Exception 1327678173 

TYPO3 Exception 1328646798 

TYPO3 Exception 1328709784 

The finisher preset identified by "xxx" could not be found, or the implementationClassName was not specified. 

This error is related to EXT:form.

You probably added a custom finisher to your current form configuration yaml file, but forgot to register the finisher in base config of your form setup.

Please ensure that you add your newly created form finisher to config section: TYPO3.CMS.Form.prototypes.standard.finishersDefinition

And that yaml is loaded to the plugin and/or module form settings: plugin.tx_form.settings.yamlConfigurations

It could also be the case that you correctly registered the finisher in the base config of your form setup (e.g. in the root template of your site) but the registration will not work because there might be a syntax error in the typoscript (e.g. a missing closing curly brace from an open code-block); in that case, the registration will not succeed and hence, the form framework is not able to find the finisher. This will most likely happen during a major upgrade of TYPO3 when there are typically bigger changes in your typoscript setup.

TYPO3 Exception 1328710202 

TYPO3 12.4.25 with EXT:recaptcha - 25.01.2025 

Installation Overview 

After installing evoweb/recaptcha the following error occurs on vieweing any page in the frontend:

The Issue 

Solution 

You need to include the TypoScript includes of the extension or the site set on each site that in the installation.

TYPO3 Exception 1328734617 

TYPO3 Exception 1329219449 

TYPO3 Exception 1329233410 

TYPO3 Exception 1329233627 

TYPO3 Exception 1329233747 

TYPO3 Exception 1329289436 

TYPO3 Exception 1329644451 

TYPO3 Exception 1329647780 

Object with identifier "..." does not exist in storage 

Possible Causes:

  • the folder has been renamed

Error was then triggered when adding an image.

Possible Solutions:

  • Logout and Login again.
  • Reindex the file storage.
  • Clear user session data.

TYPO3 Exception 1329765518 

TYPO3 Exception 1329821478 

TYPO3 Exception 1329821479 

TYPO3 Exception 1329821480 

TYPO3 Exception 1329821481 

TYPO3 Exception 1329821482 

TYPO3 Exception 1329821483 

TYPO3 Exception 1329821484 

TYPO3 Exception 1329821485 

You are not allowed to access the given folder 

This exception can occur due to at least three reasons:

  • Bug #51747 (https://forge.typo3.org/issues/51747) in TYPO3 6.1.4
  • a folder in typo3temp or fileadmin that actually is write-protected
  • The folder isn't write-protected but completely missing.

Possible missing folders are

  • typo3temp/_processed\_
  • typo3temp/_migrated\_
  • fileadmin/_processed\_
  • fileadmin/_migrated\_

Known issue, see 43484: TYPO3 Core - Extension Manager only shows error message "File has been deleted."

TYPO3 Exception 1329821486 

TYPO3 Exception 1329821487 

TYPO3 Exception 1329821488 

TYPO3 Exception 1329831691 

TYPO3 Exception 1329836110 

TYPO3 Exception 1329850997 

TYPO3 Exception 1330119451 

TYPO3 Exception 1330119452 

TYPO3 Exception 1330119453 

TYPO3 Exception 1330120649 

TYPO3 Exception 1330121088 

TYPO3 Exception 1330121089 

TYPO3 Exception 1330121117 

TYPO3 Exception 1330262731 

TYPO3 Exception 1330293778 

TYPO3 Exception 1331135889 

TYPO3 Exception 1331715956 

TYPO3 Exception 1332155239 

TYPO3 Exception 1333650506 

No settings detected 

Try the following:

  • Create a TypoScript template and set the root-flag on the first page in the rootline.
  • Check if TypoScript "module" has not been unset.

TYPO3 Exception 1333754332 

TYPO3 Exception 1333754461 

TYPO3 Exception 1333754473 

TYPO3 Exception 1333754514 

TYPO3 Exception 1333754533 

TYPO3 Exception 1333754565 

TYPO3 Exception 1333754629 

TYPO3 Exception 1333754714 

TYPO3 Exception 1333754854 

TYPO3 Exception 1333754878 

TYPO3 Exception 1333754904 

TYPO3 Exception 1333754925 

TYPO3 Exception 1333754941 

TYPO3 Exception 1333754962 

TYPO3 Exception 1334072223 

TYPO3 Exception 1334160746 

TYPO3 Exception 1334426097 

TYPO3 Exception 1334426098 

TYPO3 Exception 1334426297 

TYPO3 Exception 1334426698 

TYPO3 Exception 1334427099 

Folder for file mount "..." does not exist. 

If the folder mentioned does not exist, create it. If you want to delete the folder, make sure to delete the file mount first.

TYPO3 Exception 1334433342 

TYPO3 Exception 1334701880 

TYPO3 Exception 1334736164 

TYPO3 Exception 1334756734 

TYPO3 Exception 1334756735 

TYPO3 Exception 1334756736 

TYPO3 Exception 1334756737 

The temporary cache file "..." could not be written. 

  • Check your quota.
  • Check if filesystem is full.
  • Check if the filesystem permissions are correct.

Troubleshooting: Log on to the console or ftp as the user that runs php and try to create the file. Add some text to the file so it has more than 0 bytes.

The solution was to grant owner rights for the directory: typo3conf, typo3temp, fileadmin and uploads to PHP-User. You can also check permissions with the TYPO3 install tool.

The problem can also occur when there is not enough space on hard disk. Try to expand the hard disk drive or delete some unnecessary files.

TYPO3 Exception 1334756877 

TYPO3 Exception 1334756878 

TYPO3 Exception 1334756879 

TYPO3 Exception 1334756880 

TYPO3 Exception 1334756960 

TYPO3 Exception 1334756961 

TYPO3 Exception 1334841320 

TYPO3 Exception 1334841321 

TYPO3 Exception 1335436551 

TYPO3 Exception 1335980069 

TYPO3 Exception 1336051942 

TYPO3 Exception 1336159604 

TYPO3 Exception 1336756850 

TYPO3 Exception 1337280415 

TYPO3 Exception 1337280416 

TYPO3 Exception 1337280417 

The extension install path "%s" was no directory! 

Problem occurs when extension size is more than post_max_size (php.ini). Just fix post_max_size and restart webserver.

TYPO3 Internals: Actually error should be reported at \TYPO3\CMS\Extensionmanager\Controller\UploadExtensionFileController::extractAction if $_FILES['tx_extensionmanager_tools_extensionmanagerextensionmanager'] is null.

TYPO3 Exception 1337280418 

TYPO3 Exception 1337334849 

TYPO3 Exception 1338810870 

TYPO3 Exception 1338996122 

Package "..." is already registered. 

Accidental double install 

When installing extensions twice (for example by inadvertently using a copied folder) this exception might occur. To get rid of it again, remove the extension from the typo3conf/PackageStates.php manually.

Duplicate composer.json package name:

Another package uses the same name in its composer.json file. Even if composer mode is not enabled and the composer file is just copied, it will cause the TYPO3 Package Manager to throw the correct exception. This may happen if you copy an extension, e.g. from typo3conf/ext/acme to typo3conf/ext/acme.old. Just search the filesystem for any other instances of the same package name and rename one of them.

TYPO3 Exception 1338996142 

TYPO3 Exception 1339079804 

TYPO3 Exception 1339163922 

TYPO3 Exception 1340559079 

TYPO3 Exception 1341151261 

Columns configuration file not found 

EXT:ad_google_maps: What did I do prior to experiencing the problem? 

This error occurred using TYPO3 6.1

After installation of an extension (ad_google_maps) in the extension manager (EM) the error message appeared whenever I opened a frontend or backend page.

Apparently this happened to other people with the same extension. They reported the same error in a (German) board: Thread one, Thread two

Reason 

In ext_tables.php dynamicConfigFile uses a relative path, but \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::loadNewTcaColumnsConfigFiles() expects to get an absolute path.

Solution (patch) 

Replace the call of extRelPath() with extPath() for all dynamicConfigFile-entries in the ext_tables.php

Solution (uninstall) 

  1. Edit typo3conf/LocalConfiguration.php and remove the extension from all lists.
  2. Open the install tool in your browser: your-typo3-installation.com/typo3/install
  3. Use the database analyzer to fix the problem: Click the 'Compare' link and see what the install tool suggests to do.

TYPO3 Exception 1341397767 

TYPO3 Exception 1341397869 

TYPO3 Exception 1341406194 

TYPO3 Exception 1341406402 

TYPO3 Exception 1341406846 

TYPO3 Exception 1341505305 

TYPO3 Exception 1341571604 

TYPO3 Exception 1341826168 

TYPO3 Exception 1342294986 

TYPO3 Exception 1342294987 

TYPO3 Exception 1342345486 

TYPO3 Exception 1342345487 

TYPO3 Exception 1342348167 

TYPO3 Exception 1342432101 

"..." was requested to be downloaded in different versions 

This happens if extension A requires extension B in version X and extension C requires extension B in version Y. Check if there is a compatible combination of A and B available.

TYPO3 Exception 1342432103 

TYPO3 Exception 1342432104 

TYPO3 Exception 1342554622 

TYPO3 Exception 1342635016 

Could not retrieve extension hash file from remote server. 

ISSUE

This usually occurs with a fresh installation of TYPO3 6.2.4, right after the first login to the backend of the newly installed system, but can also occur with an existing installation. It often happens when downloading the preconfigured distributions in the Extension Manager.

POSSIBLE SOLUTION

php.ini (or vhost configuration)

allow_url_fopen = On
max_execution_time = 300
Copied!

TYPO3 Exception 1342635378 

TYPO3 Exception 1342635425 

Could not access remote resource "..." 

If this error comes directly after installation, activate cUrl support in Install-Tool.

[SYS][curlUse] = 1
Copied!

If you use a local XAMPP Installation and the error still occurs with cUrl, than it's maybe a problem with the certificate. The problem is cUrl quit with this message "SSL certificate problem: unable to get local issuer certificate".

TYPO3 Exception 1342639555 

TYPO3 Exception 1342640390 

TYPO3 Exception 1342640540 

TYPO3 Exception 1342640663 

TYPO3 Exception 1342640689 

TYPO3 Exception 1342640703 

TYPO3 Exception 1342640820 

TYPO3 Exception 1342640893 

TYPO3 Exception 1342641009 

TYPO3 Exception 1342641010 

TYPO3 Exception 1342641011 

TYPO3 Exception 1342858852 

TYPO3 Exception 1342858853 

TYPO3 Exception 1342859339 

TYPO3 Exception 1342859463 

TYPO3 Exception 1342859489 

TYPO3 Exception 1342859505 

TYPO3 Exception 1342864081 

TYPO3 Exception 1342864309 

TYPO3 Exception 1342864310 

TYPO3 Exception 1342864311 

TYPO3 Exception 1342864339 

TYPO3 Exception 1342874433 

TYPO3 Exception 1342875724 

TYPO3 Exception 1342895975 

TYPO3 Exception 1342895976 

TYPO3 Exception 1343048718 

TYPO3 Exception 1343331520 

TYPO3 Exception 1343331521 

TYPO3 Exception 1343331522 

TYPO3 Exception 1343331523 

TYPO3 Exception 1343331524 

TYPO3 Exception 1343462896 

TYPO3 Exception 1343464100 

Error message 

Broken rootline. Mountpoint parameter does not match the actual rootline. mount_pid (xxx) does not match page uid (yyy).

Possible solutions 

Check your realurl data 

When I encountered this problem the reason was an invalid entry in the ID to path mapping of realurl.

The problematic data was inside the page with the UID shown in yyy in the above example of the error message.

I cleared the ID to path mappings in the yyy page and the problem disappeared.

TYPO3 Exception 1343464101 

Broken rootline. Could not resolve page with uid "..." 

  • Workspace page preview link is opened to a page that has not been published yet (only exists in workspace)
  • Page has no connection to a parent anymore (orphan)

TYPO3 Exception 1343464103 

TYPO3 Exception 1343486350 

TYPO3 Exception 1343568853 

TYPO3 Exception 1343589451 

Could not fetch page data for uid "...". 

Error in frontend when using for example <f:link.page> ViewHelper because the pageUid was a deleted page. Make sure the target of the link is accessible.

TYPO3 Exception 1343589452 

TYPO3 Exception 1343593398 

TYPO3 Exception 1344375003 

No settings detected. This module can not work then. 

As the message states:

This usually happens if there is no frontend TypoScript template with root flag set. Please create a frontend page with a TypoScript root template.

So you need to create a template on your root page that has the box "rootlevel" under options ticked.

Things to note 

  • Make sure the root template gets loaded from the root page of your page tree. (Even if this is only shortcut to somewhere else.)
  • Make sure non of the basis templates loaded by the root template clears Setup/Config.

TYPO3 Exception 1344685036 

TYPO3 Exception 1344687432 

TYPO3 Exception 1344687436 

TYPO3 Exception 1344691048 

TYPO3 Exception 1344691049 

TYPO3 Exception 1344761814 

TYPO3 Exception 1344761938 

TYPO3 Exception 1344761991 

TYPO3 Exception 1344766387 

TYPO3 Exception 1344888548 

TYPO3 Exception 1345036334 

TYPO3 Exception 1345036335 

[TYPO3 12] - [17th December 2024] 

Situation 

Backend and Frontend only show this exception with the detail: Could not write log record to log file.

Solution 

  1. If the Install Tool can be opened, go to Admin Tools > Environment > Directory Status and check the directory status.
  2. Check if typo3temp/var/log and all files therein are writable for TYPO3

# If the disk is full, you might want to switch to log rotation. #. As a last resort: Delete the files in typo3temp/var/log. Make a copy first.

TYPO3 Exception 1345036336 

TYPO3 Exception 1345036337 

TYPO3 Exception 1345304560 

TYPO3 Exception 1345304561 

TYPO3 Exception 1345368105 

TYPO3 Exception 1345368106 

TYPO3 Exception 1345736517 

TYPO3 Exception 1345736785 

TYPO3 Exception 1346323822 

$localConfigurationFile is not writable. 

Make sure the file LocalConfiguration.php and the folder typo3conf is writeable for at least the webserver.

-rw-rw-r-- LocalConfiguration.php
chmod g+w LocalConfiguration.php
Copied!

TYPO3 Exception 1346336675 

TYPO3 Exception 1346364362 

TYPO3 Exception 1346510477 

TYPO3 Exception 1346577887 

TYPO3 Exception 1347135544 

TYPO3 Exception 1347135545 

TYPO3 Exception 1347135546 

$haystack can not be interpreted as string 

Most often, the reason for this error is a wrongly defined TCA column. For example something like this (duplicate nesting of items):

'items' => [
   'items' => [
       ['noRotation', 0],
       ['oneQuarter', 1],
       ['halfCircle', 2],
       ['threeQuarter', 3],
  ],
],
Copied!

TYPO3 Exception 1347135547 

TYPO3 Exception 1348053245 

TYPO3 Exception 1348053246 

TYPO3 Exception 1348146451 

Invalid composer manifest in package path: $packagePath 

Please check the validity of the file composer.json in the extension mentioned in the error message.

TYPO3 Exception 1349272276 

TYPO3 Exception 1349272337 

TYPO3 Exception 1349276894 

Could not find any folder to be displayed. 

This error most likely occurs because the current backend-user does not have access to any file mounts. Check that a file mount exists and that the current user has access to it - either through the group(s) or through the user directly.

TYPO3 Exception 1349340620 

TYPO3 Exception 1349692692 

TYPO3 Exception 1349776393 

TYPO3 Exception 1349868540 

No composer manifest file found at .../composer.json. 

  • check whether there is a composer.json file in that location
  • check whether the file is accessible by the web server (file permissions)

TYPO3 Exception 1350514301 

TYPO3 Exception 1350570621 

Cannot process task of type "..." 

The LocalImageProcessor can currently handle tasks of type Image named Preview or CropScaleMask - all other task type/name combinations will produce this error.

TYPO3 Exception 1350582054 

Cannot update original file! 

TYPO3 Exception 1350742864 

TYPO3 Exception 1350891642 

TYPO3 Exception 1351584844 

An argument "key" or "id" has to be provided 

Check your fluid template for empty keys or syntax errors in <f:translate> tags. Example:

Wrong:

<f:translate key="{openFeed}"/>
Copied!

Right:

<f:translate key="openFeed"/>
Copied!

TYPO3 Exception 1352320649 

TYPO3 Exception 1352549235 

TYPO3 Exception 1352565336 

TYPO3 Exception 1352566904 

TYPO3 Exception 1352566905 

TYPO3 Exception 1353170711 

The ColumnMap for property "..." of class "..." is missing. 

You encounter this Exception because you try to fetch objects from the database which most probably do not have a TCA configuration.

Without the TCA configuration Extbase is unable to build the ColumnMap correctly.

So please be sure you have a working TCA configuration by using the Configuration module in the backend.

TYPO3 Exception 1353170925 

The relation information for property "..." of class "..." is missing. 

If you have a property in a class SomeModelYY which has another class as type

/**
* @var TX\ext_key\Domain\Model\SomeOtherModelZZ
*/
protected $propertyXX;
Copied!

the object will be populated by extbase without any other configuration.

But to make queries like

$query->like("propertyXX.someproperty", '%foo%')
Copied!

work, you still have to declare a foreign_table in your TCA.

Also make sure you have the properties with corresponding getters and setters in your model.

TYPO3 Exception 1353401352 

TYPO3 Exception 1353401835 

TYPO3 Exception 1355142232 

The ColumnMap for property "..." of class "..." is missing 

What this simply says is that you don't have such a field/property with that spelling in your model for the table you are querying. Perhaps you are using the exact spelling found in your table. You should instead use the spelling in your model. Cross-check that you have such a field in your model.

TYPO3 Exception 1355155913 

TYPO3 Exception 1356356009 

Exception while parsing composer file /.../composer.json 

Most likely you have an error in the mentioned composer.json file. Check the mentioned composer.json for errors.

TYPO3 Exception 1357064326 

TYPO3 Exception 1357064437 

TYPO3 Exception 1357811441 

TYPO3 Exception 1358349150 

TYPO3 Exception 1359206803 

TYPO3 Exception 1359747976 

TYPO3 Exception 1359748085 

TYPO3 Exception 1359748132 

TYPO3 Exception 1359900487 

TYPO3 Exception 1359987599 

TYPO3 Exception 1360403545 

TYPO3 Exception 1360414192 

TYPO3 Exception 1360414193 

TYPO3 Exception 1360500126 

TYPO3 Exception 1360684914 

TYPO3 Exception 1360928582 

TYPO3 Exception 1361461834 

The storage "folder" looks currently off-line. Check the storage configuration if you think this is an error 

The folder needs to exist and be readable and writable. After creating the folder, edit the storage configuration record and set it to "online".

TYPO3 Exception 1361915115 

TYPO3 Exception 1361915206 

TYPO3 Exception 1361915596 

TYPO3 Exception 1361915610 

TYPO3 Exception 1362602559 

TYPO3 Exception 1362602560 

TYPO3 Exception 1363116592 

TYPO3 Exception 1363117435 

TYPO3 Exception 1363117491 

TYPO3 Exception 1363117507 

TYPO3 Exception 1363117531 

TYPO3 Exception 1363278130 

TYPO3 Exception 1363300030 

TYPO3 Exception 1363300072 

TYPO3 Exception 1363429303 

TYPO3 Exception 1363778104 

There is no @var annotation for property "..." in class "..." 

TYPO3 v12.4 - 21.03.2025 

For each property of a domain model Extbase needs to determine the type. It is prefered to use a real PHP type:

 class UserData extends AbstractEntity
 {
-    public $frontendUser = null;
+    public ?FrontendUser $frontendUser = null;
     //...
 }
Copied!

If using typed properties is not and option for some reason, you can use the @var annotation instead:

 class UserData extends AbstractEntity
 {
+    /** @var ?FrontendUser $frontendUser*/
     public $frontendUser = null;
     //...
 }
Copied!

Before TYPO3 v10 

If you inject a service, or whatever other class in a model:

Please be sure you implement the Singleton interface in the service.

Example:

I have a Domain Model under \CustomDomainModel.php, in which I do:

/**
* myService # optional property name as this is not really a property, it does not make much sense to name it
*
* @var \Custom\Services\MyService
* @inject
* @lazy
*/

protected $myService;
Copied!

Then I need to make sure MyService class is declared like this:

class MyService extends \TYPO3\CMS\Extbase\Mvc\Controller\ActionController implements \TYPO3\CMS\Core\SingletonInterface
Copied!

TYPO3 Exception 1364205166 

TYPO3 Exception 1364205170 

TYPO3 Exception 1364205235 

TYPO3 Exception 1364205377 

TYPO3 Exception 1364836026 

TYPO3 Exception 1365167380 

TYPO3 Exception 1365429656 

TYPO3 Fatal Error: Extension key "..." is NOT loaded! 

TYPO3 >= 10 LTS 

Starting with TYPO3 10 LTS the variable $_EXTKEY isn't filled with the extension key anymore. Solution: use the hardcoded extension key within ext_tables.php and ext_localconf.php.

See this page for further details: best-practices-for-ext-tables-php-and-ext-localconf-php

However, notice that $_EXTKEY must be used in ext_emconf.php.

TYPO3 < 10 LTS 

This error might come up, if you delete the files of a Extension from the Extension Path (typo3conf/ext), which is still activated in TYPO3.

At first you should check, if there is a typo in the name of the extension key.

To solve this error, follow these steps:

(Info: These steps will remove the installed extensions from the "loaded Extension list" and TYPO3 cache.)

1) remove the Extension from the loaded extension part in typo3conf/LocalConfiguration.php - [['EXT']['extConf']['*your_extension_key*']]

2) remove either all files from typo3temp-folder, or at least the files in typo3temp/var/Cache/Code/cache_core named ext_tables.php and ext_localconf.php. In former versions of TYPO3 the folder name is typo3temp/var/Cache/Code/cache_core.

The error should be gone by now and the extension is removed. Reinstall the extension if needed.

Additionally, this error might come up if you re-structure your TCA files to fit into the new 6.2 structure. If you try to use $_EXTKEY in the Configuration/TCA/tablename.php files (for paths with extPath($_EXTKEY)), then $_EXTKEY will be empty and thus TYPO3 looks for the extension ' '. Solution is to replace $_EXTKEY by the extension key of the extension.

If you encounter this error during an upgrade to 6.2, you might check your LocalConfiguration.php for the right order of extensions in the deprecated extListArray. (e.g. EXT:formhandler has to be included before EXT:formhandler_subscription.)

TYPO3 Exception 1365429673 

Extension key "..." is NOT loaded! 

Disable the extension manually 

Open typo3conf/PackageStates.php, look up the extension key and change

[
   // ...
   'state' => 'active'
   // ...
]
Copied!

to

[
   // ...
   'state' => 'inactive'
   // ...
]
Copied!

You might also need to clear the PHP code cache in typo3temp:

$ rm -rf typo3temp/*
Copied!

Observations 

Using a Vagrant with TYPO3 6.2beta6 we had this problem

vagrant reload --provision did not help.

Frontend is working fine but you can't login to the backend!

My solution: You can check in the TYPO3 Database Table sys_log which exception is thrown. Now find the offending extension in LocalConfiguration.php and disable it (see above).

Mixed composer/classic installation 

This could also happen when you attempt to unpack a .tar.gz packed version of TYPO3 and run it's installer over an previously composer-style-installed instance. The install-tool then breaks the PackageStates.php, trying to recover the old version did help in my case. For me the extension cms was affected. This happens during an update from TYPO3 6.2 to 7.1 or later. You must search for the following array part or add it to your file PackageStates.php:

'cms' =>
array (
  'manifestPath' => ,
  'composerName' => 'typo3/cms',
  'state' => 'active',
  'packagePath' => 'typo3/sysext/cms/',
  'classesPath' => 'Classes/',
  'suggestions' =>
  array (
  ),
),
Copied!

back from TYPO3 7.6.x 

The following error message is shown when you downgrade from TYPO3 7.6 to 6.2.

TYPO3 Fatal Error: Extension key "cms" is NOT loaded
Copied!

You must have a backup copy of the file typo3conf/PackageStates.php . Restore a file PackageStates.php which is compatible under TYPO3 6.2.

TYPO3 Exception 1365513336 

TYPO3 Exception 1365776838 

TYPO3 Exception 1365779762 

Missing storage page ids 

This error appears because you set some specific query settings, like $querySettings->setIgnoreEnableFields(true) and use generic TYPO3QuerySettings. Because this is a generic object, it knows nothing about the plugin context so, instead of using a generic object, use a $this->createQuery()->getQuerySettings() and then the pid set in FlexForm or in TypoScript will be set.

This generates an error:

public function initializeObject()
{
    /** @var \TYPO3\CMS\Extbase\Persistence\Generic\TYPO3QuerySettings $querySettings */
    $querySettings = $this->objectManager->get(\TYPO3\CMS\Extbase\Persistence\Generic\TYPO3QuerySettings::class);
    $querySettings->setIgnoreEnableFields(true);
    $querySettings->setEnableFieldsToBeIgnored(['fe_group']);
    $this->setDefaultQuerySettings($querySettings);
}

Copied!

This one is ok:

public function initializeObject()
{
    /** @var \TYPO3\CMS\Extbase\Persistence\Generic\TYPO3QuerySettings $querySettings */
    $querySettings = $this->createQuery()->getQuerySettings();
    $querySettings->setIgnoreEnableFields(true);
    $querySettings->setEnableFieldsToBeIgnored(['fe_group']);
    $this->setDefaultQuerySettings($querySettings);
}
Copied!

TYPO3 Exception 1365799920 

TYPO3 12.0-dev - 14.08.22 

Installation Overview 

TYPO3 12.0-dev with blog_example extension

The Issue 

On front end call to the extensions plugin

(1/1) #1365799920 TYPO3\CMS\Extbase\Validation\Exception\NoSuchValidatorException
Validator class FriendsOfTYPO3\ExtbaseExample\Domain\Validator\BlogValidator does not exist
Copied!

Solution 

The fully-qualified class name of the validator in the annotation was wrong

Changed annotation from

/**
* Updates an existing blog
*
* @Validate(param="blog", validator="FriendsOfTYPO3\ExtbaseExample\Domain\Validator\BlogValidator")
* @throws NoBlogAdminAccessException
*/
public function updateAction(Blog $blog): ResponseInterface
Copied!

to

/**
* Updates an existing blog
*
* @Validate(param="blog", validator="FriendsOfTYPO3\BlogExample\Domain\Validator\BlogValidator")
* @throws NoBlogAdminAccessException
*/
public function updateAction(Blog $blog): ResponseInterface
Copied!

TYPO3 Exception 1366139176 

TYPO3 Exception 1366140117 

TYPO3 Exception 1366141329 

TYPO3 Exception 1366222203 

TYPO3 Exception 1366222204 

TYPO3 Exception 1366222205 

TYPO3 Exception 1366222206 

TYPO3 Exception 1366222207 

TYPO3 Exception 1366226639 

TYPO3 Exception 1366398198 

TYPO3 Exception 1366493602 

TYPO3 Exception 1366493603 

TYPO3 Exception 1366493604 

TYPO3 Exception 1366535827 

TYPO3 Exception 1366711745 

TYPO3 Exception 1366711933 

TYPO3 Exception 1366740091 

TYPO3 Exception 1366744035 

Permission on "..." are already ok 

Happens if fixPermission is called on an object with correct permissions. If you encounter this error without calling fixPermission yourself you can most likely safely ignore this.

TYPO3 Exception 1366919440 

TYPO3 Exception 1366919442 

TYPO3 Exception 1366927513 

TYPO3 Exception 1367048077 

TYPO3 Exception 1367056363 

TYPO3 Exception 1367060201 

TYPO3 Exception 1367060202 

TYPO3 Exception 1368112037 

TYPO3 Exception 1369122038 

TYPO3 Exception 1369161225 

TYPO3 Exception 1369325619 

TYPO3 Exception 1369326592 

TYPO3 Exception 1369326593 

TYPO3 Exception 1369345838 

TYPO3 Exception 1369474308 

TYPO3 Exception 1369474309 

TYPO3 Exception 1369563246 

TYPO3 Exception 1369563247 

TYPO3 Exception 1369563248 

TYPO3 Exception 1370419654 

TYPO3 Exception 1370878522 

TYPO3 Exception 1371035200 

TYPO3 Exception 1371243449 

TYPO3 Exception 1371243450 

TYPO3 Exception 1371303903 

TYPO3 Exception 1371410113 

TYPO3 Exception 1371466663 

TYPO3 Exception 1371484524 

TYPO3 Exception 1371757718 

TYPO3 Exception 1371757719 

TYPO3 Exception 1371757720 

TYPO3 Exception 1371758436 

TYPO3 Exception 1372458274 

TYPO3 Exception 1373727309 

TYPO3 Exception 1373727310 

TYPO3 Exception 1373727311 

TYPO3 Exception 1373727329 

TYPO3 Exception 1374309323 

TYPO3 Exception 1375889830 

You are not allowed to access files outside your storages 

This exception is thrown in FAL whenever you are trying to access a file outside of your configured storages. The default storage is fileadmin (see https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Fal/Index.html).

In backend modules this exception will occur if files in legacy folders/storages are accessed, which is prohibited due to security reasons (see https://review.typo3.org/#/c/23608/).

Solution 

Either try to access files in a valid storage instead (like fileadmin/_temp_/ instead of (uploads/not/working) or add the desired folder to a storage configuration.

TYPO3 Exception 1375889832 

TYPO3 Exception 1375889834 

TYPO3 Exception 1375889838 

TYPO3 Exception 1375889840 

TYPO3 Exception 1375955429 

TYPO3 Exception 1375955430 

TYPO3 Exception 1375955684 

You are not allowed to access the given folder 

This exception occurs when file action permissions are not correct. It may occur after an upgrade due to security bulletin core-sa-2013-003

  • …and not following the given advices (clear cache, deleting the complete typo3temp/Cache folder, set storage file permissions) - in this case follow the instructions in the bulletin
  • …and deleting the complete typo3temp folder → in this case see bug 51747, manually creating the folder typo3temp/_processed_ seems to fix the problem for most people.

Exception when calling the language module 

If you encounter this exception when calling the language module in 6.1.4 => try to update to 6.1.5 or later.

Exception Scheduler calling: File Abstraction Layer: Indexing job (scheduler) 

Check that user _cli_scheduler has File Mounts to all storages on root level /

This also applies to indexing content with ke_search.

Exception when calling search in the file list module 

If this occurs as editor (not admin), you are using TYPO3 9.5 and you are directly on the top level directory of a file mount, it may be due to this bug: https://forge.typo3.org/issues/88175

Exception when calling the file list module 

You may have switched your file storage to offline. This may happen, if you create a non-public file storage without a _processed_ sub-folder and if you then switch to file list. The _processed_ sub-folder will be created by TYPO3, but the exception is not caught and the storage is set to offline.

Solution: Edit your File Storage record -> Tab Access -> Is online? [x]

Then switch back to the file list and either reload the file list frame or logout/relogin.

Exception after viewing the TYPO3 frontend in a browser 

The auto-created fileadmin folder had been put offline. Re-enabling the folder fixes the issue.

Exception, when trying to select a file in tce_forms 

Look for something like this in the Page / User / Group TS and prefix the folder with the correct storage

# fails
options.folderTree.altElementBrowserMountPoints = assets
# works, as sub-folder of storage 1, which is by default the :file:`fileadmin` folder
options.folderTree.altElementBrowserMountPoints = 1:assets
Copied!

Exception after cloning a 6.2 site when calling the file list module 

The fileadmin folder had been (deliberately) replaced by another one. Then, the page tree column displayed this error - only that 2nd column. In the third column, the files were displayed as usual. None of the above helped, but truncating all sys_file tables did. In my case, that was feasible.

Exception when deleting file as non admin user 

If sys extension recycler is enabled, make sure that there is a _recycler_ folder accessible for the user.

TYPO3 Exception 1376084316 

TYPO3 Exception 1376579070 

TYPO3 Exception 1376583188 

TYPO3 Exception 1376657142 

TYPO3 Exception 1376657189 

TYPO3 Exception 1376657199 

TYPO3 Exception 1376657210 

TYPO3 Exception 1376657277 

TYPO3 Exception 1376683066 

The slot method "..." returned a different number (...) of arguments, than it received (...). 

This happens if a signal slot method is wrongly used.

Example 

The signal is called with a parameter [$csvRow]:

$this->signalSlotDispatcher->dispatch(__CLASS__, 'beforeSetCsvRow', [$csvRow]);
Copied!

However the according slot method returns only $csvRow

class DatabaseRecordListSlots
{
  public function addValuesToCsvRow($csvRow)
  {
    $csvRow['new'] = 128;
    return $csvRow;
  }
}
Copied!

The slot must return the same array of arguments as the dispatcher signal has used before.

class DatabaseRecordListSlots
{
  public function addValuesToCsvRow($csvRow)
  {
    $csvRow['new'] = 128;
    return [$csvRow];
  }
}
Copied!

TYPO3 Exception 1376683067 

TYPO3 Exception 1376739702 

TYPO3 Exception 1376745645 

TYPO3 Exception 1376746261 

TYPO3 Exception 1376746262 

TYPO3 Exception 1376826527 

TYPO3 Exception 1376833554 

TYPO3 Exception 1376992145 

TYPO3 Exception 1377006651 

TYPO3 Exception 1377006652 

TYPO3 Exception 1377006653 

TYPO3 Exception 1377006654 

TYPO3 Exception 1377006655 

TYPO3 Exception 1377006656 

TYPO3 Exception 1377095807 

TYPO3 Exception 1377600104 

TYPO3 Exception 1377600978 

TYPO3 Exception 1377611168 

TYPO3 Exception 1377620117 

TYPO3 Exception 1377625537 

TYPO3 Exception 1377625645 

TYPO3 Exception 1377625646 

TYPO3 Exception 1377777624 

TYPO3 Exception 1377777629 

TYPO3 Exception 1377777635 

TYPO3 Exception 1377778045 

TYPO3 Exception 1377778049 

TYPO3 Exception 1377778702 

TYPO3 Exception 1377778916 

You are not allowed to delete a file with extension "..." 

Deleting a file with the mentioned extension is prohibited in this installation. If you have access to the TYPO3 configuration, you may edit the value for $GLOBALS['TYPO3_CONF_VARS']['BE']['fileDenyPattern'] in the Install Tool.

TYPO3 Exception 1377779039 

TYPO3 Exception 1377779111 

TYPO3 Exception 1377779423 

TYPO3 Exception 1377977856 

TYPO3 Exception 1377977857 

TYPO3 Exception 1377977858 

TYPO3 Exception 1378132239 

TYPO3 Exception 1378243279 

TYPO3 Exception 1378457171 

TYPO3 Exception 1378644593 

TYPO3 Exception 1378644821 

TYPO3 Exception 1378645039 

TYPO3 Exception 1378645155 

TYPO3 Exception 1378918410 

TYPO3 Exception 1378976970 

TYPO3 Exception 1379024938 

TYPO3 Exception 1379502242 

TYPO3 Exception 1379579812 

TYPO3 Exception 1379981890 

Unsupported validation option(s) found: "..." 

Possible issue is missing options configuration 

One possible issue can be, that the Validator doesn't follow the API. The validator needs to configure the $supportedOptions property like:

class StringLengthValidator extends AbstractValidator {
/**
 * @var array
 */
 protected $supportedOptions = [
    'minimum' => [0, 'minimum length for a valid string', 'integer'],
    'maximum' => [php_int_max, 'maximum length for a valid string', 'integer']
 ];
Copied!

TYPO3 Exception 1379981891 

TYPO3 Exception 1380007853 

TYPO3 Exception 1380017853 

TYPO3 Exception 1380364361 

TYPO3 Exception 1380364362 

TYPO3 Exception 1380364363 

TYPO3 Exception 1380485700 

TYPO3 Exception 1380546061 

TYPO3 Exception 1380556245 

TYPO3 Exception 1380556246 

TYPO3 Exception 1380556247 

TYPO3 Exception 1380581244 

Redirect loop aborted. 

#1380581244: Redirect loop aborted. If this message is shown again after a reload, your setup is so weird that the install tool is unable to handle it. Please make sure to remove the "install[redirectCount]" parameter from your request or restart the install tool from the backend navigation.

The error happened after an upgrade of TYPO3 6.2 via 7.6 to 8.7. The reason was wrong entries in AdditionalConf.php:

\TYPO3\CMS\Core\Configuration\ConfigurationManager::setLocalConfigurationValueByPath('DB/database', 'DBNAME');
\TYPO3\CMS\Core\Configuration\ConfigurationManager::setLocalConfigurationValueByPath('DB/username', 'USERNAME');
\TYPO3\CMS\Core\Configuration\ConfigurationManager::setLocalConfigurationValueByPath('DB/password', 'PASSWORD');
Copied!

After changing the entries to the following text, everything worked as expected.

$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['dbname'] = 'DBNAME';
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['password'] = 'USERNAME';
$GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['user']     = 'PASSWORD';
Copied!

If the error appears on 7.6, check if the port is set.

TYPO3 Exception 1380897593 

TYPO3 Exception 1380898792 

TYPO3 Exception 1380905851 

Major/Minor release "..." not found in version matrix. 

see https://forge.typo3.org/issues/67848

TYPO3 Exception 1380905852 

TYPO3 Exception 1380905853 

TYPO3 Exception 1380909029 

TYPO3 Exception 1380975303 

TYPO3 Exception 1381059600 

TYPO3 Exception 1381164687 

TYPO3 Exception 1381263173 

TYPO3 Exception 1381269811 

TYPO3 Exception 1381507733 

TYPO3 Exception 1381512753 

TYPO3 Exception 1381512761 

Invalid value "..." for enumeration "..." in v12 

Invalid value "-1" for enumeration "TYPO3CMSCoreVersioningVersionState" 

The value -1 is no longer valid for VersionState. The corresponding rows should have been updated within the database by an Upgrade Wizard "WorkspaceNewPlaceholderRemovalMigration". More information is available at: https://forge.typo3.org/issues/99401#note-3

TYPO3 6.2.x and higher (after update from 6.1 or lower) 

Error occurred in an extension after migration 6.1 -> 6.2 due to wrong (invalid) field data types in the TCA ('type' => 'date',) -> 'date' is an invalid type. It seems, v6.1 didn't care very much about invalid types, but 6.2 does. Changing the datatype to 'type' => 'input', 'eval' => 'datetime' solved the problem.

After Upgrade to v11 TCA config internal_type => 'file_reference' make problem 

After an update to TYPO3 v11 from a very old v6.2 installation, the TCA config for TCA type group is deprecated. You cannot use internal_type => 'file_reference' or internal_type => 'file'. Migrate your old TCA to new one using type inline as fileReferences.

TYPO3 Exception 1381512797 

TYPO3 Exception 1381512807 

TYPO3 Exception 1381512859 

TYPO3 Exception 1381559376 

TYPO3 Exception 1381570091 

TYPO3 Exception 1381570997 

A file needs to reside in a Storage 

You are trying to access a file for which no storage information can be found.

TYPO3 Exception 1381590731 

Metadata can only be retrieved for indexed files. UID: "..." 

Occurrence in TYPO3 6.2 LTS with tx_news 

Missing MySQL Tables sys_file and sys_file_processedfile due to MySQL version incompatibility.

Cause in TYPO3 6.2 LTS Beta3 

Copy / Paste images in fileadmin doesn't index the images

Quickfix in TYPO3 6.2 LTS Beta3:

Edit the images you've pasted and save them. This is a quickfix, not a solution

This bug still occurs in 6.2beta5 if you forgot to run the Upgrade Wizard.

TYPO3 Exception 1381597628 

TYPO3 Exception 1381597629 

TYPO3 Exception 1381597630 

TYPO3 Exception 1381597631 

TYPO3 Exception 1381609294 

TYPO3 Exception 1381612729 

TYPO3 Exception 1381615295 

TYPO3 Exception 1381768833 

TYPO3 Exception 1381823570 

TYPO3 Exception 1381847136 

Could not determine the current charset of the database. 

Did you update MySQL last time and this exception occurred? First verify if MySQL can check the charsets by running the following SQL query:

SHOW SESSION VARIABLES LIKE 'character_set%';
Copied!

If it shows you an error like Table 'performance_schema.session_variables' doesn't exist you can try to fix it by the console command:

mysql_upgrade -u root -p --force
Copied!

After that, restart mysql.

reference: http://stackoverflow.com/q/31967527/1066240

TYPO3 Exception 1381847779 

TYPO3 Exception 1381922460 

TYPO3 Exception 1381922465 

TYPO3 Exception 1381923089 

TYPO3 Exception 1381960493 

Your dependencies have cycles. That will not work out. Cycles found: "..." 

This happens if you have circular dependencies in your extensions:

Extension A requires B and B requires A. This cannot be resolved automatically, please check and adjust your dependencies.

TYPO3 Exception 1381960494 

TYPO3 Exception 1382006142 

TYPO3 Exception 1382276561 

The package "..." depends on "..." which is not present in the system. 

Solution 1 

Clear system caches

Solution 2 

The cache cannot be cleared, because both the TYPO3 backend and the TYPO3 install tool are not available any more. Open the file typo3conf/PackageStates.php and remove the part which belongs to the extension which requires the missing extension. If everything is finally restored, then you can install this extension again manually.

Solution 3 

If deleting PackageStates.php is no option, try using the typo3cms console to re-install an extension which is already installed. That should fix it.

TYPO3 Exception 1382284105 

You must either specify a string src or a File object. 

This error happens in Fluid if an <img> tag (or a media / image view helper) has an undefined variable in the src parameter.

Example:

<img src="{f:uri.image(image: file)}" title="{file.title}" alt="{file.alternative}" />
Copied!

and "file" is undefined, or not a String or a FileReference.

TYPO3 Exception 1382284106 

TYPO3 Exception 1382351456 

TYPO3 Exception 1382360258 

TYPO3 Exception 1382364019 

TYPO3 Exception 1382364370 

TYPO3 Exception 1382449759 

TYPO3 Exception 1382651858 

TYPO3 Exception 1382687163 

Supplied file object type "..." must be File or FileReference. 

This exception can be thrown when you use a fluid template with an image tag <f:image src="image.jpg"> and the image does not exist! So check your templates for correct image sources before checking models.

TYPO3 Exception 1382867521 

TYPO3 Exception 1384209020 

TYPO3 Exception 1384209021 

TYPO3 Exception 1384209022 

TYPO3 Exception 1384209023 

TYPO3 Exception 1384209025 

TYPO3 Exception 1384268260 

TYPO3 Exception 1384275695 

TYPO3 Exception 1384275696 

TYPO3 Exception 1384275697 

TYPO3 Exception 1384275698 

TYPO3 Exception 1384611413 

No record was found. The "record" or "uid" argument must be specified. 

Case 1: v:page.resources.fal 

This happens when <v:page.resources.fal> is used and the page is not visible (hidden, or start/endtime).

See https://github.com/FluidTYPO3/vhs/issues/1618#issuecomment-579699504

TYPO3 Exception 1385547291 

TYPO3 Exception 1385807526 

TYPO3 Exception 1385811397 

TYPO3 Exception 1387619575 

TYPO3 Exception 1389265726 

TYPO3 Backend not accessed via SSL: TYPO3 Backend is configured to only be accessible through SSL. 

Change the login URL from http:// to https://.

TYPO3 Exception 1389265900 

You are not allowed to access the backend as your IP does not matches the [BE][IPmaskList] setting in the Install Tool. 

Go to the Install Tool and add your IP address in All Configuration ['BE']['IPmaskList'], using comma separation (no semicolon).

See also https://docs.typo3.org/typo3cms/SecurityGuide/GuidelinesIntegrators/GlobalTYPO3Options/Index.html#ipmasklist for more security advice.

TYPO3 Exception 1389606342 

TYPO3 Exception 1389697515 

TYPO3 Exception 1389969623 

TYPO3 Exception 1390290029 

You are trying to use a method on an inaccessible folder. 

Processed directory readonly 

We had this error when listing files in the backend. The source of the problem was that the folder contained image files and the backend wanted to create and save preview images. The processed folder was set to a second file storage whose root directory was readonly. After fixing that permission problem of the second file storage, everything worked again.

TYPO3 11.5 - File storage is offline / not found 

Got to the backend module File > Filelist and check if a file storage is offline. If so right click on it and choose Edit from the context menu. Check the paths or sources that are configured here.

TYPO3 7 

  • accessed files/folders may be missing (check if the do exist)
  • file storage may be out of webroot (try to move the files into a valid file storage)
  • check the same folder in the backend module File->List - maybe some Icons will show you that the folder is not accessible
  • check missing folders in typo3temp
  • If the file storage is readonly (Flag Is writable not set), then you may need to set a Folder for manipulated and temporary images -> This folder may be located in another file storage, which is writeable (eg the non-writable file storage is number 2, a writeable storage is number 1, then set this folder value to 1:/_processed_)

TYPO3 Exception 1390334120 

No cache in the specified group "..." 

This happens if flushCachesInGroup is called with a group that has no caches defined.

Possible Solutions: 

  • If you recently installed new extensions, try uninstalling them and clearing the cache.
  • If you are a developer, check the error message for the groupIdentifier and verify that the cache group exists.

TYPO3 Exception 1390337129 

TYPO3 Exception 1390337130 

TYPO3 Exception 1390913893 

TYPO3 Exception 1390913894 

TYPO3 Exception 1391295611 

TYPO3 Exception 1391295613 

TYPO3 Exception 1391295633 

TYPO3 Exception 1391295643 

TYPO3 Exception 1391295644 

TYPO3 Exception 1391432222 

TYPO3 Exception 1391440658 

TYPO3 Exception 1391894094 

TYPO3 Exception 1392409507 

Invalid form/module token detected. Access Denied. 

The problem is usually caused by an missing security token which protects against CSRF. It can occur in the backend by clicking on an icon, link or using other controls. This problem is usually only backend related but could also occur in the frontend when using frontend editing.

For TYPO3 integrators:

If you encounter this problem with default backend modules included in the TYPO3 distribution you should first check if there is already an error report on https://forge.typo3.org and if this is not the case feel free to create a new bug report.

For developers:

See https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/FormProtection/Index.html

TYPO3 Exception 1392840462 

TYPO3 Exception 1393574895 

TYPO3 Exception 1393614709 

TYPO3 Exception 1393614710 

TYPO3 Exception 1393686550 

TYPO3 Exception 1393883341 

TYPO3 Exception 1393883342 

TYPO3 Exception 1393960943 

TYPO3 Exception 1394099179 

TYPO3 Exception 1394099256 

TYPO3 Exception 1394442417 

TYPO3 Exception 1394453197 

TYPO3 Exception 1394480725 

Could not acquire lock for ClassLoader cache creation. 

see https://forge.typo3.org/issues/59845

Possible Solutions 

  • Clear Cache
  • On setups with shared typo3temp: use a local folder for the cache

TYPO3 Exception 1394620167 

TYPO3 Exception 1394631927 

TYPO3 Exception 1395055513 

TYPO3 Exception 1395140007 

TYPO3 Exception 1395353470 

TYPO3 Exception 1395362539 

TYPO3 Exception 1395614959 

Version number in composer manifest of package "..." is missing or invalid 

This happens in TYPO3 6.2 whenever an extension has a dependency on another extension which contains a file composer.json without any version number (which is actually the best practice).

Simple solution for the time being since composer is not properly supported in TYPO3 6.2 is to delete the corresponding file composer.json or to explicitly set a version number.

TYPO3 Exception 1395710211 

TYPO3 Exception 1396278700 

TYPO3 Exception 1396278734 

TYPO3 Exception 1396302624 

TYPO3 Exception 1396340331 

TYPO3 Exception 1396340332 

TYPO3 Exception 1396340333 

TYPO3 Exception 1396795884 

The current host header value does not match the configured trusted hosts pattern! 

Error displayed during installation of TYPO3 

Usually, when installing a new TYPO3 instance, the system will detect the instance has not been configured yet and will redirect to the installer to proceed with the installation. However, depending on web server configuration, this trusted hosts pattern error may still be thrown and the redirect will not be performed. An easy way to circumvent this is to just manually add the path url typo3/install.php in the browser to directly reach the installer, which will take care of the trusted hosts pattern setting in one of its installer steps.

Error displayed on an existing instance 

You see this error, because the submitted HTTP host-header does not match the trustedHosts configuration. You may want to adjust the trusted host pattern, which is security mechanism to validate the HTTP host-header and prevent host spoofing.

Please read the security advisory »TYPO3-CORE-SA-2014-001« to understand the need for this configuration option.

The trusted host pattern may be set with the Install Tool (Backend > Install Tool > All configuration > Toggle all and find trustedHostsPattern) or by editing /typo3conf/LocalConfiguration.php.

$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']
Copied!

This is a regular expression pattern that matches all allowed hostnames (including their ports) of this TYPO3 installation, or the string "SERVER_NAME" (default). The default value SERVER_NAME checks if the HTTP Host header equals the SERVER_NAME and SERVER_PORT. This is secure in correctly configured hosting environments and does not need further configuration.

Under certain circumstances, it might be required to change the default configuration. A typical case is a hosting setup with a Load Balancer, CDN or a HA proxy.

Typical configuration examples 

The following matches all hosts that end with .domain.com with all corresponding subdomains:

.*\.domain\.com
Copied!

A common setup could include the leading www. (optional):

(www\.)?domain\.com
Copied!

The following matches all hosts with subdomains under .domain.com and .otherdomain.com:

(.*\.domain|.*\.otherdomain)\.com
Copied!

Be aware that HTTP Host header may also contain a port. If your installation runs on a specific port, you need to explicitly allow this in your pattern. To allows only www.domain.com:88, not www.domain.com, you could configure:

www\.domain\.com:88
Copied!

To disable this check completely (not recommended because it is insecure) you can use ".*" as pattern:

.*
Copied!

Extension 'hosts_pattern' 

Take a look at the extension 'hosts_pattern' which generates the patterns for you

TYPO3 Exception 1396795886 

TYPO3 Exception 1397406356 

TYPO3 Exception 1397836158 

No or invalid extension key "..." given. 

  • Search for variable $extensionKey and replace with the extension key as $_EXTKEY or string myExtension
  • Try not to use $_EXTKEY in dynamicConfigFiles or otherwise included TCA snippets
  • Check https://forge.typo3.org/issues/59033

You may have to clear the cache in install tool (See Important actions).

https://docs.typo3.org/typo3cms/InstallationGuide/Upgrade/RemoveTemporaryCacheFiles/Index.html

TYPO3 Exception 1399144499 

TYPO3 Exception 1399144521 

TYPO3 Exception 1399144551 

TYPO3 Exception 1399161266 

TYPO3 Exception 1399161284 

TYPO3 Exception 1399161302 

TYPO3 Exception 1399512421 

TYPO3 Exception 1399638572 

TYPO3 Exception 1399982816 

TYPO3 Exception 1401205213 

TYPO3 Exception 1401732564 

Invalid file identifier given. It must be of type string and not empty. "NULL" given. 

This is an exception happening if GIFBUILDER is used in css_styled_content texpic renderer:

See https://forge.typo3.org/issues/62184

The bug has been solved in TYPO3 6.2.12 (and later)

TYPO3 Exception 1401732565 

TYPO3 Exception 1402043263 

TYPO3 Exception 1402421007 

TYPO3 Exception 1403653369 

TYPO3 Exception 1404038665 

TYPO3 Exception 1404068038 

No extension key could be determined when calling addPlugin() 

You will see this exception most likely because \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPlugin() is used in a ext_tables.php file, which will not work. As described in the API \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPlugin() is meant to be called from ext_tables.php or (as of TYPO3 6.2.4 or later) in a file in Configuration/TCA/Overrides/tt_content.php. Calling it from any other place e.g. ext_localconf.php does not work and is not supported

If you call it from Configuration/TCA/Overrides/tt_content.php, the extension key needs to be specified as third parameter.

TYPO3 Exception 1404068039 

TYPO3 Exception 1404378171 

TYPO3 Exception 1404472382 

TYPO3 Exception 1407060572 

Fluid parse error in template "..." 

Case 1: Missing Extension 

E.g. #1 Frontend editing required but not installed

If you did change your templates like this:

<core:contentEditable table="tt_content" field="header" uid="42"> <f:render partial="Header/All" arguments="{_all}" /> </core:contentEditable>

… you need to add the frontend_editing extension.


E.g. #2 Vhs extension missing

Fluid parse error in template Query_action_show_0c62eb625eb2a7904988fc25163bb9056e30949a, line 11 at character 1. Error: The ViewHelper <v:variable.set> could not be resolved. Based on your spelling, the system would load the class FluidTYPO3\Vhs\ViewHelpers\Variable\SetViewHelper, however this class does not exist. (error code 1407060572). Template source chunk: <v:variable.set name="CUD" value='<f:cObject typoscriptObjectPath="lib.CUD" />' />

In Fluid the namespace {namespace v=FluidTYPO3\Vhs\ViewHelpers} was declared, but the Vhs extension was missing.

Case 2 - Typos 

Uncaught TYPO3 Exception #1407060572: Fluid parse error in template Standard_action_index_d05c4e8f75e024f00a98da5e29c3ed0043a25267, line 9 at character 1. Error: The ViewHelper <xy:custom> could not be resolved. Based on your spelling, the system would load the class MyVendor\MyExtension\ViewHelpers\CustomViewHelper, however this class does not exist. (error code 1407060572). Template source chunk: <xy:custom myParameter="somedata" />

Check for typos! I named the ViewHelper "CustomViewhelper" with an lowercase "h", which leads to above fatal error.

Case 3 - Autoloading failed 

Check for correct namespaces derived from PSR-4 in /vendor/composer/autoload_psr4.php. Sometimes the class hasnt been autoloaded at all, due to typos in composer.json.

Case 4 - Clear Caches 

Clearing caches in Install Tool resolved the error.

Case 5 - Fix outdated ViewHelpers 

In many cases the ViewHelpers of an Extension have changed. This can happen, when partials or templates did not get updated when an extension was updated. In this case you have to check, where the Viewhelper is used and compare it to the new template or partial.

For example in powermail this ViewHelper: <vh:string.RawAndRemoveXss>{foo}</vh:string.RawAndRemoveXss>

Is in newer versions this: <vh:string.escapeLabels>{foo}</vh:string.escapeLabels>

TYPO3 Exception 1410286153 

TYPO3 Exception 1410633087 

TYPO3 Exception 1410633412 

TYPO3 Exception 1410633510 

TYPO3 Exception 1411581139 

TYPO3 Exception 1411840171 

TYPO3 Exception 1411840172 

TYPO3 Exception 1414513947 

TYPO3 Exception 1415714161 

TYPO3 Exception 1415878732 

TYPO3 Exception 1415958218 

TYPO3 Exception 1415968498 

TYPO3 Exception 1416391467 

Registered eID has invalid script path. 

Make sure the eID registration is either a path to a .php script, or a ClassName::methodName:

$TYPO3_CONF_VARS['FE']['eID_include']['tx_vendor_extname'] = 'Vendor\Extname\Handler::search';
Copied!

TYPO3 Exception 1416919866 

TYPO3 Exception 1417105493 

TYPO3 Exception 1417988921 

The CSRF protection token for the requested module is missing or invalid. 

Page module not working (TYPO3 7.x - fixed in newer versions) 

Create your first page in the List-tab. Afterwards it will work in the Page-tab too. Copied from this german thread: https://forum.typo3.org/index.php/t/210486/

Other Workaround, which applies for 7.4.0:

  • Export (to .t3d) a single leaf page from another TYPO3 CMS instance (mine was 6.2)
  • Right click root element in page tree => Import from .t3d (I imported only page properties)
  • Now I can append other pages to that page by using the New operation (which failed before)
  • I can even add pages (with New to the root element which did not work before.

Still, none of my pages is tagged as Use as Root Page in Page Properties > Behaviour => It does not have to do with "Root Page". Instead, at least one page must exist to get rid of the Bug (as a workaround).

Limitation: When I delete all pages in the page tree, and then try to right-click-New => I hit the error again. Basically this means that this workaround only works as long as you don't delete all pages.

See https://forge.typo3.org/issues/66704. When there is a fix available and released, an update should do.

TYPO3 Exception 1420281366 

$className "..." must not start with a backslash. 

Might happen, if a PHP class is referenced with a leading backslash, for example in itemsProcFunc. In newer versions of PHP reference classes via ::class to avoid the error.

TYPO3 Exception 1420480928 

RealURL is not able to find the root page id for the given domain 

RealURL searches in the sys_domain table for a domain with matches the current host. It would then detect the PID of the domain record and hence get the root page of the domain.

If this exception is thrown, then

  • either no domain record exists for the current domain (solution: add domain record)
  • or a proxy modifies the host of the request and RealURL cannot find it (solution: check what RealURL uses to match a domain, check for proxies, maybe add a domain record)
  • or RealURL cant handle ports in the domain (eg: localhost:8023 - currently no other solution than switching to a host without ports or overwrite the ConfigurationReader class)

TYPO3 Exception 1421053336 

TYPO3 Exception 1422044826 

TYPO3 Exception 1422553107 

TYPO3 Exception 1422564295 

TYPO3 Exception 1422625075 

TYPO3 Exception 1422631610 

TYPO3 Exception 1422634778 

TYPO3 Exception 1422705270 

TYPO3 Exception 1422705271 

TYPO3 Exception 1422709241 

TYPO3 Exception 1422723050 

TYPO3 Exception 1422723059 

TYPO3 Exception 1422771427 

TYPO3 Exception 1422906893 

TYPO3 Exception 1423043755 

TYPO3 Exception 1423347324 

TYPO3 Exception 1424031813 

TYPO3 Exception 1424031814 

TYPO3 Exception 1424031815 

TYPO3 Exception 1424355157 

Session file not writable. Please check permission on typo3temp/InstallToolSessions and its subdirectories. 

As the error states, check file permission on the mentioned directory. Additionally, check $GLOBALS['TYPO3_CONF_VARS']['BE']['fileCreateMask'] and $GLOBALS['TYPO3_CONF_VARS']['BE']['folderCreateMask']. The masks might be too restrictive.

TYPO3 Exception 1425153762 

TYPO3 Exception 1425236663 

TYPO3 Exception 1425381442 

TYPO3 Exception 1425389240 

The requested resource "..." was not found. 

Affected: 7.4.0 and 7.5.0-dev and maybe earlier versions.

See https://forge.typo3.org/issues/66704

Limitation: When I delete all pages in the page tree, and then try to right-click-"New" => I hit the error again. Basically this means that this workaround only works as long as you don't delete all pages.

As soon as https://forge.typo3.org/issues/66704 is fixed and the corresponding version released, an update might fix the problem.

TYPO3 Exception 1425389455 

Invalid request for route "..." 

Solutions 

  • Log out / Log in again
  • Clear caches in the Install Tool
  • Reload the backend

TYPO3 Exception 1425990190 

TYPO3 Exception 1425990198 

TYPO3 Exception 1426448465 

TYPO3 v12.4, 18.06.2024 

#1426448465 RuntimeException
Field must not be empty
Copied!

This error happened after updating from TYPO3 v10.4 when trying to edit a files metadata in the "Filelist" module.

There was an invalid entry in the TCA of sys_file_metadata. In TYPO3 v10 the falsely declared div title was not displayed and ignored. In TYPO3 v12.4 this error was thrown.

Solution: Fix TCA of sys_file_metadata 

Items in TCA showitem must be separated by comma , not semicolon ;. A divider --div-- must start with this string after the previous comma.

$GLOBALS['TCA']['sys_file_metadata']['types'][1] = [
    'showitem' => $GLOBALS['TCA']['sys_file_metadata']['types'][1]['showitem']
-        . ';--div--;My-Cool-Center,my_cool_center_enable',
+        . ',--div--;My-Cool-Center,my_cool_center_enable,',
];
Copied!

Unknown TYPO3 Version 

Field must not be empty 

Error in TCA configuration. E.g. in section types['1']['showitem'].

Possible solution 

Fix TCA configuration. E.g. showitem string. (In my case, the value was illegally starting with ;;1,.)

TYPO3 Exception 1426454001 

TYPO3 Exception 1426459735 

TYPO3 Exception 1427143328 

TYPO3 Exception 1427455377 

TYPO3 Exception 1427455378 

TYPO3 Exception 1428176468 

TYPO3 Exception 1428227862 

TYPO3 Exception 1428582655 

TYPO3 Exception 1428700748 

TYPO3 Exception 1430409089 

TYPO3 Exception 1430560390 

TYPO3 Exception 1430561927 

TYPO3 Exception 1430562374 

TYPO3 Exception 1430580308 

TYPO3 Exception 1430635895 

TYPO3 Exception 1430635896 

TYPO3 Exception 1430657869 

TYPO3 Exception 1430852128 

TYPO3 Exception 1431452406 

Missing renderType in TCA of field "..." 

This exception can be raised when the TCA definition is invalid (check if the "type"-Attribute is correct/non-empty). The current TCA can be shown under System > Configuration > $GLOBALS['TCA']...

TYPO3 Exception 1431872546 

Node of type "..." must implement NodeInterface 

Check the code of the mentioned node type and implement the interface.

TYPO3 Exception 1432080411 

TYPO3 Exception 1432207533 

TYPO3 Exception 1432223531 

TYPO3 Exception 1432223893 

TYPO3 Exception 1432933855 

TYPO3 Exception 1433155522 

TYPO3 Exception 1433155563 

TYPO3 Exception 1433155705 

Element "..." already has a resolver registered with priority "..." 

This happens, if two NodeResolvers with the same priority for the same element have been registered, for example when installing two RTEs (like ckeditor and tinymce). Remove one of them and everything works again.

TYPO3 Exception 1433157422 

TYPO3 Exception 1433416043 

The login provider "..." defines an invalid provider. 

Flush all caches via Clear all cache button in the Install Tool.

TYPO3 Exception 1433416044 

TYPO3 Exception 1433416045 

TYPO3 Exception 1433416046 

TYPO3 Exception 1433417281 

TYPO3 Exception 1433944932 

TYPO3 Exception 1434539815 

TYPO3 Exception 1436195933 

TYPO3 Exception 1436195934 

TYPO3 Exception 1436201329 

TYPO3 Exception 1436717266 

TYPO3 Exception 1436717267 

TYPO3 Exception 1436717268 

TYPO3 Exception 1436717269 

TYPO3 Exception 1436717270 

TYPO3 Exception 1436717271 

TYPO3 Exception 1436717272 

TYPO3 Exception 1436717273 

TYPO3 Exception 1436717274 

TYPO3 Exception 1436717275 

TYPO3 Exception 1436717277 

TYPO3 Exception 1436717278 

TYPO3 Exception 1436717279 

TYPO3 Exception 1436717281 

TYPO3 Exception 1436717282 

TYPO3 Exception 1436717284 

TYPO3 Exception 1436717285 

TYPO3 Exception 1436717286 

TYPO3 Exception 1436717287 

TYPO3 Exception 1436717288 

TYPO3 Exception 1436717289 

TYPO3 Exception 1436717290 

TYPO3 Exception 1436717291 

TYPO3 Exception 1436717292 

TYPO3 Exception 1436717293 

TYPO3 Exception 1436717294 

TYPO3 Exception 1436717295 

TYPO3 Exception 1436717296 

TYPO3 Exception 1436717297 

TYPO3 Exception 1436717301 

TYPO3 Exception 1436717302 

TYPO3 Exception 1436717303 

TYPO3 Exception 1436717304 

TYPO3 Exception 1436717305 

TYPO3 Exception 1436717306 

TYPO3 Exception 1436717307 

TYPO3 Exception 1436717308 

TYPO3 Exception 1436717309 

TYPO3 Exception 1436717310 

TYPO3 Exception 1436717311 

TYPO3 Exception 1436717320 

TYPO3 Exception 1436717322 

The parsedUri string appears to be malformed 

TYPO3 Exception 1436717324 

TYPO3 Exception 1436717326 

TYPO3 Exception 1436717328 

TYPO3 Exception 1436717330 

TYPO3 Exception 1436717332 

TYPO3 Exception 1436717334 

TYPO3 Exception 1436717336 

TYPO3 Exception 1436717337 

TYPO3 Exception 1436717338 

TYPO3 Exception 1436809789 

TYPO3 Exception 1436895930 

TYPO3 Exception 1436895931 

TYPO3 Exception 1436899571 

TYPO3 Exception 1436899572 

TYPO3 Exception 1436909478 

TYPO3 Exception 1437078620 

TYPO3 Exception 1437078780 

TYPO3 Exception 1437081986 

TYPO3 Exception 1437420865 

TYPO3 Exception 1437425803 

TYPO3 Exception 1437425804 

TYPO3 Exception 1437653136 

TYPO3 Exception 1437654247 

TYPO3 Exception 1437654332 

TYPO3 Exception 1437654409 

TYPO3 Exception 1437655862 

TYPO3 Exception 1437656081 

Record with uid "..." from table "..." not found 

TYPO3 Exception 1437656323 

TYPO3 Exception 1437656456 

$uid must be positive integer, 0 given 

Gridelements 

Try updating to a newer Gridelements version.

Database not up to date 

The issue was solved here by comparing the database with the specification (see Install Tool > Important Actions). Make sure your table definitions are the same as they are in the current database!

TYPO3 Exception 1437663061 

TYPO3 Exception 1437679336 

TYPO3 Exception 1437679657 

TYPO3 Exception 1437679856 

TYPO3 Exception 1437683248 

TYPO3 Exception 1437687404 

TYPO3 Exception 1437688402 

TYPO3 Exception 1437689705 

TYPO3 Exception 1437690507 

TYPO3 Exception 1437745221 

TYPO3 Exception 1437745640 

TYPO3 Exception 1437745759 

TYPO3 Exception 1437750231 

The way registering a wizard in TCA has changed in 6.2 and was removed in CMS 7. 

See: https://docs.typo3.org/typo3cms/extensions/core/Changelog/7.0/Breaking-59659-DeprecatedCodeRemovalInBackendSysext.html

Solution: 

Check and adapt TCA and FlexForms.

For TCA replace

'script' => 'browse_links.php?mode=wizard&act=file'
Copied!

with

'module' => [
    'name' => 'wizard_element_browser',
    'urlParameters' => [
        'mode' => 'wizard',
        'act' => 'file'
    ]
]
Copied!

For FlexForms replace

<script>browse_links.php?mode=wizard&act=file</script>
Copied!

with

<module type="array">
    <name>wizard_element_browser</name>
    <urlParameters type="array">
        <mode>wizard</mode>
        <act>file</act>
    </urlParameters>
</module>
Copied!

For wizard_add.php, wizard_edit.php, wizard_list.php, wizard_rte.php, the module names stay the same as the old php files name, for instance:

'module' => [
    'name' => 'wizard_add',
],
Copied!

TYPO3 Exception 1437906440 

TYPO3 Exception 1437906441 

TYPO3 Exception 1437914223 

TYPO3 Exception 1437991120 

TYPO3 Exception 1438079402 

TYPO3 Exception 1438170741 

TYPO3 Exception 1438183881 

TCA table "..." ctrl['type'] is set to "...", but this field does not exist in the database of this table 

This error happens for example in an extension because the TCA configuration was not suitable for the MySQL table fields defined in ext_tables.sql.

Error Example - TCA:

$TCA['tx_myExtension_table'] = [
  'ctrl' => [
     'title'     => $ll.'table.auteur',
     'label'     => 'nom',
     'tstamp'    => 'tstamp',
     'crdate'    => 'crdate',
     'cruser_id' => 'cruser_id',
     'type'      => 'type',
     ...
     ...
Copied!

And in ext_tables.sql:

CREATE TABLE tx_myExtension_table (
  uid int(11) NOT NULL auto_increment,
  pid int(11) DEFAULT '0' NOT NULL,
  tstamp int(11) DEFAULT '0' NOT NULL,
  crdate int(11) DEFAULT '0' NOT NULL,
  cruser_id int(11) DEFAULT '0' NOT NULL,
  sys_language_uid int(11) DEFAULT '0' NOT NULL,
  ...
  ...
Copied!

Missing:

type varchar(100) NOT NULL DEFAULT '0',
Copied!

or any other type field definition.

TYPO3 Exception 1438185331 

At least one "types" array must be defined for table "...", preferred "0" 

Solution: Edit the file your_extension_key/Configuration/TCA/table_from_error.php of your extension. Use your extension key and file name of your table instead of this example.

Add an empty part of types to it, like this:

$result = [
   'ctrl' => [
      'title' => 'LLL:EXT:your_extension_key/locallang_db.xml:myfirsttable_mm_second',
      // ...
      'columns' => [
         // ...
      ],
   'types' => [
      '0' => [
        'showitem' =>
      ]
   ],
],
Copied!

Of course you can add a more enhanced types array if you have a need for it.

TYPO3 Exception 1438185437 

TYPO3 Exception 1438191758 

TYPO3 Exception 1438249426 

Default language record with id X not found in table Y while editing record Z 

This message is a result of an data inconsistency. This happens if the translation parent in default language has been deleted without deleting the translation that is currently being edited. Please contact your support for further help (if you are the support: either remove the translation parent manually in the database, restore the parent record or discard the translations, too).

TYPO3 Exception 1438253614 

TYPO3 Exception 1438352574 

TYPO3 Exception 1438505113 

TYPO3 Exception 1438594044 

TYPO3 Exception 1438594406 

No columns definition in TCA table 

On possible cause for this is the use of old ext_tables.php/TCA configuration. Please see https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/7.6/Index.html for the changes in TYPO3. Also, the TCA file must return the array, not only declare it, as would work before.

TYPO3 Exception 1438594829 

TYPO3 Exception 1438604329 

TYPO3 Exception 1438607163 

TYPO3 Exception 1438607164 

TYPO3 Exception 1438607165 

TYPO3 Exception 1438614542 

TYPO3 Exception 1438780511 

TCA internal_type of field "..." in table "..." must be set to either db, (file) or file_reference 

In v10.4.3 this exception may happen if

  • an internal_type file or file_reference is used in combination with type group

Using these types has been deprecated in v9.5 and removed in v10. Only internal_type db or folder are allowed.

If you are using files via the file abstraction layer (FAL) or as inline elements (IRRE), you should use the type inline instead.

TYPO3 Exception 1438782187 

TYPO3 Exception 1438871603 

TYPO3 Exception 1438875247 

TYPO3 Exception 1438875248 

TYPO3 Exception 1438875249 

TYPO3 Exception 1439228111 

Cannot set an alias map as the alias loader is not registered! 

Composer install with "--no-scripts" option 

Probably you tried to run a composer install/update using the --no-scripts option.

composer install --no-scripts
Copied!

Try to run composer install again without the --no-scripts option.

composer install
Copied!

TYPO3 Exception 1439288036 

An item in field "..." of table "..." is not an array as expected 

This happens in TYPO3 7.6 if there is a incompatible 'items' TCA definition in the according field like

'items' => [
    '0' => '-'
]
Copied!

or

'items' => ['-']
Copied!

This has to be replaced with a correct item definition like

'items' => [
    ['-', 0]
]
Copied!

https://docs.typo3.org/typo3cms/TCAReference/7.6/Reference/Columns/Select/Index.html#items

Same error on TYPO3 12.4: 

I got this error in TYPO3 12.4 when changing the TCA items (l10n_parent field) from old format to new one forgetting the outer brackets []

wrong:

'items' => [
    'label' => '-',
     'value' => 0,
],
Copied!

right:

'items' => [
    [
        'label' => '',
        'value' => 0,
    ],
],
Copied!

TYPO3 Exception 1439298496 

TYPO3 Exception 1439317801 

TYPO3 Exception 1439317802 

TYPO3 Exception 1439552058 

The extension "..." has invalid version constraints in depends section. Extension key is missing! 

  • To fix this, go to your TYPO3 Installation directory, go to typo3conf/ext/... and edit ext_emconf.php and delete the line in the depends section, which neither contains any extension key nor any version, but only an empty array key with empty array value (' ' => ' ',). In my case this was line 31. -> Save the file.
  • After this go to your TYPO3 backend, go to the extensions subcategory and enable the extension by clicking the box in front of this entry.
  • Refresh your page, and you should be fine.

TYPO3 Exception 1439552059 

The extension "..." has invalid version constraints in "conflicts" section. Extension key is missing! 

Check the ext_emconf.php or composer.json file for invalid "conflicts".

TYPO3 Exception 1439552060 

The extension "..." has invalid version constraints in suggests section. Extension key is missing! 

Check the ext_emconf.php or composer.json file for invalid "suggests".

TYPO3 Exception 1439555561 

The composer.json found for extension "..." is invalid! 

A composer.json file has a syntax error. Use the command line composer.phar validate to get details about this error and the line number which causes this error.

This error can also occur if the composer.json file is not accessible.

Alternatively, use a JSON online validator and copy-paste the contents of your composer.json. Then you will see the exact syntax error in this JSON file. E.g. here.

TYPO3 Exception 1439569743 

Field "..." of table fe_users reference to foreign table "...", but this table is not defined in TCA 

Make sure you have the correct table name in foreign_table (TCA).

TYPO3 Exception 1439587168 

TYPO3 Exception 1439925240 

TYPO3 Exception 1440066481 

TYPO3 Exception 1440499337 

TYPO3 Exception 1440499338 

TYPO3 v12.3 - 2023-03-30 

The issue 

With TYPO3 v12.3 the items of the TCA types "check", "radio" and "select" requires a "label" key instead of the array index "0". In v12 a TCA migration is in place which is not applied to custom site configurations in v12.3.

Solution 

Migrate from:

'config' => [
    'type' => 'check',
    'renderType' => 'checkboxToggle',
    'items' => [[
        0 => '',
        1 => '',
    ]],
]
Copied!

to:

'config' => [
    'type' => 'check',
    'renderType' => 'checkboxToggle',
    'items' => [[
        'label' => '',
        'value' => '',
    ]],
]
Copied!

To stay compatible with TYPO3 v12 and v11, use:

'config' => [
    'type' => 'check',
    'renderType' => 'checkboxToggle',
    'items' => [[
        0 => '',
        1 => '',
        'label' => '',
        'value' => '',
    ]],
]
Copied!

TYPO3 Exception 1440506893 

Data structure error: Line 1: Invalid document end 

Invalid document end: This happens if you define a FlexForm xml file which is not available. Check the path to your file.

TYPO3 Exception 1440601540 

TYPO3 Exception 1440676540 

TYPO3 Exception 1440685208 

Using Flux 

#1440685208: Broken data structure on field name pi_flexform. section
without type or vice versa is not allowed
Copied!

Happens when using <flux:form.container> in a fluid content element.

In our case it was due to <type>no_map</type> which we commented out. Then it worked.

Issues:

TYPO3 Exception 1440754978 

TYPO3 Exception 1440754979 

TYPO3 Exception 1440754980 

The option "source" is required and must not be empty 

This happens in 9LTS if you use ExtensionManagementUtility::addModule() with 7LTS parameters. Instead of

'labels' => [
  'tabs_images' => [
    'tab' => 'EXT:someext/Resources/Public/Images/icon.svg',
  ],
  'll_ref' => 'LLL:EXT: someext/Resources/Private/Language/locallang_mod.xml',
]
Copied!

you need the 8LTS+ parameter type

'icon' => 'EXT: someext/Resources/Public/Icons/icon.svg',
'labels' => 'LLL:EXT: someext/Resources/Private/Language/locallang_mod.xml'
Copied!

TYPO3 Exception 1440777705 

TYPO3 Exception 1440779351 

TYPO3 Exception 1441108674 

TYPO3 Exception 1441108719 

TYPO3 Exception 1441390263 

TYPO3 Exception 1441706330 

TYPO3 Exception 1441706340 

TYPO3 Exception 1441706370 

Button "TYPO3CMSBackendTemplateComponentsButtonsLinkButton" is not valid 

#1441706370: Button "TYPO3\CMS\Backend\Template\Components\Buttons\LinkButton" is not valid
 InvalidArgumentException thrown in file
 typo3_src/typo3/sysext/backend/Classes/Template/Components/ButtonBar.php in line 66.
Copied!

(TYPO3 7.6.15)

Reason: URL, title or icon is empty.

One reason may be a missing language file. Imagine you check out a TYPO3-page from git locally and also use a copy of the database/configuration of this site. Then, perhaps, the configured language is missing on your system. (For me it was german and the quick fix was to disable it via "Languages".)

TYPO3 Exception 1441706378 

TYPO3 Exception 1441791615 

TYPO3 Exception 1441893777 

TYPO3 Exception 1442050529 

TYPO3 Exception 1442050579 

TYPO3 Exception 1442052249 

TYPO3 Exception 1442052263 

TYPO3 Exception 1442236317 

TYPO3 12.4.17 - 29.07.2024 

caption: Exception Message

MenuItem "" is not valid
Copied!

Situation 

Right after an update from TYPO3 11 to 12. Forgot to clear the cache

Solution 

Clear all caches from install tool or console

TYPO3 12.4.14 - 17.05.2024 

caption: Exception Message

MenuItem "Liste" is not valid
Copied!

Situation 

Trying to add a menu Item to the menu in a custom backend module:

EXT:my_extension/Classes/Controller/MyModuleController.php
$menu = $moduleTemplate->getDocHeaderComponent()->getMenuRegistry()->makeMenu();

 $menuItem = $menu->makeMenuItem()
    ->setTitle($menuItemConfig['label'])
    ->setHref($this->uriBuilder->reset()->uriFor($menuItemConfig['action'], [], $menuItemConfig['controller']))
    ->setActive($isActive);
$menu->addMenuItem($menuItem);
Copied!

This exception is thrown when the title or the href of the menuitem are empty. In this case the UriBuilder returned an emptry result, therefore the Href was empty.

Solution 

Fix the href generation.

TYPO3 Exception 1442236362 

TYPO3 Exception 1442239768 

TYPO3 Exception 1442305505 

TYPO3 Exception 1442431631 

TYPO3 Exception 1442592030 

TYPO3 Exception 1442736343 

TYPO3 Exception 1442763890 

TYPO3 Exception 1442787911 

Solution 

Delete all cache_core files

sudo rm -rf typo3temp/cache/code/cache_core
Copied!

TYPO3 Exception 1442928537 

TYPO3 Exception 1442996707 

TYPO3 Exception 1443651368 

TYPO3 Exception 1443651369 

TYPO3 Exception 1443706103 

TYPO3 Exception 1443793404 

TYPO3 12.4 - 01.07.2025 

Installation Overview 

Custom extension with custom table and inline field created by stefanfroemken/ext-kickstarter

The Issue 

The generated TCA is not complete:

'fieldname' => [
    'label' => 'Fieldname',
    'config' => [
        'type' => 'inline',
    ],
],
Copied!

Solution 

Add foreign_table and foreign_field to TCA:

'fieldname' => [
    'label' => 'Fieldname',
    'config' => [
        'type' => 'inline',
        'foreign_table' => 'tx_myextension_domain_model_othertable',
        'foreign_field' => 'parent',
    ],
],
Copied!

See also Example: Simple 1:n inline relation

TYPO3 Exception 1443829370 

TYPO3 Exception 1443944274 

TYPO3 Exception 1443986127 

TYPO3 Exception 1444142481 

TYPO3 Exception 1444374805 

TYPO3 Exception 1444398947 

TYPO3 Exception 1444431128 

TYPO3 Exception 1444434102 

TYPO3 Exception 1444434103 

TYPO3 Exception 1444434104 

TYPO3 Exception 1444725828 

TYPO3 Exception 1444725853 

TYPO3 Exception 1444995464 

TYPO3 Exception 1444996537 

This error happens since TYPO3 7.6 if your extension has defined the TCA in the file Configuration/TCA/my_extension_table.php and when "'displayCond' => 'EXT:foreign_extension:LOADED:true'" is used.

see Bug #76958: displayCond LOADED does not check the loaded extension

You must move the the column with the condition into the folder Configuration/TCA/Overrides of your extension (my_extension) or of the foreign extension (foreign_extension) or of a third connector extension like my_extension_connector. There you must use condition

if (\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::isLoaded('foreign_extension')) {
   $temporaryColumns = array (
     'my_field_for_foreign_extension' => array (
Copied!

in the file Configuration/TCA/Overrides/my_extension_table.php around the part where the column is defined.

TYPO3 Exception 1444999130 

TYPO3 Exception 1445078627 

TYPO3 Exception 1445078628 

TYPO3 Exception 1446118286 

TYPO3 Exception 1446483133 

TYPO3 Exception 1446559458 

TYPO3 Exception 1446664764 

TYPO3 Exception 1446996136 

TYPO3 Exception 1446996254 

TYPO3 Exception 1446996319 

Configuration retrieved from FlexForm is incomplete or not of type "inline" 

#1446996319: Configuration retrieved from FlexForm is incomplete or not of type "inline"
UnexpectedValueException thrown in file
/../typo3/sysext/backend/Classes/Controller/FormInlineAjaxController.php in line 935.
Copied!

Happens when attaching an image to a new non-saved Fluid content element.

Also:

UnexpectedValueException thrown in file
/.../typo3/sysext/backend/Classes/Controller/FormInlineAjaxController.php in line 909.
Copied!

TYPO3 v7.6.32 Happens when attaching an image to an existing content element.

TYPO3 Exception 1447789490 

TYPO3 Exception 1447789491 

TYPO3 Exception 1447789492 

TYPO3 Exception 1448194036 

TYPO3 Exception 1450086736 

TYPO3 Exception 1450561838 

TYPO3 Exception 1450561878 

TYPO3 Exception 1450714322 

TYPO3 Exception 1450904202 

No storage folder (option storagePid) for frontend users given 

Solution: Define your user storage page: Either in plugin options (flexform) or in your site's TypoScript.

TYPO3 Exception 1454252193 

TYPO3 Exception 1454510731 

TYPO3 Exception 1454510732 

TYPO3 Exception 1455499673 

TYPO3 Exception 1455499679 

TYPO3 Exception 1455499720 

TYPO3 Exception 1455499721 

TYPO3 Exception 1456914444 

TYPO3 Exception 1457097250 

TYPO3 Exception 1457175152 

TYPO3 Exception 1457177667 

TYPO3 Exception 1457690656 

TYPO3 Exception 1457693564 

TYPO3 Exception 1457873493 

TYPO3 Exception 1458302830 

TYPO3 Exception 1458302901 

TYPO3 Exception 1458745468 

This exception has been introduced together with exception 1458745712, same documentation may apply for this one as well.

TYPO3 10 - 2022-05-19 

The Issue 

(1/1) #1458745468 UnexpectedValueException

Invalid flex form data structure on field name "pi_flexform" with element "image" in section container "objectFeedback": Nesting inline elements in flex form sections is not allowed.

This exception occurs when nesting a <flux:field.inline.fal> inside a <flux:form.section>. This is not supported anymore since TYPO3 v10.

See https://github.com/FluidTYPO3/flux/issues/1803#issuecomment-697283924

Solution 

Rework the content element: Split it into a container element and a sub element that may be added multiple times.

TYPO3 Exception 1458745712 

Invalid flex form data structure 

Invalid flex form data structure on field name "pi_flexform" with
element "..." in section container "section": Nesting sections in
container elements sections is not allowed.
Copied!

Background 

Support for editing/creating nested flex form section containers has been blocked in TYPO3 7.4.5 due to issues in data consistency and component handling.

See Core bug report #73125.

Nested sections in Flux aka "Fluid Powered TYPO3" 

Nesting sections could be thought of as "repeaters" inside "repeaters", such as for a FCE which contained a dynamic list of contacts with another dynamic list of phone numbers inside. Blockage of nested sections in TYPO3 Core means that Flux isn't able to support these data structures any more if TYPO3 7.4.5 or higher is being used.

A request for a flag to circumvent the blockage when Flux is being used has been made but was rejected (see TYPO3 Core bug report #76281 on Forge, "Change 47369 killed features in flux").

Flux developers stated that it was only meant to abstract core's API for flex forms, thus support for nested sections was only available because it was in Core. No workarounds will be implemented by "Fluid Powered TYPO3" (i.e. neither flux or fluidcontent) and the Core exception will not be caught (see flux issue 1139 on GitHub, "Nesting sections in container elements sections is not allowed.").

Impact 

Previously created FCEs with nested sections can still be read (and rendered), disabled/enabled, copied and deleted, but no longer be fully edited in backend until all nested sections have been removed from the FCE's Configuration section. Attempting to enter the edit view for a FCE with such a structure now generally fails with the above exception being displayed. Previously entered nested data seems to survive saving in BE even after the data structure has been modified, but the absence of a clean-up of such invalid data cannot be guaranteed for all times.

Workarounds 

Using nested FCEs (containers/grid) instead 

Most times it's possible to split affected FCEs into one or more container FCEs to contain special FCEs only meant for use inside these containers.

For example, if you had a structure such as:

  • FCE "Contacts"

    • Section/object "Person"

      • Field "Name" => "John Doe"
      • Section/object "Number"

        • Field "Type" => "Phone"
        • Field "Number" => "12345"
      • Section/object "Number"

        • Field "Type" => "Fax"
        • Field "Number" => "54321"
    • Section/object "Person"

      • ...

You could split it so that you get:

  • FCE "Contacts Container"

    • Grid column "Contacts"

      • FCE "Contact Person"

        • Field "Name" => "John Doe"

          • Section/object "Number"

            • Field "Type" => "Phone"
            • Field "Number" => "12345"
          • Section/object "Number"

            • Field "Type" => "Fax"
            • Field "Number" => "54321"
      • FCE "Contact Person"

        • ...

TYPO3 Exception 1459421719 

TYPO3 Exception 1459422125 

TYPO3 Exception 1459422492 

Datebase credential structure in LocalConfiguration.php not up to date 

This error happen when you update a TYPO3 7.x installation to Version 8.x. Because of the changed array structure in version 8.x, TYPO3 cannot find the proper database connection.

Change your typo3conf/LocalConfiguration.php

From:

'DB' => [
    'database' => '',
    'host' => 1',
    'password' => '',
    'port' => 3306,
    'username' => '',
],
Copied!

To:

'DB' => [
    'Connections' => [
        'Default' => [
            'charset' => 'utf8',
            'dbname' => 'typo3_v8',
            'driver' => 'mysqli',
            'host' => '',
            'password' => '',
            'port' => 3306,
            'user' => '',
        ],
    ],
],
Copied!

TYPO3 Exception 1459422968 

TYPO3 Exception 1459423448 

TYPO3 Exception 1459690516 

TYPO3 Exception 1459696089 

TYPO3 Exception 1459696090 

TYPO3 Exception 1459696680 

TYPO3 Exception 1459696681 

TYPO3 Exception 1459708283 

TYPO3 Exception 1459941569 

TYPO3 Exception 1460581769 

TYPO3 10.4.21 - October 6, 2021 

Situation 

  • Exception in FE on loading page: Oops, an error occurred! LinkHandler for page=uid=p1004 was not registered
  • Exception in redirects module when filtering for the redirect where this problem occurs (e.g. enter the source URL)

The exception is logged, you can find the exception stack trace in the TYPO3 log.

Cause of problem 

  • An invalid link target was entered in a redirect, e.g. target=t3://page=uid=p1004

Solution 

  1. This can be fixed by entering a correct target in the redirect.
  2. Because of the exception, it can't be done in the redirects module, must be done in the database directly, e.g.
UPDATE sys_redirect SET target='t3://page?uid=1004' WHERE target='t3://page=uid=p1004';
Copied!

Core issue 

TYPO3 Exception 1460629247 

TYPO3 8.7.1 

Error: No valid handlers found for type: javascript 

Happens after saving in CKEditor.

You may have received this error, because you are trying to save a non-compliant link in CKEditor. Usually CKEditor will eliminate (remove) such links - but in combination with extraAllowedContent it might happen that the link passes the filter.

For example, this would cause the error above:

href="/impressum/"
Copied!

Valid links would be:

href="t3://page?uid=175"
href="https://typo3.org"
Copied!

TYPO3 Exception 1460975513 

TYPO3 Exception 1460975538 

TYPO3 Exception 1460975593 

TYPO3 Exception 1460975633 

TYPO3 Exception 1460975728 

TYPO3 Exception 1460975777 

TYPO3 Exception 1460975840 

TYPO3 Exception 1460975877 

TYPO3 Exception 1460975902 

TYPO3 Exception 1460975922 

TYPO3 Exception 1460976089 

TYPO3 Exception 1460976233 

In a custom content element, that doesn't check, if an image exists this exception might be encountered if the image is missing.

The extension Camaliga is sensible for this issue. If you have assigned a Gallery Map Element to a plugin and with this element is no image connected, than you receive this error message. Look in your storage folder with the Gallery Elements and check all Elements if they have an image assigned. Check also all the translated elements in this folder.

TYPO3 Exception 1460976250 

TYPO3 Exception 1460976286 

TYPO3 Exception 1460976320 

TYPO3 Exception 1460976340 

TYPO3 Exception 1460976403 

TYPO3 Exception 1460976527 

TYPO3 Exception 1460976566 

Misspelled folder name in icon path 

I've encountered the exception that "source" is mandatory during icon rendering.

This was because I misspelled a folder name in the icon path using "EXT:...".

It could not be resolved and therefore the icon path was empty in the end.

Cache 

Clearing the cache via the install tool fixed the error for me

Other 

I received following exception when I installed the following extension svconnector.

I had a similar problem with the same error-code but in a local ddev server. I used ddev v. 0.18.0 - where the error came out and updated to ddev 1.3.0 there the error was gone.

TYPO3 Exception 1460976610 

TYPO3 Exception 1460976644 

TYPO3 Exception 1460977275 

TYPO3 Exception 1461170686 

TYPO3 Exception 1461248062 

TYPO3 Exception 1461598332 

TYPO3 Exception 1462820645 

TYPO3 Exception 1462821084 

TYPO3 Exception 1462869795 

TYPO3 Exception 1463073434 

TYPO3 Exception 1463577497 

TYPO3 Exception 1463578899 

TCA misconfiguration: a field name that does not exist 

TCA misconfiguration in table
"the_table_name" field "the_field_name" config section: ds_pointerField
"the_field_name_type" points to a field name that does not exist.
Copied!

This happens in the TCE for a field which is configured by a 'ds_pointerField'. You must also add a TCA column for the corresponding type field the_field_name_type.

'config_type' => array (
    'label' => 'LLL:EXT:my_extension/locallang_db.xml:the_table_name.the_field_name_type',
    'config' => array (
        'type' => 'select',
        'renderType' => 'selectSingle',
        'items' => array (
            array(, )
        ),
        'default' => ,
        'authMode' => $GLOBALS['TYPO3_CONF_VARS']['BE']['explicitADmode'],
    )
),
Copied!

TYPO3 Exception 1463578900 

TYPO3 Exception 1463652560 

TYPO3 Exception 1463653197 

TYPO3 Exception 1463678524 

TYPO3 Exception 1463826960 

TYPO3 Exception 1463833794 

TYPO3 Exception 1464110956 

TYPO3 Exception 1464112555 

TYPO3 Exception 1464114011 

TYPO3 Exception 1464115059 

TYPO3 Exception 1464115639 

TYPO3 Exception 1464116002 

TYPO3 Exception 1464435459 

TYPO3 Exception 1464550977 

TYPO3 Exception 1464550984 

TYPO3 Exception 1464552894 

TYPO3 Exception 1464553495 

TYPO3 Exception 1464555007 

TYPO3 Exception 1464555650 

TYPO3 Exception 1464556045 

TYPO3 Exception 1464557160 

TYPO3 Exception 1465223252 

TYPO3 Exception 1465392861 

TYPO3 Exception 1466769483 

TYPO3 Exception 1466799482 

TYPO3 Exception 1467983513 

Error message 

ID parameter needs to be passed for the cHash calculation! As a temporary not recommended workaround, you can set $GLOBALS['TYPO3_CONF_VARS']['FE']['cHashIncludePageId'] to false to avoid this error.

General 

This error can happen with TYPO3 6.2.27, 7.6.11 or 8.3.1 and newer. It happens when the CacheHashCalculator API is called without id argument. Starting with TYPO3 6.2.27, 7.6.11 or 8.3.1 this API requires the id argument to be set.

With RealURL 

This exception will be solved with the successor of RealURL 2.0.15. Until an updated version of RealURL has been released, if you encounter this exception, you can manually integrate this fix in RealURL.

Afterwards, clear all your caches.

See also 

TYPO3 Exception 1468149217 

TYPO3 Exception 1468363945 

TYPO3 Exception 1468363946 

TYPO3 Exception 1469363238 

TYPO3 Exception 1469363365 

TYPO3 Exception 1470230766 

Unknown column 'a' in 'field list' 

The field might not have been created yet: do a Database compare.

This error might occur if a model contains a field that does not exist in the corresponding database table. In this case you should add the field to the table in ext_tables.sql.

Table 'db.tx_myextension_domain_model_mymodel' doesn't exist 

TYPO3 Exception 1470230767 

TYPO3 Exception 1470230768 

TYPO3 Exception 1470230769 

TYPO3 Exception 1470230770 

TYPO3 Exception 1470230771 

TYPO3 Exception 1470231748 

TYPO3 Exception 1470742770 

TYPO3 Exception 1471460676 

TYPO3 Exception 1471473377 

TYPO3 Exception 1471473378 

TYPO3 Exception 1471630578 

TYPO3 Exception 1471630579 

TYPO3 Exception 1471630580 

TYPO3 Exception 1471630581 

TYPO3 Exception 1471708999 

TYPO3 Exception 1471710357 

TYPO3 Exception 1471713296 

TYPO3 Exception 1471776457 

TYPO3 Exception 1471776458 

TYPO3 Exception 1472044085 

TYPO3 Exception 1472046376 

TYPO3 Exception 1472060918 

TYPO3 Exception 1472060919 

TYPO3 Exception 1472064721 

TYPO3 Exception 1472064775 

TYPO3 Exception 1472074379 

TYPO3 Exception 1472074485 

Unknown column 'tx_myext_domain_model_myfield.' in 'order clause' 

There's no 'foreign_sorting' set in TCA. For me it happened with an Inline type.

Table 'my_db.tx_someotherextension_domain_model_myfield' doesn't exist 

When you have mapped a relation to an external model in your extension, and did not map it in EXT:extension/Configuration/Extbase/Persistence/Classes.php.

Table 'my_db.tx_mytablename' doesn't exist 

A table name which does not correspond the Extbase table naming scheme, and did not define define the tableName name in EXT:my_extension/Configuration/Extbase/Persistence/Classes.php.

Table 'my_db.tx_myext_persistence_objectstorage' doesn't exist 

Solution 

Go to Admin tools -> Maintenance -> Database compare and bring the database schema up to date.

TYPO3 Exception 1472238493 

TYPO3 Exception 1472239516 

TYPO3 Exception 1472239534 

TYPO3 Exception 1472239535 

TYPO3 Exception 1472239536 

TYPO3 Exception 1472312204 

TYPO3 Exception 1472585525 

TYPO3 Exception 1472748872 

TYPO3 Exception 1473169459 

Using extension cdsrc_httpbasicauth 

This issue is thrown by cdsrc_httpbasicauth if the extension doesn't find a rewrite rule in htaccess.

Add the rule described in file EXT:cdsrc_httpbasicauth/Resources/Private/README.txt

TYPO3 Exception 1474900796 

TYPO3 Exception 1474900797 

TYPO3 Exception 1474900799 

TYPO3 Exception 1474905835 

TYPO3 Exception 1474905953 

TYPO3 Exception 1475924277 

Including a form without including the TypoScript template of the "forms" extension 

For me the exception occurred in TYPO3 9.5.7 When I was trying to include a "form" form and forgot to include the TypoScript Template of extension form.

TYPO3 Exception 1476010403 

TYPO3 Exception 1476029421 

TYPO3 Exception 1476044776 

TYPO3 Exception 1476044883 

TYPO3 Exception 1476044961 

TYPO3 Exception 1476045062 

TYPO3 Exception 1476045117 

TYPO3 [V9] - [2023/12/05] 

The Issue 

This error mesage appears in the frontend when using an Extbase model.

(1/1) #1476045117 TYPO3CMSExtbasePersistenceGenericExceptionInvalidClassException

Could not find class definition for name "Videos". This could be caused by a mis-spelling of the class name in the class definition.

Solution 

In the model, you have to use the full namespace for properties, replace:

use TYPO3\CMS\Extbase\Persistence\ObjectStorage;
use \Site\Mda\Domain\Model\Videos;

/**
 * @var ObjectStorage<Videos>
 */
protected $videos;
Copied!

with:

/**
 * @var \TYPO3\CMS\Extbase\Persistence\ObjectStorage<\Site\Mda\Domain\Model\Videos>
 */
protected $videos;
Copied!

TYPO3 Exception 1476045164 

TYPO3 Exception 1476045274 

TYPO3 Exception 1476045345 

TYPO3 Exception 1476045417 

TYPO3 Exception 1476045469 

TYPO3 Exception 1476045666 

TYPO3 Exception 1476045801 

TYPO3 Exception 1476045828 

TYPO3 Exception 1476045871 

TYPO3 Exception 1476045971 

TYPO3 Exception 1476046229 

TYPO3 Exception 1476046290 

TYPO3 Exception 1476046324 

TYPO3 Exception 1476046361 

TYPO3 Exception 1476046386 

TYPO3 Exception 1476046425 

TYPO3 Exception 1476046453 

TYPO3 Exception 1476047422 

TYPO3 Exception 1476047775 

TYPO3 Exception 1476048246 

TYPO3 Exception 1476048278 

TYPO3 Exception 1476048304 

TYPO3 Exception 1476048351 

TYPO3 Exception 1476048371 

TYPO3 Exception 1476048416 

TYPO3 Exception 1476048455 

TYPO3 Exception 1476048456 

TYPO3 Exception 1476048485 

TYPO3 Exception 1476048511 

TYPO3 Exception 1476048550 

TYPO3 Exception 1476049363 

TYPO3 Exception 1476049364 

TYPO3 Exception 1476049365 

TYPO3 Exception 1476049367 

TYPO3 Exception 1476049451 

TYPO3 Exception 1476049512 

TYPO3 Exception 1476049553 

TYPO3 Exception 1476049592 

TYPO3 Exception 1476049619 

TYPO3 Exception 1476049651 

TYPO3 Exception 1476049652 

TYPO3 Exception 1476049653 

TYPO3 Exception 1476049654 

TYPO3 Exception 1476049702 

TYPO3 Exception 1476049767 

TYPO3 Exception 1476049953 

TYPO3 Exception 1476049981 

TYPO3 Exception 1476049990 

TYPO3 Exception 1476050009 

TYPO3 Exception 1476050084 

TYPO3 Exception 1476050135 

TYPO3 Exception 1476050190 

TYPO3 13.4.4 - 25.01.2025 

When trying to view the Content Security Policy backend module throws error if EXT:lowlevel is not installed.

See also https://forge.typo3.org/issues/105988

Can be solved by installing typo3/cms-lowlevel .

On accesssing the admin tool from the backend 

Access the the install tool directly(via typo3/install.php) and clear all caches.

This helped in TYPO3 9.5.

TYPO3 Exception 1476050222 

TYPO3 Exception 1476050312 

TYPO3 Exception 1476107195 

TYPO3 Exception 1476107260 

TYPO3 Exception 1476107295 

Permission denied 

PHP Warning: session_start(): failed: Permission denied (13)
Copied!

Solution 

Can be fixed by deleting all sess_ files in the temp folder or by creating the folder by hand (if it doesn't exist).

On logging into the backend 

After upgrading from TYPO3 v7.6.23 to TYPO3 v8.7.9, I am getting this error most of the time that I login to the backend.

Solution 

After I delete the folder var in typo3temp, the next backend login succeeds.

case 2:

#1476107295: PHP Warning: include(/var/www/html/foobar/typo3_src-8.7.29/vendor/composer/../psr/http-message/src/UriInterface.php): failed to open stream: Bad message in /var/www/html/foobar/typo3_src-8.7.29/vendor/composer/ClassLoader.php line 444 (More information)
Copied!

Solution 

Check your file system at the folder given in the error message and run

sudo fsck -cfk /dev/sda2
Copied!

where dev/sda2 is the corrupted disk.

PHP Warning: Illegal offset type 

PHP Warning: Illegal offset type in
typo3/sysext/rte_ckeditor/Classes/Controller/BrowseLinksController.php
line 234
Copied!

(TYPO3 v8.7) The error occurred in CKEditor Rich Text Editor while setting a link. This was caused by the page TSconfig for the old rte html Editor. After deleting the page TSconfig for the old RTE everything works as expected again.

Using sb_portfolio2 

1476107295: PHP Warning: Declaration of
Tx_SbPortfolio2_Domain_Repository_CategoryRepository::findByTags(Tx_SbPortfolio2_Domain_Model_Tag
$tag) should be compatible with
Tx_SbPortfolio2_Domain_Repository_CoreRecordRepository::findByTags($tag,
array $portSetup) in
7/typo3conf/ext/sb_portfolio2/Classes/Domain/Repository/CategoryRepository.php
line 0 (More information)
Copied!

The error occurs if the function in a extended class has different arguments

Vhs ScriptViewHelper 

I'm getting this error after the update from TYPO3 v8.7 to v9.5 while rendering a template which contains JavaScript in the \FluidTYPO3\Vhs\ViewHelpers\Asset\ScriptViewHelper.

Upgrading from TYPO3 8 to 9 

After upgrading from TYPO3 v8 to v9 I got this error because PHP Cache is loading the files out of the old TYPO3 v8 source dir. After removing the old typo3_src-8.x.x dir or reloading the webserver the paths are correct.

PHP Warning: key() expects parameter 1 to be array, string given in ConditionMatcher.php 

PHP Warning: key() expects parameter 1 to be array, string given in
/home/host/data/www/typo3_src-9.5.9/typo3/sysext/backend/Classes/Configuration/TypoScript/ConditionMatching/ConditionMatcher.php
Copied!

It is happened because of my _GP('edit') coincided with $editStatement = GeneralUtility::_GP('edit');.

My solution: I change from "edit" to "redact", now I do not get this error.

PHP version to high 

Got this error because PHP version was higher (7.3.8) than supported by Ext:mask. No problems under PHP 7.2.21.

PHP Warning: preg_match(): Compilation failed: regular expression is too large 

"Uncaught TYPO3 Exception: #1476107295: PHP Warning: preg_match():
Compilation failed: regular expression is too large at offset 27 in
/html/typo3/typo3_src-9.5.22/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php
Copied!

Reason 

Ext. news: An editor created a text in a news-article (RTE) with only 1 (ONE) paragraph. In the raw data, there was no html-tag, only the beginning <p> and the ending </p> and the text had more than 3410 letters

Solution 

After splitting this ONE paragraph into 3 paragraphs, the above mentioned error was gone

Calling typo3/sysext/core/bin/typo3 scheduler:run from CLI: 

Array and string offset access syntax with curly braces is deprecated in
(...)/typo3_src-9.5.9/vendor/typo3/phar-stream-wrapper/src/PharStreamWrapper.php
line 479
Copied!

Solution 

Disable Debug Mode

Extension gridelements in debug mode 

When gridelements is enabled in debug mode, this error comes currently in v10.4.12 - disable the extension, when you are in debug mode and you are good to go.

PHP Warning: Undefined array key "<field>" in ControllerName.php 

Using TYPO3 v11 with PHP 8 this error occurs because of misconfiguration of an extension due to changes from PHP 7.4 to 8.x. It can happen when an extension is not migrated to work with PHP 8.x. Please contact the developer to fix this issue, or fix it by yourself if it is your own extension. (See below)

Solution 

Check your TCA configuration, inside the ctrl section columns might be referenced which have not been defined in columns, e.g. hidden.

Remove the offending entry in your ctrl section or add the missing column to columns.

PHP Warning: file_exists(): open_basedir restriction in effect. File(/typo3temp/assets/js/<something>.js) is not within the allowed path(s) 

Happens after Updating from TYPO3 v11.5.13 to v11.5.14. There is an issue: 98106. And a patch that can be applied. Should be resolved with the next bug fix version.

TYPO3\CMS\Core\Error\Exception 

PHP Warning: file_get_contents(.../public/fileadmin/<file>): failed to open stream: No such file or directory in .../public/typo3/sysext/core/Classes/Configuration/Loader/YamlFileLoader.php line 110
Copied!

Reason 

Missing file .../public/fileadmin/<file>

Solution 

Add the missing file.

PHP Warning: Array to string conversion in vendor/doctrine/dbal/lib/Doctrine/DBAL/Query/Expression/CompositeExpression.php line 174 

Reason 

You add some where constraints through an array with where() function and this function is waiting for string|CompositeExpression as parameter.

$constraints = [];
$constraints[] = $queryBuilder->expr()->eq('doktype', 100);
$constraints[] = $queryBuilder->expr()->in('categories.uid_local', $categories);

$result = $queryBuilder->select('pages.*')
    ->from('pages')
    ->where($constraints)
    ->execute()
    ->fetchAllAssociative();
Copied!

Solution 

You have to use the unpacking ellipsis ( ...) PHP token in order to add your constaints :

$result = $queryBuilder->select('pages.*')
    ->from('pages')
    ->where(...$constraints)
    ->execute()
    ->fetchAllAssociative();
Copied!

PHP Warning: Division by zero in /var/www/html/public/typo3/sysext/recordlist/Classes/RecordList/DatabaseRecordList.php line 1884 

This error occurred when editing certain IRRE data and when displaying the detail list.

Reason 

We add wrong TCA parameters :

'maxDBListItems' => 0,
'maxSingleDBListItems' => 0,
Copied!

which generated an error in the following code ( / $this->iLimit)

/**
 * @return string Navigation HTML
 */
protected function renderListNavigation($renderPart = 'top')
{
    $totalPages = ceil($this->totalItems / $this->iLimit);
    // Show page selector if not all records fit into one page
    if ($totalPages <= 1) {
        return '';
    }
    // ...
}
Copied!

Solution 

Check that you do not have a null value for the maxDBListItems and maxSingleDBListItems parameters.

TYPO3 12.4.19, 21.08.2024: PHP Warning: Undefined array key "renderType" 

PHP Warning: Undefined array key "renderType" in /var/www/html/vendor/typo3/cms-backend/Classes/Form/FormDataProvider/TcaSelectItems.php line 200
Copied!

Reason 

TCA Select field where the render type was accidently overridden

Solution 

Fix TCA

PHP 8: PHP Warning: Undefined array key "foo" 

PHP Warning: Undefined array key "foo" in /var/www/html/Bar.php line 200
Copied!

Reason 

The warning level for undefined array keys in PHP 8 is stronger than in PHP 7.

Solution 

Use the double question mark (null coalescing) operator to fix the PHP code.

before:

$value = $foo['bar']; 
Copied!

after:

$value = ($foo['bar'] ?? false);
Copied!

PHP 8: PHP Warning: Undefined array key "NEW_xxx" 

PHP Warning: Undefined array key "NEW_xxx" in typo3/sysext/frontend/Classes/Hooks/TreelistCacheUpdateHooks.php line 81
Copied!

Reason 

This error is shown when trying to create a page in TYPO3 < v13 if the pages table does not contain all necessary columns.

Solution 

Use the database analyzer in the Install Tool to create the missing columns.

TYPO3 Exception 1476107338 

TYPO3 Exception 1476107339 

TYPO3 Exception 1476107387 

TYPO3 Exception 1476107418 

TYPO3 Exception 1476107444 

TYPO3 Exception 1476107445 

TYPO3 Exception 1476107446 

TYPO3 Exception 1476107480 

TYPO3 Exception 1476107518 

TYPO3 Exception 1476107580 

TYPO3 Exception 1476107618 

TYPO3 Exception 1476107661 

TYPO3 Exception 1476107681 

TYPO3 Exception 1476107941 

[TYPO3 11.3] - [2021.08.13] 

TYPO3 cannot configure Dependency Injection for the plugin controller. 

Dependeny Injection may not be properly configured. Make sure that either the affected class or all classes (_defaults) have autoconfigure: true defined.

Bare minimum example:

Configuration/Services.yaml
services:
  _defaults:
    # ...
    autoconfigure: true
    # ...

# ...
Copied!

See Configuration in TYPO3 Explained.

[TYPO3 LTS 10] - [2021.05.05] 

Unable to call the controller configured in a plugin. 

TYPO3 creates the wrong class object for the controller due to using only the controller name (and not the fully qualified class name) in configurePlugin or registerModule.

Incorrect example:

ext_localconf.php
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'Examples', // $extensionName
    'HtmlParser', // plugin name
    // this is deprecated!
    ['ControllerName' => 'actionName'],
    // this is deprecated!
    ['ControllerName' => 'actionName']
);
Copied!

Use fully qualified class names as array keys in arguments $controllerActions and $nonCacheableControllerActions in configurePlugin or registerModule.

More details are in the changelog Deprecation: #87550 - Use controller classes when registering plugins/modules:

Correct example:

ext_localconf.php
\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'Examples', // $extensionName
    'HtmlParser', // plugin name
    // controller class name => action name
    [\T3docs\Examples\Controller\HtmlParserController::class => 'search',],
    [\T3docs\Examples\Controller\HtmlParserController::class => 'search',]
);
Copied!

TYPO3 Exception 1476108030 

TYPO3 Exception 1476108078 

TYPO3 Exception 1476108103 

TYPO3 Exception 1476108111 

TYPO3 Exception 1476108352 

TYPO3 Exception 1476108413 

TYPO3 Exception 1476108500 

TYPO3 Exception 1476108614 

TYPO3 Exception 1476108651 

TYPO3 Exception 1476108687 

TYPO3 Exception 1476108717 

TYPO3 Exception 1476109149 

TYPO3 Exception 1476109221 

TYPO3 Exception 1476109266 

TYPO3 Exception 1476109311 

TYPO3 Exception 1476109357 

TYPO3 Exception 1476109402 

TYPO3 Exception 1476109434 

TYPO3 Exception 1476109435 

TYPO3 Exception 1476109436 

TYPO3 Exception 1476109437 

TYPO3 Exception 1476109533 

TYPO3 Exception 1476109646 

TYPO3 Exception 1476109666 

TYPO3 Exception 1476109709 

TYPO3 Exception 1476122008 

TYPO3 Exception 1476122052 

TYPO3 Exception 1476122080 

TYPO3 Exception 1476122081 

TYPO3 Exception 1476122125 

TYPO3 Exception 1476122151 

TYPO3 Exception 1476122186 

TYPO3 Exception 1476122222 

TYPO3 Exception 1476122223 

TYPO3 Exception 1476122265 

TYPO3 Exception 1476122315 

TYPO3 Exception 1476122366 

TYPO3 Exception 1476122402 

TYPO3 Exception 1476171315 

TYPO3 Exception 1476199898 

TYPO3 Exception 1476216007 

TYPO3 Exception 1476216059 

TYPO3 Exception 1476216060 

TYPO3 Exception 1476340371 

TYPO3 Exception 1476362091 

TYPO3 Exception 1476362572 

TYPO3 Exception 1476557628 

TYPO3 Exception 1476958086 

TYPO3 Exception 1477070964 

TYPO3 Exception 1477071939 

TYPO3 Exception 1477082501 

TYPO3 Exception 1477082502 

TYPO3 Exception 1477082503 

TYPO3 Exception 1477083126 

TYPO3 Exception 1477083145 

TYPO3 Exception 1477217619 

TYPO3 Exception 1477512798 

TYPO3 Exception 1477520356 

TYPO3 Exception 1477679819 

TYPO3 Exception 1477679820 

TYPO3 Exception 1477680881 

TYPO3 Exception 1477688567 

TYPO3 Exception 1477699595 

TYPO3 Exception 1478096535 

TYPO3 Exception 1478098527 

TYPO3 Exception 1478100828 

TYPO3 Exception 1478104554 

TYPO3 Exception 1478105491 

TYPO3 Exception 1478105826 

FlexForm location was not found, TYPO3 12.0 

Data structure file "EXT:my_extension/Configuration/FlexForms/NotExisting.xml" could not be resolved to an existing file
Copied!

When opening a plugin in the backend and the referenced FlexForm is missing.

Solution 

Correct the path to the flexform in method ExtensionManagementUtility::addPiFlexFormValue(), which is usually called in EXT:my_extension/Configuration/TCA/Overrides/tt_content.php.

Using $_EXTKEY in configuration files in TYPO3 v9 and above 

This error can happen when using the variable $_EXTKEY in a TCA definition like Configuration/TCA/Overrides/tt_content.php without defining it. In TYPO3 versions before 8 the variable was automatically defined.

Solution 

Replace all occurences of $_EXTKEY with the extension's name or define the variable locally.

TYPO3 Exception 1478106090 

TYPO3 Exception 1478112411 

TYPO3 Exception 1478113471 

TYPO3 Exception 1478113873 

TYPO3 Exception 1478168512 

TYPO3 Exception 1478265661 

TYPO3 Exception 1478342067 

TYPO3 Exception 1478345642 

TYPO3 Exception 1478350806 

TYPO3 Exception 1478350835 

TYPO3 Exception 1478351691 

TYPO3 Exception 1478604742 

TYPO3 Exception 1478607036 

TYPO3 Exception 1478608245 

TYPO3 Exception 1478781081 

TYPO3 Exception 1478806566 

TYPO3 Exception 1479386729 

TYPO3 Exception 1479386990 

TYPO3 Exception 1479399227 

TYPO3 Exception 1479593622 

TYPO3 Exception 1480024933 

TYPO3 Exception 1480195405 

TYPO3 Exception 1480286138 

TYPO3 Exception 1480293084 

TYPO3 Exception 1480293085 

TYPO3 Exception 1480293086 

TYPO3 Exception 1480293087 

TYPO3 Exception 1480294720 

TYPO3 Exception 1480294721 

TYPO3 Exception 1480294722 

TYPO3 Exception 1480469086 

TYPO3 Exception 1480609491 

TYPO3 Exception 1480611208 

TYPO3 Exception 1480611252 

TYPO3 Exception 1480765571 

Data structure identifier must be set, typically by executing TcaFlexPrepare 

If you encounter this error during FlexForm integration:

Data structure identifier must be set, typically by executing TcaFlexPrepare data provider before
Copied!

it means that your FlexForm's XML structure is defective (broken, has errors, does not parse properly).

Missing prefix "FILE:" 

It occurs, for example, when you try to add a FlexForm file to a CE or plugin, but forget the prefix FILE::

EXT:my_extension/Configuration/TCA/Overrides/tt_content.php
/**
 * WRONG WAY to add a FlexForm file to a content element
 */
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPiFlexFormValue(
    '*',
    'EXT:my_extension/Resources/Private/FlexForm/MyFlexForm.xml',
    'textpic'
);

/**
 * CORRECT WAY to add a FlexForm file to a content element
 */
\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPiFlexFormValue(
    '*',
    'FILE:EXT:my_extension/Resources/Private/FlexForm/MyFlexForm.xml',
    'textpic'
);
Copied!

TYPO3 Exception 1481269826 

TYPO3 Exception 1481270871 

TYPO3 Exception 1481270923 

TYPO3 Exception 1481270961 

TYPO3 Exception 1481270987 

TYPO3 Exception 1481281404 

TYPO3 Exception 1481380393 

Might happen after upgrading to TYPO3 8.7 LTS or above.

Fix: Check the syntax in your FlexForms when using <displayCond>. See the displayCond in the TCA Reference:

Old: 

<displayCond>
   <AND>
      <numIndex>FIELD:switchableControllerActions:!=:Event->list</numIndex>
   </AND>
</displayCond>
Copied!

New: 

<displayCond>
   FIELD:switchableControllerActions:!=:Event->list
</displayCond>
Copied!

TYPO3 Exception 1481381058 

TYPO3 Exception 1481381950 

TYPO3 Exception 1481382954 

TYPO3 Exception 1481383660 

TYPO3 Exception 1481383888 

TYPO3 Exception 1481384123 

TYPO3 Exception 1481384784 

TYPO3 Exception 1481384947 

TYPO3 Exception 1481385173 

TYPO3 Exception 1481385695 

TYPO3 Exception 1481386239 

TYPO3 Exception 1481401543 

TYPO3 Exception 1481401892 

TYPO3 Exception 1481456806 

TYPO3 Exception 1481457277 

TYPO3 Exception 1481464101 

The cause of this error is the FlexForm file itself. Especially when plugin options are defined under display conditions within <AND> clause.

<settings.subtitle_align>
     <TCEforms>
         <label>Subtitle Alignment</label>
           <displayCond>
             <AND>
               FIELD:settings.subtitle:!=:0
             </AND>
           </displayCond>
       <!-- ....... -->
</settings.subtitle_align>
Copied!

If there is only a single condition, please avoid <AND> and get rid of the exception.

<settings.subtitle_align>
     <TCEforms>
         <label>Subtitle Alignment</label>
           <displayCond>
               FIELD:settings.subtitle:!=:0
           </displayCond>
       <!-- ....... -->
</settings.subtitle_align>
Copied!

TYPO3 Exception 1481467208 

TYPO3 Exception 1481469854 

TYPO3 Exception 1481483061 

TYPO3 Exception 1481485705 

TYPO3 Exception 1481488492 

TYPO3 Exception 1481492953 

TYPO3 Exception 1481496170 

TYPO3 Exception 1481634649 

TYPO3 Exception 1481647089 

Nesting select and group elements in flex form sections is not allowed with MM relations 

#1481647089: Invalid flex form data structure on field name "pi_flexform"
with element "foo" in section container "content": Nesting select and group
elements in flex form sections is not allowed with MM relations.
Copied!

Happens on TYPO3 v8 when using a multiRelation field inside a section container

This also happens with flux 8 when using a <flux:field.relation> tag. This has been fixed in flux 9.0.0.

TYPO3 Exception 1481885483 

TYPO3 Exception 1481885583 

TYPO3 Exception 1481889220 

Optimize MySQL tables scheduler task 

If you get this error when running the Optimize MySQL database tables (scheduler) task, try using the mysqli driver instead of pdo_mysql.

See: https://forge.typo3.org/issues/82686?next_issue_id=82682

TYPO3 Exception 1481895005 

TYPO3 Exception 1481895647 

TYPO3 Exception 1481896383 

TYPO3 Exception 1482234750 

TYPO3 Exception 1482235035 

TYPO3 Exception 1482242961 

TYPO3 Exception 1482250512 

TYPO3 Exception 1482251886 

TYPO3 Exception 1482251887 

TYPO3 Exception 1482251888 

TYPO3 Exception 1482251889 

TYPO3 Exception 1482394401 

Missing "type" in TCA of field 

Using form finishers 

Enabling in the Form plugin the "Override finisher settings" option may display this error for wrongly configured form finishers.

Solution 

Comment out one finisher at a time in the form definition file (*.form.yaml) to find the culprit.

Using TCEforms FlexForm 

The error message only gives an example table name and table field, because due to some migration to real names are not used in this error message. So you have to do some guesswork from which extension causes this error. Check the FlexForm file FlexForm_ds.xml (or another name) of the extension if there are TCEforms entries. In the child pair config a type must have been defined.

Example:

<config>
  <form_type>user</form_type>
  <userFunc><![CDATA[EXT:myextension/lib/class.tx_myextension_tceFunc.php:&tx_myextension_tceFunc->getCheckbox]]></userFunc>
  <checked>0</checked>
</config>
Copied!

You must use the type instead:

<type>user</type>
Copied!

TYPO3 Exception 1483114905 

TYPO3 Exception 1483292643 

TYPO3 Exception 1483823746 

TYPO3 Exception 1483890332 

TYPO3 Exception 1483890482 

11.3-master - [Date of solution] 

Situation 

I got this error on defining a node when the title was missing from the language file:

class ImportDataControl extends AbstractNode
{
    public function render()
    {
        $result = [
            'iconIdentifier' => 'import-data',
            'title' => $GLOBALS['LANG']->sL('LLL:EXT:examples/Resources/Private/Language/locallang_db.xlf:pages.importData'),
            'linkAttributes' => [
                'class' => 'importData ',
                'data-id' => $this->data['databaseRow']['somefield']
            ],
            'requireJsModules' => ['TYPO3/CMS/Examples/ImportData'],
        ];
        return $result;
    }
}
Copied!

Solution 

Add pages.importData to examples/Resources/Private/Language/locallang_db.xlf

TYPO3 Exception 1483891272 

TYPO3 Exception 1483971165 

TYPO3 Exception 1483971855 

TYPO3 Exception 1484050401 

TYPO3 Exception 1484066647 

TYPO3 Exception 1484071612 

TYPO3 Exception 1484071985 

TYPO3 13.4.0 - 11.11.2024 

Installation Overview 

  • TYPO3 13.4.0
  • "lavitto/typo3-form-to-database": "dev-update-v13"

The Issue 

Error upon trying to save a form in the Web > Form module into a path lying in an extension.

Solution 

https://gitlab.com/lavitto/typo3-form-to-database/-/issues/118

TYPO3 Exception 1484073571 

TYPO3 Exception 1484073878 

TYPO3 Exception 1484152906 

TYPO3 Exception 1484173035 

TYPO3 Exception 1484173650 

TYPO3 Exception 1484176136 

TYPO3 Exception 1484311516 

TYPO3 Exception 1484312516 

TYPO3 Exception 1484389971 

TYPO3 Exception 1484483040 

TYPO3 Exception 1484484612 

TYPO3 Exception 1484484613 

TYPO3 Exception 1484484619 

TYPO3 Exception 1484484620 

TYPO3 Exception 1484486383 

TYPO3 Exception 1484828466 

TYPO3 Exception 1484828468 

TYPO3 Exception 1484838560 

TYPO3 Exception 1485007097 

TYPO3 Exception 1485084419 

TYPO3 Exception 1485201279 

TYPO3 Exception 1485206970 

TYPO3 Exception 1485274618 

TYPO3 Exception 1485278693 

TYPO3 Exception 1485279226 

TYPO3 Exception 1485284352 

TYPO3 Exception 1485299408 

TYPO3 Exception 1485377267 

TYPO3 Exception 1485386982 

TYPO3 Exception 1485425530 

TYPO3 Exception 1485425531 

TYPO3 Exception 1485636499 

TYPO3 Exception 1485784246 

Extension 'chk_editor' installed, but not enabled 

Be sure the chk_editor extension is enabled.

TYPO3 Exception 1486045419 

TYPO3 Exception 1486045420 

TYPO3 Exception 1486155150 

The RecordLinkHandler expects identifier and uid as $parameter configuration 

#1486155150: The RecordLinkHandler expects identifier and uid as
$parameter configuration.
Copied!

Happened during upgrade to TYPO3 version 8 in the migration wizard.

Reason 

The Linkparser can't handle links to extension records, like

<link record:tt_news:1 - internal-link>News Record</link>
Copied!

Solution 

Search for records in database and change the link manually, then run the migration wizard again.

TYPO3 Exception 1486155151 

TYPO3 Exception 1486233164 

This error can happen, when a record, containing a FAL relation, is about to be translated into another language. Possible reasons:

  1. The FAL data was created before any languages were created. In that case just delete the original FAL data and recreate it.
  2. The TCA is missing an "appearance" configuration, for example:
[
    'config' => [
        // ...
        'appearance' => [
            'showPossibleLocalizationRecords' => true,
            'showRemovedLocalizationRecords' => true,
            'showAllLocalizationLink' => true,
            'showSynchronizationLink' => true,
            'enabledControls' => [
                'info' => false,
            ]
        ]
]
Copied!

Check the TCA Reference for examples, like here: IRRE / inline examples

TYPO3 Exception 1486313971 

TYPO3 Exception 1486325248 

TYPO3 Exception 1486676313 

TYPO3 Exception 1486676314 

TYPO3 Exception 1486676358 

TYPO3 Exception 1487192370 

TYPO3 Exception 1487326416 

This error happened on deleting content elements. We had several entries in table tx_solr_indexqueue_item with "root" pointing to a deleted page. Clearing the Index Queue did not delete these entries and not solve the problem. Truncating the table and adding all content anew to the queue did solve it for me.

TYPO3 Exception 1487849315 

TYPO3 Exception 1487849326 

TYPO3 Exception 1487944884 

TYPO3 Exception 1488130499 

TYPO3 Exception 1488634845 

TYPO3 Exception 1489238980 

TYPO3 Exception 1489260796 

TYPO3.CMS.Form.prototypes.standard does not exist within the configuration 

#1489260796: TYPO3.CMS.Form.prototypes.standard does not exist within
the configuration
Copied!

This happens when you create a form based on the TYPO3 standard form and call it on a page in the frontend, but you forgot to include the extension template in TypoScript settings.

TYPO3 Exception 1489272978 

TYPO3 Exception 1489412790 

TYPO3 Exception 1489413379 

TYPO3 Exception 1489413538 

TYPO3 Exception 1489486301 

TYPO3 Exception 1489486302 

TYPO3 Exception 1489593090 

TYPO3 Exception 1489593098 

TYPO3 Exception 1489593099 

TYPO3 Exception 1489751361 

TYPO3 Exception 1489751362 

TYPO3 Exception 1489751363 

TYPO3 Exception 1490360772 

TYPO3 Exception 1490371322 

TYPO3 Exception 1490989149 

TYPO3 Exception 1490989449 

TYPO3 Exception 1490989659 

TYPO3 Exception 1490990031 

TYPO3 Exception 1491130170 

TYPO3 Exception 1491130459 

TYPO3 Exception 1491130460 

TYPO3 Exception 1494579849 

TYPO3 Exception 1494878863 

TYPO3 Exception 1496402460 

TYPO3 Exception 1496496724 

TYPO3 Exception 1497332874 

YamlParseException YAML file $fileName could not be parsed 

::
YAML file "/path/typo3conf/sites/my-site/config.yaml" could not be parsed into valid syntax, probably empty?

This error can happen in the TYPO3 backend on the page configuration.

Solution 

Use a yaml syntax checker tool for for config.yaml file.

TYPO3 Exception 1498144052 

Parameter $extensionName cannot be empty 

Parameter $extensionName cannot be empty if a fully-qualified key is not
specified.
Copied!

Error happended in a new installations of TYPO3 v8.7.4 (Aug 2017) after installing the media extension.

TYPO3 Exception 1498802253 

TYPO3 Exception 1498924810 

TYPO3 Exception 1499710202 

TYPO3 Exception 1499710203 

TYPO3 Exception 1499777261 

TYPO3 Exception 1499777330 

TYPO3 Exception 1499789246 

TYPO3 Exception 1499789259 

TYPO3 Exception 1499789384 

TYPO3 Exception 1499789433 

TYPO3 Exception 1499803909 

TYPO3 Exception 1500060252 

TYPO3 Exception 1500306488 

TYPO3 Exception 1500492001 

TYPO3 Exception 1500496068 

TYPO3 Exception 1500557309 

TYPO3 Exception 1500735983 

TYPO3 Exception 1500958070 

TYPO3 Exception 1501415721 

TYPO3 Exception 1501416365 

TYPO3 Exception 1501419367 

TYPO3 Exception 1501509548 

TYPO3 Exception 1501509605 

TYPO3 Exception 1501509738 

TYPO3 Exception 1501510168 

TYPO3 Exception 1501781453 

TYPO3 Exception 1501781454 

TYPO3 Exception 1501942151 

TYPO3 Exception 1501944076 

TYPO3 Exception 1502282283 

TYPO3 Exception 1502721731 

TYPO3 Exception 1502721732 

TYPO3 Exception 1502800555 

TYPO3 Exception 1502987245 

Go to TYPO3 Install tool -> All Configurations -> [encryptionKey] and add an encryptionKey.

http://blog.joergboesche.de/typo3-cms-encryption-key-was-empty-exception

TYPO3 Exception 1503060454 

TYPO3 Exception 1504793406 

TYPO3 Exception 1504793407 

TYPO3 Exception 1504804727 

[10.4] - [9th April 2021] 

Situation 

The TYPO3 backend throws an exception, when I click on Extensions.

(1/1) #1504804727 RuntimeException

This module "tools_ExtensionmanagerExtensionmanager" is only available as system maintainer
in /foo/bar/typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php line 464
Copied!

Solution 

The currently logged in backend user has been removed from the system maintainers list. Ask for access to be granted again by a backend user who is a system maintainer. Any system maintainer may grant access to other users.

TYPO3 Exception 1504814459 

TYPO3 Exception 1504870805 

TYPO3 Exception 1504870806 

TYPO3 Exception 1504871830 

TYPO3 Exception 1504972433 

TYPO3 Exception 1504972434 

TYPO3 Exception 1505055445 

TYPO3 Exception 1505215756 

TYPO3 Exception 1505216027 

TYPO3 Exception 1505304205 

TYPO3 Exception 1505304206 

TYPO3 Exception 1505407269 

TYPO3 Exception 1505563556 

TYPO3 Exception 1505564888 

TYPO3 Exception 1505567462 

TYPO3 Exception 1505637427 

TYPO3 Exception 1505647681 

TYPO3 Exception 1505647737 

TYPO3 Exception 1505687700 

TYPO3 Exception 1507321200 

TYPO3 Exception 1507321291 

TYPO3 10.4.13 - 01.04.2021 

Situation 

This happened when installing an old extension that still dependet on $_EXTKEY beeing automatically set.

Solution 

Patched the extension.

TYPO3 Exception 1507321297 

TYPO3 Exception 1507321535 

TYPO3 Exception 1507321542 

TYPO3 Exception 1507321596 

TYPO3 Exception 1507645348 

TYPO3 Exception 1507645349 

TYPO3 Exception 1507645381 

RuntimeException: Object Name String, contains invalid character 

#1507645381 RuntimeException
Line 0: Object Name String, ".." contains invalid character "...".
Must be alphanumeric or one of: "_:-\."
Copied!

Cause of error: BOM in ext_conf_template.txt 

This exception got thrown in TYPO3 9.5.5, when the ext_conf_template.txt file contained a BOM (byte order mark) character at beginning of the file and the Extension Configuration was fetched using the ExtensionConfiguration API.

Fix error 

Fix, see these resources:

TYPO3 Exception 1507645417 

Object Name String, "..." was not followed by any operator 

This happened in TYPO3 9.3.3:

Object Name String, "exclude.tt_products_cat_language" was not followed
by any operator, =<>({
Copied!

Solution: 

The file ext_conf_template.txt of the extension contains a missing equation sign (=).

Change it into this format:

TYPO3 Exception 1507645445 

Object Name String, was not followed by any operator 

#1507645445 RuntimeException Line 2: Object Name String,
"Enables" was not followed by any operator, =<>({**
Copied!

This might habben when there is an error in the TypoScript. For example the following has a line break where there should be none:

Wrong:

Correct:

TYPO3 Exception 1507645489 

TYPO3 Exception 1507845662 

TYPO3 Exception 1508912031 

TYPO3 Exception 1508916031 

TYPO3 Exception 1508916185 

TYPO3 Exception 1508916285 

TYPO3 Exception 1509296032 

TYPO3 Exception 1509296606 

TYPO3 Exception 1509303611 

TYPO3 Exception 1509303783 

TYPO3 Exception 1509654728 

[TYPO3 10.4.17] - [2021.06.15] 

Situation 

The exception was thrown when trying to activate an extension which utilized \TYPO3\CMS\Core\Configuration\ExtensionConfiguration->get() to load its configurations. The configuration file was missing.

Solution 

Make sure a configuration file exists or properly catch the exception: https://docs.typo3.org/m/typo3/reference-coreapi/10.4/en-us/ExtensionArchitecture/ConfigurationOptions/Index.html

TYPO3 Exception 1509715852 

TYPO3 Exception 1509741907 

TYPO3 Exception 1509741908 

TYPO3 13.4 - 2025-04-23 

Installation overview 

A content element has a relation to a custom record which itself has a relation to one image. When now using the record-transformation data processor and reference {data.record.image} in a <f:image> tag, the following exception is thrown:

Unable to render image uri in "tt_content:140": Supplied file must be File or 
FileReference, TYPO3\CMS\Core\Resource\Collection\LazyFileReferenceCollection given.
Copied!

The issue 

TYPO3 provides a collection by default which cannot be resolved by the ImageViewHelper.

Solution 

Add 'relationship' => 'oneToOne' (or one of the other values if appropriate) to the config section in the TCA configuration of the according field. See: relationship

TYPO3 Exception 1509741909 

TYPO3 Exception 1509741910 

TYPO3 Exception 1509741911 

Folder "/testing/foo/file.png/" does not exist 

(1/2) #1509741911 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
Folder "/testing/foo/file.png/" does not exist.
in /var/www/site/htdocs/typo3_src/typo3/sysext/fluid/Classes/ViewHelpers/ImageViewHelper.php line 175
Copied!

This exception happens if an image file should be rendered in Fluid, but failed because the file does not exist:

A simple workaround is to (re)create the image/folder at the desired location or to change the path in the used extension.

TYPO3 Exception 1509741912 

Insights from the code 

A comment in the code associated with this exception explains that it is “thrown if a file has been replaced with a folder.”

Added in TYPO3 v9.0 • Confirmed present in TYPO3 v13.1

Supplied file object type ProcessedFile for must be File or FileReference 

Concerned Version: TYPO3 Version 9.2.1

Related issues:

When moving some files in the File-module with the clipboard this Error Message is shown:

#1509741912: Supplied file object
type TYPO3\CMS\Core\Resource\ProcessedFile for must be
File or FileReference.
Copied!

TYPO3 Exception 1509741913 

TYPO3 Exception 1509741914 

Insights from the code 

A comment in the code associated with this exception explains that it is “thrown if file storage does not exist.”

Added in TYPO3 v6.3 • Still present in TYPO3 v13.1

TYPO3 11.5.0 - ext:news dev-master - 8.10.2021 

Installation Overview 

TYPO3 11.5.0 with composer and ext:news dev-master using the default news templates that come bundled with the extension.

The Issue 

The following error when displaying a page with the news plugin:

(1/2) #1509741914 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
File /typo3conf/ext/news/Resources/Public/Images/dummy-preview-image.png does not exist.
Copied!

The dummy image is present in the path.

Solution 

As a workaround set the following TypoScript:

plugin.tx_news.settings.displayDummyIfNoMedia = 1
Copied!

For further informatin, visit https://github.com/georgringer/news/issues/1589

TYPO3 13.4.9 - Add image with custom extension 

Context 

Have an image in a custom extension and want to display it with Fluid Template.:

<f:image src="EXT:my_ext/Resources/Public/MyImage.svg" />
Copied!

The Issue 

The following error is shown when the Fluid Template is used:

(1/2) #1509741914 TYPO3Fluid\Fluid\Core\ViewHelper\Exception
File typo3 Unable to render image tag in "tt_content:6": _assets/0c22fd3d95c93dc31098cc8d4b1d7232/MyImage.svg File  does not exist.
Copied!

Solution 

Add this to composer.json:

"extra": {
   "typo3/cms": {
      "web-dir": "public"
   }
}
Copied!

TYPO3 Exception 1509977699 

TYPO3 Exception 1510906768 

TYPO3 Exception 1511792197 

TYPO3 Exception 1511945040 

TYPO3 Exception 1511950673 

TYPO3 Exception 1512578002 

TYPO3 Exception 1512582637 

TYPO3 Exception 1512582753 

TYPO3 Exception 1512582929 

TYPO3 Exception 1512583307 

TYPO3 Exception 1512584488 

TYPO3 Exception 1515073585 

TYPO3 Exception 1515075192 

TYPO3 Exception 1516531195 

TYPO3 Exception 1516708789 

TYPO3 Exception 1516821342 

TYPO3 Exception 1517174114 

TYPO3 Exception 1517949792 

TYPO3 Exception 1517949793 

TYPO3 Exception 1517949794 

TYPO3 Exception 1518042216 

TYPO3 Exception 1518448686 

No suitable request handler found 

The following exception may be displayed since TYPO3 v9 during login:

#1518448686 TYPO3\CMS\Core\Exception
No suitable request handler found.
Copied!

Reasons 

The password for installation tool is missing in LocalConfiguration.php. TYPO3 tries to find out the encryption type by analyzing the password in order to allow logins after migrating to an other encrypting algorithm.

Solutions 

See Recovering from a corrupt or missing install tool password.

TYPO3 Exception 1518472181 

TYPO3 Exception 1518472189 

Path is not found (TYPO3 version 9.5) 

The error is shown if the requested page can't be found for one of the following or further reasons:

  • Slugs are defined for pages but there is a fault in the definitions (for example a trailing slash or the path is broken).
  • This may happen with a PersistedAliasMapper definition if the record you try to decode is stored outside of your site.
  • If there are several domains defined in one TYPO3-installation and a page includes a link to a page that is in another domain but still to another page inside the TYPO3-installation.
  • If there are several domains defined in a TYPO3-installation and one some configurations share the same rootPageId

Request parameters could not be validated 

Some parameters in your url should not be part of the cHash generation. You must add them to the cacheHash excluded parameters list in the install Tool. For example the eID parameter for Ajax calls should not be part of the cHash generation.

How to fix cross-domain problems (TYPO3 version 9.5)? 

  • Create a site-configuration for the rootpage of each domain in the TYPO3-installation's pagetree.

How to fix issues regarding multiple site configurations with the same rootPageId (TYPO3 version 9.5)? 

  • Remove the offending configuration or consolidate the configurations in one file

TYPO3 Exception 1518472195 

TYPO3 Exception 1518472235 

TYPO3 Exception 1518472245 

TYPO3 Exception 1518472252 

TYPO3 Exception 1518472257 

TYPO3 Exception 1518558797 

TYPO3 Exception 1518785877 

TYPO3 Exception 1518787887 

TYPO3 Exception 1519239265 

TYPO3 Exception 1519490105 

TYPO3 Exception 1519490112 

TYPO3 Exception 1519739203 

TYPO3 Exception 1519788775 

Using extension filefill < version 3 

I received this error when using the new style configuration of filefill

$GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['filefill']['storages'][1] = [
      'placeholder' => true,
      [
          'identifier' => 'domain',
          'configuration' => 'https://www.example.de/',
      ],
      [
          'identifier' => 'placeholder',
      ]
];
Copied!

with a too old version of filefill (<3), upgrading filefill to 3.2.1 did the trick for me.

TYPO3 Exception 1519931815 

Unresolved extension-dependencies 

This error might be caused by unresolved extension dependencies. More detailed error-message could be retrieved using extension "typo3_console".

Executing following command on command line:

typo3cms install:generatepackagestates
Copied!

See the TYPO3 console manual <https://docs.typo3.org/p/helhum/typo3-console/master/en-us/Introduction/Index.html> for further information.

TYPO3 Exception 1519978105 

TYPO3 Exception 1519998923 

TYPO3 Exception 1520109807 

TYPO3 Exception 1520117054 

TYPO3 Exception 1520117245 

TYPO3 Exception 1520169691 

TYPO3 Exception 1520170845 

TYPO3 Exception 1520170846 

TYPO3 Exception 1520170847 

TYPO3 Exception 1520170848 

TYPO3 Exception 1520175002 

TYPO3 Exception 1520176318 

TYPO3 Exception 1520370364 

TYPO3 Exception 1520756142 

TYPO3 Exception 1520756466 

TYPO3 Exception 1520756623 

TYPO3 Exception 1520757000 

TYPO3 Exception 1520886092 

TYPO3 Exception 1520886234 

TYPO3 Exception 1521030950 

TYPO3 Exception 1521032781 

TYPO3 Exception 1521190675 

TYPO3 Exception 1521220141 

TYPO3 Exception 1521220142 

TYPO3 Exception 1521220491 

TYPO3 Exception 1521293813 

TYPO3 Exception 1521293814 

TYPO3 Exception 1521555037 

TYPO3 Exception 1521555177 

TYPO3 Exception 1521555340 

TYPO3 Exception 1521561148 

TYPO3 Exception 1521561226 

TYPO3 Exception 1521565182 

TYPO3 Exception 1521573955 

TYPO3 Exception 1521668882 

TYPO3 Exception 1521668982 

TYPO3 Exception 1521716622 

No site found in rootline of page 123 

#1521716622 TYPO3\CMS\Core\Exception\SiteNotFoundException
No site found in rootline of page 123
Copied!

When a page of type shortcut with external URL is created the slug that is automatically created looks like this: "/https//wwwfacebookcom/...".

Changing this slug to something like "/my-company" is raising the error-message shown on the screenshot.

TYPO3 Exception 1521716628 

TYPO3 Exception 1521719709 

TYPO3 Exception 1521726421 

TYPO3 Exception 1521783937 

TYPO3 Exception 1521788518 

TYPO3 Exception 1521789306 

TYPO3 Exception 1521789455 

TYPO3 Exception 1522491300 

TYPO3 Exception 1522491734 

TYPO3 Exception 1522493094 

TYPO3 Exception 1522493095 

TYPO3 Exception 1522493097 

TYPO3 Exception 1522494737 

TYPO3 Exception 1522495102 

TYPO3 Exception 1522495914 

TYPO3 Exception 1522495954 

TYPO3 Exception 1522771624 

TYPO3 Exception 1522771632 

TYPO3 Exception 1522771640 

TYPO3 Exception 1522826413 

TYPO3 Exception 1522826609 

TYPO3 Exception 1522866183 

TYPO3 Exception 1522866184 

TYPO3 Exception 1522959186 

TYPO3 Exception 1522959187 

TYPO3 Exception 1522959188 

TYPO3 Exception 1522960188 

Bug in LTS 9 (fixed) 

https://forge.typo3.org/issues/86623

Faulty configuration for ext:crawler 

The DB table tx_crawler_configuration contains a faulty configuration. This may occur when upgrading from LTS 8 to versions 9 and 10.

TYPO3 Exception 1522965188 

TYPO3 Exception 1523971295 

TYPO3 Exception 1524063160 

TYPO3 Exception 1524209729 

TYPO3 Exception 1524502548 

TYPO3 Exception 1524502549 

TYPO3 Exception 1524502550 

TYPO3 Exception 1524502666 

TYPO3 Exception 1524526354 

TYPO3 Exception 1524684442 

TYPO3 Exception 1524684462 

TYPO3 Exception 1525342106 

TYPO3 Exception 1526013723 

TYPO3 Exception 1526042080 

TYPO3 Exception 1526042081 

TYPO3 Exception 1526042082 

TYPO3 Exception 1526042084 

TYPO3 Exception 1526052118 

TYPO3 Exception 1526127158 

TYPO3 Exception 1526128259 

TYPO3 Exception 1526129969 

TYPO3 Exception 1526134901 

TYPO3 Exception 1526136338 

TYPO3 Exception 1526136362 

TYPO3 Exception 1526695869 

TYPO3 Exception 1526695870 

TYPO3 Exception 1526695874 

TYPO3 Exception 1527186844 

TYPO3 Exception 1527186845 

TYPO3 Exception 1527432330 

TYPO3 Exception 1527777641 

TYPO3 Exception 1527777868 

TYPO3 Exception 1527778767 

TYPO3 Exception 1527779447 

TYPO3 Exception 1527780439 

TYPO3 Exception 1527854474 

TYPO3 Exception 1528538222 

TYPO3 Exception 1528538252 

TYPO3 Exception 1528538322 

TYPO3 Exception 1528538323 

TYPO3 Exception 1528538324 

TYPO3 Exception 1528578401 

TYPO3 Exception 1528578402 

TYPO3 Exception 1528588035 

TYPO3 Exception 1528588036 

TYPO3 Exception 1528588037 

TYPO3 Exception 1528591502 

TYPO3 Exception 1528591585 

TYPO3 Exception 1528591586 

TYPO3 Exception 1528625039 

TYPO3 Exception 1528631951 

TYPO3 Exception 1528631952 

TYPO3 Exception 1528631953 

TYPO3 Exception 1528631954 

TYPO3 Exception 1528633965 

TYPO3 Exception 1528633966 

TYPO3 Exception 1528633967 

TYPO3 Exception 1528634966 

TYPO3 Exception 1528636941 

TYPO3 Exception 1528638085 

TYPO3 Exception 1528822131 

TYPO3 Exception 1528822485 

TYPO3 Exception 1528822486 

TYPO3 Exception 1529299833 

TYPO3 Exception 1529710560 

TYPO3 Exception 1529996567 

TYPO3 Exception 1530030672 

TYPO3 Exception 1530030673 

TYPO3 Exception 1530103998 

TYPO3 Exception 1530103999 

TYPO3 Exception 1530169746 

TYPO3 Exception 1530169814 

TYPO3 Exception 1530169845 

TYPO3 Exception 1530169955 

TYPO3 Exception 1530281201 

TYPO3 Exception 1530281202 

TYPO3 Exception 1530448504 

TYPO3 Exception 1530827194 

TYPO3 Exception 1530827195 

TYPO3 Exception 1531160649 

TYPO3 Exception 1531216505 

TYPO3 Exception 1531235592 

TYPO3 Exception 1531235715 

TYPO3 Exception 1531235777 

TYPO3 Exception 1531336156 

TYPO3 Exception 1532528246 

TYPO3 Exception 1532528267 

TYPO3 Exception 1532861423 

TYPO3 Exception 1533159150 

TYPO3 Exception 1533290762 

TYPO3 Exception 1533294109 

TYPO3 Exception 1533294113 

TYPO3 Exception 1533294116 

TYPO3 Exception 1533294120 

TYPO3 Exception 1533818569 

TYPO3 Exception 1533818591 

InvalidPasswordHashException: No implementation found that handles given hash 

The following exception may bubble up since TYPO3 v9 during login:

#1533818591 TYPO3\CMS\Core\Crypto\PasswordHashing\InvalidPasswordHashException
No implementation found that handles given hash. This happens if the
stored hash uses a mechanism not supported by current server.
Copied!

Explanation 

A frontend user, a backend user or the install tool password hash is stored using a mechanism not supported by the current server. The login process can not compare the given password with the stored hash.

Reasons 

This typically happens if a TYPO3 upgrade is performed on a system that supports the default hash mechanism argon2i, passwords in the database and/or the install tool password is updated to use this hash, and the system is then deployed to a system that does not support argon2i.

Solutions 

Please see Password hashing troubleshooting.

More information 

TYPO3 Exception 1533820041 

TYPO3 Exception 1533820194 

TYPO3 Exception 1533820281 

TYPO3 Exception 1533822084 

Argon2iPasswordHash is not available 

The following exception may bubble up since TYPO3 v9 during login:

#1533822084 TYPO3\CMS\Core\Crypto\PasswordHashing\InvalidPasswordHashException
Configured default hash method
TYPO3\CMS\Core\Crypto\PasswordHashing\Argon2iPasswordHash is not
available. If the instance has just been upgraded, please log in to the
standalone install tool at typo3/install.php to fix this.
Copied!

Explanation 

If an instance has just been upgraded and if argon2i hash mechanism is not available locally, the default backend will still try to upgrade a given user password to argon2i if the install tool has not been executed once.

Reasons 

This typically happens only if a system has just been upgraded and a backend login is performed before the install tool has executed silent upgarde wizards.

Solutions 

Please see Password hashing troubleshooting.

More information 

TYPO3 Exception 1533893665 

TYPO3 Exception 1533894782 

TYPO3 Exception 1533899612 

TYPO3 Exception 1533899613 

TYPO3 Exception 1533899614 

TYPO3 Exception 1533902002 

TYPO3 Exception 1533903544 

TYPO3 Exception 1533903545 

TYPO3 Exception 1533931298 

TYPO3 Exception 1533931299 

TYPO3 Exception 1533931329 

TYPO3 Exception 1533931330 

TYPO3 Exception 1533931343 

TYPO3 Exception 1533931350 

TYPO3 Exception 1533931351 

TYPO3 Exception 1533931352 

TYPO3 Exception 1533931354 

TYPO3 Exception 1533931374 

TYPO3 Exception 1533931380 

TYPO3 Exception 1533931388 

TYPO3 Exception 1533931395 

TYPO3 Exception 1533931402 

TYPO3 Exception 1533931423 

TYPO3 Exception 1533939251 

TYPO3 Exception 1533940454 

TYPO3 Exception 1533948312 

TYPO3 Exception 1533948733 

TYPO3 Exception 1533949053 

TYPO3 Exception 1533950385 

TYPO3 Exception 1533950622 

TYPO3 Exception 1533988846 

TYPO3 Exception 1533989414 

TYPO3 Exception 1533989428 

TYPO3 Exception 1533989434 

TYPO3 Exception 1534484203 

TYPO3 Exception 1534682840 

TYPO3 Exception 1534710048 

Exeption is thrown when click in Backend on Module "Sites" 

This error happens after upgrading from TYPO3 8 or 9 or after importing a database from an older TYPO3 instance. It happens on trying to create a site configuration. The error is cause by Missing database tables

Solution: 

Go to Admin Tools -> Maintenance -> Database Compare and bring the database schema up to date.

Exception is thrown when trying to edit records in BE 

Error in TCA configuration 

Might be caused by a TCA definition of a table other then pages using the following:

'displayCond' => 'USER:'
   . \\TYPO3\CMS\Core\Compatibility\PseudoSiteTcaDisplayCondition::class .
   '->isInPseudoSite:pages:false'
Copied!

is used for records. The pseudo site check should only be used for pages. Remove or adopt display condition. Problem occurred for example in tt_address >= 5.0.0, < 5.2.0 for field slug.

The error may only occur if you edit specific records as a problem only arises if a page(!) with the uid of the record(!) does not exist.

Extension news or tt_address needs updates 

Some versions of the extensions news and tt_address can cause this error on opening records like sys_category. Updating the extension to the most recent version can help. For example updating News to version 8.4.1 or newer fixes this issue.

TYPO3 Exception 1534951024 

TYPO3 Exception 1534951025 

TYPO3 Exception 1534952559 

TYPO3 Exception 1534962573 

TYPO3 Exception 1535055415 

TYPO3 Exception 1535137045 

TYPO3 Exception 1535301628 

TYPO3 Exception 1535379534 

TYPO3 Exception 1535406600 

TYPO3 Exception 1535462423 

TYPO3 Exception 1535462429 

TYPO3 Exception 1535462452 

TYPO3 Exception 1535462454 

TYPO3 Exception 1535462458 

TYPO3 Exception 1535576053 

TYPO3 Exception 1535578522 

TYPO3 Exception 1535578569 

TYPO3 Exception 1535803185 

TYPO3 Exception 1535803186 

TYPO3 Exception 1535835666 

TYPO3 Exception 1536248936 

TYPO3 Exception 1536248937 

TYPO3 Exception 1536322935 

TYPO3 Exception 1536407967 

TYPO3 Exception 1536819047 

TYPO3 Exception 1536950931 

TYPO3 Exception 1537158043 

TYPO3 Exception 1537209128 

TYPO3 Exception 1537273550 

TYPO3 Exception 1537277133 

TYPO3 Exception 1537277134 

TYPO3 Exception 1537277136 

TYPO3 Exception 1537277143 

TYPO3 Exception 1537277144 

TYPO3 Exception 1537277153 

TYPO3 Exception 1537277154 

TYPO3 Exception 1537277163 

TYPO3 Exception 1537277164 

TYPO3 Exception 1537277173 

TYPO3 Exception 1537277174 

TYPO3 Exception 1537277175 

TYPO3 Exception 1537277222 

TYPO3 Exception 1537298284 

TYPO3 Exception 1537348076 

TYPO3 Exception 1537348083 

TYPO3 Exception 1537356346 

TYPO3 Exception 1537613247 

TYPO3 Exception 1537633463 

OutOfRangeException: Hash not resolvable 

If you have a problem with an OutOfRangeException with the message "Hash not resolvable" this is a bug reported here: https://forge.typo3.org/issues/87688

TYPO3 Exception 1537696771 

TYPO3 Exception 1537696772 

TYPO3 Exception 1537962752 

TYPO3 Exception 1538055997 

TYPO3 Exception 1538057402 

TYPO3 Exception 1538079481 

TYPO3 Exception 1538079482 

TYPO3 Exception 1538152266 

TYPO3 Exception 1538152269 

TYPO3 Exception 1538156220 

TYPO3 Exception 1538160231 

TYPO3 Exception 1538326790 

TYPO3 Exception 1538326791 

TYPO3 Exception 1538327508 

TYPO3 Exception 1538327509 

TYPO3 Exception 1538327510 

TYPO3 Exception 1538331833 

TYPO3 Exception 1538331852 

TYPO3 Exception 1538335671 

TYPO3 Exception 1538370377 

TYPO3 Exception 1538389998 

TYPO3 Exception 1538389999 

TYPO3 Exception 1538390230 

TYPO3 Exception 1540246570 

TYPO3 13.4: No Content Object definition found [21.10.2024] 

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()
Copied!

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
}
Copied!

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
}
Copied!

You have removed Typoscript by Conditon? 

For example you have used this:

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

lib.login >

[global]
Copied!

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]
Copied!

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" />
Copied!

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" />
Copied!

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.

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.

TYPO3 Exception 1540548015 

TYPO3 Exception 1543617278 

TYPO3 Exception 1544172838 

RuntimeException: Error handler could not fetch error page 

::
RuntimeException: Error handler could not fetch error page(due to no internet connection or protected)

Migrating from Fluidpages to Flux 

If this exception appears while migrating from Fluidpages to Flux, verify that the corresponding Flux-TS is included.

404 error handler set to "Display content from page" (TYPO3 9.x) 

(1/1) #1544172838 Error handler could not fetch error pageuntimeException
Error handler could not fetch error page
"https://project.localdomain.vm/http-error-404",
reason: cURL error 51: SSL: no alternative certificate subject name
matches target host name 'project.localdomain.vm' (see
https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Copied!

When you have set your 404-error-handler to "Display content from page" on a development domain, cURL can't call the target page when the certificate isn't valid.

Solution: test again without SSL or test on a staging system with a properly installed valid certificate.

Self signed certificate problem 

(1/1) #1544172838 RuntimeException  Error handler could not fetch
error page "https://example.de/startseite", reason: cURL error 60:
SSL certificate problem: self signed certificate (see
https://curl.haxx.se/libcurl/c/libcurl-errors.html)
Copied!

You can avoid this exception with $GLOBALS['TYPO3_CONF_VARS']['HTTP']['verify'] = false;

TYPO3 Exception 1544172839 

TYPO3 Exception 1544278754 

TYPO3 Exception 1544278778 

TYPO3 Exception 1545260108 

TYPO3 Exception 1545260109 

TYPO3 Exception 1546632293 

TYPO3 12.4 - 2025-04-02 

The TCA definition for the field was missing.

TYPO3 10.4.14 - 2021-04-02 

Situation 

When validating a controller's argument, the following exception is thrown:

#1546632293 RuntimeException Could not get value of property "Site\Site\Domain\Model\Order::cart",
make sure the property is either public or has a getter getCart(), a hasser hasCart() or an isser isCart().
Copied!

But there is a public function getCart(); defined in the class.

Solution 

In Model, the property is nullable:

protected ?Cart $cart;
Copied!

Add explicitly a default value:

protected ?Cart $cart = null;
Copied!

Read more information on this behaviour.

TYPO3 11.5.31 - 2023-09-29 

Situation 

When validating a controller's argument, the following exception is thrown:

#1546632293 RuntimeException Could not get value of property "Site\Site\Domain\Model\Booking::startdate",
make sure the property is either public or has a getter getStartdate(), a hasser hasStartdate() or an isser isStartdate().
Copied!

But there is a public function getStartdate(): DateTime defined in the class.

Solution 

In the getter, the return value has to be nullable:

public function getStartdate(): ?DateTime
Copied!

TYPO3 Exception 1547675557 

TYPO3 Exception 1547675594 

TYPO3 Exception 1548052629 

TYPO3 Exception 1549404144 

TYPO3 Exception 1549446998 

TYPO3 Exception 1549988537 

TYPO3 Exception 1550060977 

TYPO3 Exception 1550092654 

A registered extension for the service "backend.routes" requires the service 

Uncaught TYPO3 Exception #1550092654: A registered extension for the
service "backend.routes" requires the service to be available, which is
missing.
Copied!

TYPO3 Exception 1550247164 

TYPO3 Exception 1550302554 

TYPO3 Exception 1550351445 

TYPO3 Exception 1550670118 

TYPO3 Exception 1551950301 

TYPO3 10.4 - 2023-01-26 

The Issue 

  • "Hash has to be non-empty string."
  • Entries in sys_file table point to non-existing files on the server

Solution 

  • Ensure that the files contained in your fileadmin/ tree are consistent with your sys_file database relations.

    You may either be missing referenced files in fileadmin/, or sys_file lists outdated entries.

    The CLI command typo3 cleanup:missingfiles may help synchronizing your database to the current fileadmin/ structure.

TYPO3 Exception 1555303496 

TYPO3 Exception 1555850106 

TYPO3 Exception 1555944032 

TYPO3 Exception 1556282257 

TYPO3 Exception 1556367071 

TYPO3 Exception 1557839801 

TYPO3 Exception 1558354033 

TYPO3 Exception 1559794913 

TYPO3 Exception 1559794914 

TYPO3 Exception 1559794916 

TYPO3 Exception 1559794919 

TYPO3 Exception 1560319866 

TYPO3 Exception 1560875741 

TYPO3 Exception 1560876288 

TYPO3 Exception 1560876294 

TYPO3 Exception 1561583122 

TYPO3 Exception 1561583127 

TYPO3 10.4.28 - 2020-05-25 

Exception message:

InvalidArgumentException: TypoScriptFrontendController must be constructed with a valid SiteLanguage object or a resolved site in the current request as fallback. None given.

Situation 

The Preview section of a flux content element used <f:cObject> to access a TypoScript-defined function. Because no TSFE is available in the backend, one is created and that brings this error

Solution 

Workaround: Do not use <f:cObject> in backend previews.

In TYPO3v11 this has been fixed with https://forge.typo3.org/issues/91511, but that change has not been backported to v10.

TYPO3 Exception 1561618885 

TYPO3 Exception 1562240407 

TYPO3 Exception 1562253559 

TYPO3 Exception 1562257073 

TYPO3 Exception 1562314987 

TYPO3 Exception 1562354465 

TYPO3 Exception 1562357346 

TYPO3 Exception 1562665945 

TYPO3 Exception 1563217364 

TYPO3 Exception 1563270337 

TYPO3 Exception 1563375558 

TYPO3 Exception 1563375562 

TYPO3 Exception 1565709712 

TYPO3 Exception 1565709713 

TYPO3 Exception 1565709714 

TYPO3 Exception 1565773005 

TYPO3 Exception 1565773006 

TYPO3 Exception 1565777179 

TYPO3 Exception 1565863174 

TYPO3 Exception 1566823423 

TYPO3 Exception 1566823434 

TYPO3 Exception 1566823435 

TYPO3 Exception 1566853697 

TYPO3 Exception 1566909446 

TYPO3 Exception 1566909447 

TYPO3 Exception 1566909448 

TYPO3 Exception 1567969355 

TYPO3 Exception 1568119209 

TYPO3 Exception 1568119221 

TYPO3 Exception 1568119229 

TYPO3 Exception 1569620858 

TYPO3 Exception 1569668681 

TYPO3 Exception 1570543657 

TYPO3 Exception 1572521099 

TYPO3 Exception 1573047338 

TYPO3 Exception 1573061766 

TYPO3 Exception 1573385431 

TYPO3 Exception 1573740447 

TYPO3 Exception 1573753057 

TYPO3 Exception 1573753070 

TYPO3 Exception 1573825624 

TYPO3 Exception 1573825625 

TYPO3 Exception 1574174231 

TYPO3 Exception 1574362327 

TYPO3 Exception 1574422322 

TYPO3 Exception 1576247863 

TYPO3 Exception 1577789315 

TYPO3 Exception 1577789316 

TYPO3 Exception 1577789317 

TYPO3 Exception 1578045577 

TYPO3 Exception 1578054920 

TYPO3 Exception 1578162207 

TYPO3 Exception 1578164101 

TYPO3 Exception 1578164102 

TYPO3 Exception 1578831632 

TYPO3 Exception 1578950324 

TYPO3 Exception 1579965021 

TYPO3 Exception 1580056272 

TYPO3 Exception 1580225311 

TYPO3 Exception 1580225312 

TYPO3 Exception 1580225313 

TYPO3 Exception 1580743847 

TYPO3 Exception 1581343410 

TYPO3 Exception 1581501124 

TYPO3 Exception 1581501216 

TYPO3 Exception 1581502783 

TYPO3 Exception 1581862822 

This error might be caused by inserting content into a Fluid template by

<f:cObject typoscriptObjectPath="lib.myLib"/>
Copied!

If the TypoScript object uses a insertData = 1 or the datawrap curly braces might get parsed, see https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Stdwrap.html?highlight=insertdata.

So, the serialized value of the hidden form field tx_form_formframework[__trustedProperties] get's parsed, too. The following HMAC validation throws the exception, because the __trustedProperties is broken.

TYPO3 Exception 1581862823 

TYPO3 Exception 1582022226 

TYPO3 Exception 1582385098 

TYPO3 Exception 1582385619 

TYPO3 Exception 1582574541 

TYPO3 Exception 1582574553 

TYPO3 Exception 1582877555 

TYPO3 Exception 1584637096 

TYPO3 Exception 1584777201 

TYPO3 Exception 1584778196 

TYPO3 Exception 1584998393 

TYPO3 Exception 1585249769 

TYPO3 Exception 1586728563 

TYPO3 Exception 1586861816 

TYPO3 Exception 1586942436 

TYPO3 Exception 1588095935 

TYPO3\CMS\Core\Http\Security\MissingReferrerException 

#1588095935 TYPO3\CMS\Core\Http\Security\MissingReferrerException
Missing referrer for /main
Copied!

This error occurs when logging into the backend or Install Tool and is triggered by a failed check of the Referer header.

The reason for this may be:

  • the use of an HTTP proxy, e.g. a reverse proxy to an encapsulated system without sufficient header delegation
  • the webserver is not configured correctly to use a valid certificate

Solution 

The security check for the correct referrer was introduced due to potential security risks, visit the related security advisory for more information.

It is recommended that you keep this feature enabled, but it can be enabled or disabled in Admin Tools > Settings > Configure Installation-Wide Options > System > [SYS][features][security.backend.enforceReferrer].

TYPO3 Exception 1588095936 

Error occurs after importing database dump and open the backend the first time. No login, normally automatically logged in by a service. Maybe old temporary files or other old data. Clear InstallTool Cache solve the problem.

The error might also occur due to: a. A very strict referrer-policy of your webserver. For instance, if you set it to 'Header set Referrer-Policy "strict-origin"' in your Apache server, you will see this page after trying to login to the backend. or b. A reverseproxy in front of typo3 (like varnish or haproxy). To overcome that configure the proxy settings in [SYS][reverseProxy*]

TYPO3 Exception 1588178538 

TYPO3 Exception 1588784141 

TYPO3 Exception 1588784142 

TYPO3 Exception 1589183114 

TYPO3 Exception 1590314046 

TYPO3 Exception 1590487011 

TYPO3 Exception 1590487411 

TYPO3 Exception 1590740612 

TYPO3 Exception 1590850369 

TYPO3 Exception 1592207959 

TYPO3 Exception 1594043425 

TYPO3 Exception 1596462020 

TYPO3 Exception 1596980032 

InvalidArgumentException: A cache identifier was not set 

When debuging the corresponding cache.definition might look like this:

'' => array('groups' => array('pages', 'all'))
Copied!

This error can break the backend and frontend.

Background 

Before TYPO3 version 10 it was common that the variable $_EXTKEY was replaced automatically by the extension key of the corresponding extension.

This has changed and the variable either has to be defined or the extension key automatically applied.

As the variable $_EXTKEY was undefined, the array key for the cache definition was empty.

The error was therefore caused by an incomplete extension-update.

Solution 

Search in all extensions for usage of $_EXTKEY in the file ext_localconf.php.

If the variable is used but not defined in that file, define it in the beginning or replace it by the extension key.

TYPO3 Exception 1596980033 

TYPO3 Exception 1597310560 

TYPO3 Exception 1597437985 

TYPO3 Exception 1597577827 

TYPO3 Exception 1598341765 

TYPO3 Exception 1598350445 

TYPO3 Exception 1599164743 

TYPO3 Exception 1599235454 

TYPO3 Exception 1599395651 

TYPO3 Exception 1599724418 

TYPO3 Exception 1599767133 

TYPO3 Exception 1599834020 

TYPO3 Exception 1600373491 

TYPO3 Exception 1601021306 

TYPO3 Exception 1601370681 

TYPO3 Exception 1601370682 

TYPO3 Exception 1601370683 

TYPO3 Exception 1601566451 

TYPO3 Exception 1601923209 

TYPO3 Exception 1601923215 

TYPO3 Exception 1601923319 

TYPO3 Exception 1602103603 

TYPO3 Exception 1602226715 

TYPO3 Exception 1602251838 

TYPO3 Exception 1602432207 

TYPO3 Exception 1602505264 

TYPO3 Exception 1602615347 

TYPO3 Exception 1602615348 

TYPO3 Exception 1603087515 

TYPO3 Exception 1603439142 

TYPO3 Exception 1603439146 

TYPO3 Exception 1604308205 

TYPO3 Exception 1604308206 

TYPO3 Exception 1604564346 

TYPO3 Exception 1604584766 

TYPO3 Exception 1604608843 

TYPO3 Exception 1604608922 

TYPO3 Exception 1605192311 

TYPO3 Exception 1605305001 

TYPO3 Exception 1605305002 

TYPO3 Exception 1605812020 

TYPO3 Exception 1605861181 

TYPO3 Exception 1605861905 

TYPO3 Exception 1605873757 

TYPO3 Exception 1606222812 

TYPO3 Exception 1606306196 

TYPO3 Exception 1606478088 

TYPO3 Exception 1606478090 

TYPO3 Exception 1606490398 

TYPO3 Exception 1606732015 

TYPO3 Exception 1606732016 

TYPO3 Exception 1606732017 

TYPO3 Exception 1606732018 

TYPO3 Exception 1606732019 

TYPO3 Exception 1606732020 

TYPO3 Exception 1606732021 

TYPO3 Exception 1607172972 

TYPO3 Exception 1607271511 

TYPO3 Exception 1607271592 

TYPO3 Exception 1607271637 

TYPO3 Exception 1607271747 

TYPO3 Exception 1607271781 

TYPO3 Exception 1607328584 

TYPO3 Exception 1607585445 

"No page configured for type=0." TYPO3 v13.4.0 - 2024-11-02 

This happens if the following line is missing from your TypoScript:

page = PAGE
Copied!

See also Troubleshooting.

"No TypoScript record found!" TYPO3 v13.4.0 - 2024-11-02 

This happens when the current site has no root TypoScript record and no site set including TypoScript.

See also Troubleshooting.

TYPO3 v13.1.0 - 2024-04-28 

The issue 

When configuring sets <ext_core:feature-103437-1712062105> with an invalid dependency in the Configuration/Sets/MySet/config.yaml the following error is displayed:

No page configured for type=0.
Copied!

In the var/log/typo3_xxx.log is also an error logged:

Sun, 28 Apr 2024 19:05:23 +0200 [ERROR] request="3274a5986fc4e" component="TYPO3.CMS.Core.Site.Set.SetRegistry": Invalid set "my-vendor/my-site": Missing dependency "some-vendor/some-set"
Copied!

Solution 

Correct the name of the dependency in Configuration/Sets/MySet/config.yaml, or remove it completely.

TYPO3 Exception 1607596900 

TYPO3 Exception 1608286894 

TYPO3 Exception 1608658396 

TYPO3 Exception 1610464090 

TYPO3 Exception 1610994735 

TYPO3 Exception 1611748791 

TYPO3 Exception 1611748792 

TYPO3 Exception 1611879242 

TYPO3 Exception 1611879243 

TYPO3 Exception 1611879244 

TYPO3 Exception 1612649840 

TYPO3 Exception 1612649842 

TYPO3 Exception 1612781782 

TYPO3 Exception 1612868954 

TYPO3 Exception 1612868955 

TYPO3 Exception 1612883326 

TYPO3 Exception 1613216548 

TYPO3 Exception 1613300274 

TYPO3 Exception 1613666803 

TYPO3 Exception 1613687097 

TYPO3 Exception 1613993188 

TYPO3 Exception 1614264312 

TYPO3 Exception 1614264313 

TYPO3 Exception 1614500657 

TYPO3 Exception 1614500658 

TYPO3 Exception 1614500659 

TYPO3 Exception 1614500660 

TYPO3 Exception 1614500661 

TYPO3 Exception 1614500662 

TYPO3 Exception 1614500663 

TYPO3 Exception 1615020908 

TYPO3 Exception 1615020909 

TYPO3 Exception 1615021869 

TYPO3 Exception 1616175847 

TYPO3 Exception 1616175867 

11.5.11 - 26.06.2022 

Situation 

Exception message upon failed login
(1/1) #1616175867 TYPO3\CMS\Core\RateLimiter\RequestRateLimitedException

The login is locked until 26-06-22 12:33 due to too many failed login attempts from your IP address.
Copied!

This exception is thrown, when there have been too many failed login attempts from one IP address within a given time frame.

See also: Feature: #93825 - Rate limiting for failed logins.

Solution 

  1. Wait for the lock to time out.
  2. If the limit is too short for your purposes, make the limit higher.
  3. During Development: Deleting the cache folder var/cache/data/ratelimiter/ manually enables login right away again.

TYPO3 Exception 1618342858 

TYPO3 Exception 1618989190 

TYPO3 Exception 1618992262 

TYPO3 Exception 1619030957 

TYPO3 Exception 1619446378 

TYPO3 Exception 1619446379 

TYPO3 Exception 1620147893 

TYPO3 Exception 1621511632 

TYPO3 Exception 1622109821 

TYPO3 Exception 1622148496 

TYPO3 Exception 1623097600 

TYPO3 Exception 1623148753 

TYPO3 Exception 1623881310 

TYPO3 Exception 1623881311 

TYPO3 Exception 1623881312 

TYPO3 Exception 1623881313 

TYPO3 Exception 1623881314 

TYPO3 Exception 1623881315 

TYPO3 Exception 1623914347 

TYPO3 Exception 1623925235 

TYPO3 Exception 1623940985 

TYPO3 Exception 1623941276 

TYPO3 Exception 1623941361 

TYPO3 Exception 1624029932 

TYPO3 Exception 1624029933 

TYPO3 Exception 1624029934 

TYPO3 Exception 1624286811 

TYPO3 Exception 1624286812 

TYPO3 Exception 1624286813 

TYPO3 Exception 1624286814 

TYPO3 Exception 1624310264 

TYPO3 Exception 1624313533 

TYPO3 Exception 1624436360 

TYPO3 Exception 1624452070 

TYPO3 Exception 1624452071 

TYPO3 Exception 1624551586 

TYPO3 Exception 1624562166 

TYPO3 Exception 1624876139 

TYPO3 Exception 1624876266 

TYPO3 Exception 1624879295 

TYPO3 Exception 1625169125 

TYPO3 Exception 1625556521 

TYPO3 Exception 1625562833 

TYPO3 Exception 1625585157 

TYPO3 Exception 1625585158 

TYPO3 Exception 1625826491 

TYPO3 Exception 1625838481 

TYPO3 Exception 1626357141 

TYPO3 Exception 1627335016 

TYPO3 Exception 1627335017 

TYPO3 Exception 1627336557 

TYPO3 Exception 1627407451 

TYPO3 Exception 1627407452 

TYPO3 Exception 1627407511 

TYPO3 Exception 1627565458 

TYPO3 Exception 1627565459 

TYPO3 Exception 1627573099 

TYPO3 Exception 1627573100 

TYPO3 Exception 1627573101 

TYPO3 Exception 1627573103 

TYPO3 Exception 1627640208 

TYPO3 Exception 1627640209 

TYPO3 Exception 1627640210 

TYPO3 Exception 1627898896 

TYPO3 Exception 1627899274 

TYPO3 Exception 1627899342 

TYPO3 Exception 1627899708 

TYPO3 Exception 1627905246 

TYPO3 Exception 1627907107 

TYPO3 Exception 1627907587 

TYPO3 Exception 1628189230 

TYPO3 Exception 1628677079 

TYPO3 Exception 1628736154 

TYPO3 Exception 1629196918 

TYPO3 Exception 1629817141 

TYPO3 Exception 1629819799 

TYPO3 Exception 1629819858 

TYPO3 Exception 1629820498 

TYPO3 Exception 1629824596 

TYPO3 Exception 1629922856 

TYPO3 Exception 1629996089 

TYPO3 Exception 1629996090 

TYPO3 Exception 1629996091 

TYPO3 Exception 1630089406 

TYPO3 Exception 1630324435 

TYPO3 Exception 1630346631 

TYPO3 Exception 1630773210 

TYPO3 Exception 1630773230 

TYPO3 Exception 1630773261 

TYPO3 Exception 1630773276 

TYPO3 Exception 1631254000 

TYPO3 Exception 1631630087 

TYPO3 Exception 1631630764 

TYPO3 Exception 1631700480 

TYPO3 Exception 1632154036 

TYPO3 Exception 1633171038 

TYPO3 Exception 1633171172 

TYPO3 Exception 1633604720 

TYPO3 Exception 1633671654 

TYPO3 Exception 1633674049 

TYPO3 Exception 1633777536 

TYPO3 Exception 1634662405 

TYPO3 Exception 1635268969 

TYPO3 Exception 1635863703 

TYPO3 Exception 1635927108 

TYPO3 Exception 1636145677 

TYPO3 Exception 1636901978 

TYPO3 Exception 1638022483 

TYPO3 Exception 1638264590 

TYPO3 12.4 - 2024-05-09 

Overview 

An extension adds to a backend Form own Form Nodes. Form node definition adds the deprecated: RequireJsModules:

Example:

$resultArray['requireJsModules'][] = 'TYPO3/CMS/Extension/JavaScriptFile';

The Issue 

Calling the "Edit" Function in TYPO3 Backend of a record using such own Form Node raises this LogicException

Solution 

see needed migration steps for the Extension maintainer in the TYPO3 Documentation: <https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/12.0/Breaking-96221-DenyInlineJavaScriptInFormEnginesRequireJsModules.html>

TYPO3 Exception 1638376684 

TYPO3 Exception 1638376687 

TYPO3 Exception 1638376689 

TYPO3 Exception 1638554283 

TYPO3 Exception 1638880941 

TYPO3 Exception 1638976434 

TYPO3 Exception 1638976490 

TYPO3 Exception 1639224353 

TYPO3 Exception 1639224354 

TYPO3 Exception 1639672666 

TYPO3 Exception 1639741792 

TYPO3 Exception 1639818540 

TYPO3 Exception 1639819269 

TYPO3 12.4.12 - 20.03.2024 

Installation Overview 

Sending a \TYPO3\CMS\Core\Mail\FluidEmail from a console command. The template uses the Uri.page ViewHelper <f:uri.page>.

The Issue 

Error message:

Example error output
[ERROR] The rendering context of ViewHelper f:link.page is missing a valid request object. 
Copied!

Solution 

Switch to using other ViewHelpers or set a valid request object to the FluidEmail See also Send email with FluidEmail.

TYPO3 Exception 1639819692 

TYPO3 Exception 1639820200 

TYPO3 Exception 1639821269 

TYPO3 Exception 1639821904 

TYPO3 Exception 1639828178 

TYPO3 Exception 1640095993 

TYPO3 Exception 1640097205 

TYPO3 Exception 1640297526 

TYPO3 Exception 1640297535 

TYPO3 Exception 1641658569 

TYPO3 Exception 1641670373 

TYPO3 Exception 1641670374 

TYPO3 Exception 1641670375 

TYPO3 Exception 1641715832 

TYPO3 Exception 1641715833 

TYPO3 Exception 1641717510 

TYPO3 Exception 1641720169 

TYPO3 Exception 1641720929 

TYPO3 Exception 1641986533 

TYPO3 Exception 1641989097 

TYPO3 12.4.14 - 25.04.2024 

Installation Overview 

Installation with custom Email templates for form, Updated from TYPO3 v10.4

The Issue 

Warning message
(1/1) #1641989097 LogicException
Invoked ContentObjectRenderer::parseFunc without any configuration
Copied!

Solution 

The template contained the following:

Template.html before
<f:format.html parseFuncTSPath="">
    <f:translate extensionName="..." key="emailToSender.thankYou" arguments="{0: type}"/>
</f:format.html>
Copied!

Replace with

Template.html before
<f:format.html>
    <f:translate extensionName="..." key="emailToSender.thankYou" arguments="{0: type}"/>
</f:format.html>
Copied!

This way null is used instead of an empty string and the default can be applied.

TYPO3 Exception 1641993564 

TYPO3 Exception 1642000232 

TYPO3 Exception 1642001442 

TYPO3 Exception 1642171035 

TYPO3 Exception 1642174843 

TYPO3 Exception 1642375889 

TYPO3 Exception 1642375890 

TYPO3 Exception 1642450334 

TYPO3 Exception 1642938352 

TYPO3 Exception 1642954501 

TYPO3 Exception 1642956282 

TYPO3 Exception 1643372902 

TYPO3 Exception 1643798660 

TYPO3 Exception 1644600510 

TYPO3 Exception 1644600511 

TYPO3 Exception 1644932383 

TYPO3 Exception 1644932384 

TYPO3 Exception 1645506529 

TYPO3 Exception 1645700473 

TYPO3 Exception 1645721824 

TYPO3 Exception 1645916594 

TYPO3 Exception 1645916610 

TYPO3 Exception 1645916622 

TYPO3 Exception 1645916633 

TYPO3 Exception 1646504471 

TYPO3 Exception 1646922484 

TYPO3 Exception 1647241084 

TYPO3 Exception 1647241085 

TYPO3 Exception 1647241086 

TYPO3 Exception 1647241087 

TYPO3 Exception 1647338094 

TYPO3 Exception 1647338470 

TYPO3 Exception 1647947686 

TYPO3 Exception 1649124682 

TYPO3 Exception 1649846004 

TYPO3 Exception 1650546252 

TYPO3 Exception 1650579934 

TYPO3 Exception 1650893781 

TYPO3 Exception 1651137904 

TYPO3 Exception 1651138603 

TYPO3 Exception 1651499353 

TYPO3 Exception 1651499354 

TYPO3 Exception 1651671582 

TYPO3 Exception 1651690534 

TYPO3 Exception 1651771351 

TYPO3 Exception 1651771352 

TYPO3 Exception 1651775963 

TYPO3 Exception 1651785134 

TYPO3 Exception 1651996049 

TYPO3 Exception 1652741356 

TYPO3 Exception 1653737656 

TYPO3 Exception 1653743453 

TYPO3 Exception 1653743454 

TYPO3 Exception 1653743455 

TYPO3 Exception 1654249048 

TYPO3 Exception 1654249049 

TYPO3 Exception 1654267174 

TYPO3 Exception 1655138907 

TYPO3 Exception 1655551062 

TYPO3 Exception 1655723512 

TYPO3 Exception 1655725105 

TYPO3 Exception 1655823705 

TYPO3 Exception 1655824257 

TYPO3 Exception 1655824258 

TYPO3 Exception 1655824621 

TYPO3 Exception 1655824946 

TYPO3 Exception 1655824947 

TYPO3 Exception 1655825120 

TYPO3 Exception 1655825121 

TYPO3 Exception 1655825122 

TYPO3 Exception 1655825891 

TYPO3 Exception 1655825892 

TYPO3 Exception 1655826025 

TYPO3 Exception 1655826193 

TYPO3 Exception 1655826443 

TYPO3 Exception 1655977210 

TYPO3 Exception 1655977211 

TYPO3 Exception 1655988945 

TYPO3 Exception 1656668000 

TYPO3 Exception 1656668001 

TYPO3 Exception 1657960610 

TYPO3 Exception 1658562276 

TYPO3 Exception 1658568446 

TYPO3 Exception 1658568794 

TYPO3 Exception 1658578645 

TYPO3 Exception 1660215701 

TYPO3 13.4.18 - 26.09.2025 

The Issue 

The model had a setter, which accidently used bool instead of null for a not-set value

#[Lazy]
protected ?Page $pageoverride = null;

public function setPageoverride(Page|bool $pageoverride): void
{
    $this->pageoverride = $pageoverride;
}
Copied!

Solution 

- public function setPageoverride(Page|bool $pageoverride): void
+ public function setPageoverride(Page|bool $pageoverride): void
Copied!

TYPO3 Exception 1660217846 

TYPO3 Exception 1660834545 

TYPO3 Exception 1661333862 

TYPO3 Exception 1661333863 

TYPO3 Exception 1661333864 

TYPO3 Exception 1661350211 

TYPO3 Exception 1661365944 

TYPO3 Exception 1661532580 

TYPO3 Exception 1661540376 

TYPO3 Exception 1661615151 

TYPO3 Exception 1661617062 

TYPO3 Exception 1661769346 

TYPO3 Exception 1662458842 

TYPO3 Exception 1662727149 

TYPO3 Exception 1662808782 

TYPO3 Exception 1663617170 

TYPO3 12.4.19 - 20.08.2024 

Installation Overview 

Upgrade from TYPO3 v11.5 to v12.4

The Issue 

f:form viewhelpers cannot be used in non-Extbase context anymore:

See Avoiding f:form in non-Extbase context

Solution 

Replace the viewhelpers with plain HTML, write your own viewhelpers or create an Extbase context if needed

TYPO3 Exception 1663851377 

TYPO3 Exception 1663860283 

TYPO3 Exception 1664195013 

TYPO3 Exception 1664202134 

TYPO3 Exception 1664202135 

TYPO3 Exception 1664215980 

TYPO3 Exception 1664260307 

TYPO3 Exception 1664364262 

TYPO3 Exception 1664364263 

TYPO3 Exception 1664380909 

TYPO3 Exception 1664440476 

TYPO3 Exception 1664473929 

TYPO3 Exception 1664486783 

TYPO3 Exception 1664486790 

TYPO3 Exception 1664486791 

TYPO3 Exception 1664672015 

TYPO3 Exception 1664968186 

TYPO3 Exception 1666024513 

TYPO3 Exception 1666131903 

TYPO3 Exception 1666303735 

TYPO3 Exception 1666303765 

TYPO3 Exception 1666309039 

TYPO3 Exception 1666513644 

TYPO3 Exception 1666513645 

TYPO3 13.4 - 30th December 2024 

Installation Overview 

It uses the extension tslib_fetce 0.9.2 which uses the FrontendTce class Middleware.

The Issue 

RuntimeException

Setup array has not been initialized. This happens in cached Frontend scope where full TypoScript is not needed by the system.

Solution 

Call the method hasSetup before getSetupArray.

public function process(ServerRequestInterface $request, RequestHandlerInterface $handler): ResponseInterface
{
   $tsfe = $this->getTypoScriptFrontendController();
   $frontendTypoScript = $request->getAttribute('frontend.typoscript');
   if ($frontendTypoScript->hasSetup()) {
       $typoScriptSetupArray = $frontendTypoScript->getSetupArray();
       // ...
   }
}

/**
 * @return TypoScriptFrontendController
 */
 protected function getTypoScriptFrontendController(): TypoScriptFrontendController
 {
    return $GLOBALS['TSFE'];
 }
Copied!

TYPO3 Exception 1667557900 

TYPO3 Exception 1667557901 

TYPO3 Exception 1667557902 

TYPO3 Exception 1667565756 

TYPO3 Exception 1667565757 

TYPO3 Exception 1667645426 

TYPO3 Exception 1668084601 

TYPO3 Exception 1668696350 

TYPO3 Exception 1668942244 

TYPO3 Exception 1669358326 

TYPO3 Exception 1669747192 

TYPO3 Exception 1669747200 

TYPO3 Exception 1669747572 

TYPO3 Exception 1669747578 

TYPO3 Exception 1669747592 

TYPO3 Exception 1669747601 

TYPO3 Exception 1669747607 

TYPO3 Exception 1669747614 

TYPO3 Exception 1669747620 

TYPO3 Exception 1669747625 

TYPO3 Exception 1669747685 

TYPO3 Exception 1669757255 

TYPO3 Exception 1669800914 

TYPO3 Exception 1669813635 

TYPO3 Exception 1669822315 

TYPO3 Exception 1669839336 

TYPO3 Exception 1669905551