TYPO3 Exception 1476107295¶

Note

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

General TYPO3 troubleshooting tips can be found in the section “Troubleshooting” of the menu, and live support is available in the TYPO3 Slack channel #typo3-cms.

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

Permission denied¶

PHP Warning: session_start(): failed: Permission denied (13)

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 7.6.23 to TYPO3 8.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)

Solution¶

Check your filesystem at the folder given in the error message and run

sudo fsck -cfk /dev/sda2

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

(TYPO3 8.7) The error occurred in CKEditor Rich Text Editor while setting a link. This was caused by the pageTSconfig for the old rte html Editor. After deleting the pageTSconfig 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)

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 8.7 to 9.5 while rendering a template which contains JavaScript in the FluidTYPO3VhsViewHelpersAssetScriptViewHelper.

Upgrading from TYPO3 8 to 9¶

After upgrading from TYPO3 8 to 9 I got this error because PHP Cache is loading the files out of the old TYPO3 8 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

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

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

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 ext, when you are in debug mode and you are good to go.

PHP Warning: Undefined array key “<field>” in ControllerName.php¶

Using TYPO3v11 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 11.5.13 to 11.5.14. There is an issue: Forge #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

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();

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();