Bug #41897
closedFatal error: Cannot use string offset as an array
0%
Description
Unfortunetly I encountered this PHP-Error when logging into the backend with TYPO3 6.0b2:
Fatal error: Cannot use string offset as an array in /var/www/typo3_src-git/typo3/sysext/core/Classes/Resource/ResourceFactory.php on line 145 Call Stack: 0.0002 643648 1. {main}() /var/www/typo3_src-git/typo3/index.php:0 0.0003 671656 2. require('/var/www/typo3_src-git/typo3/init.php') /var/www/typo3_src-git/typo3/index.php:36 0.2013 18314072 3. TYPO3\CMS\Core\Core\Bootstrap->initializeBackendUserMounts() /var/www/typo3_src-git/typo3/init.php:100 0.2013 18314776 4. TYPO3\CMS\Core\Authentication\BackendUserAuthentication->returnFilemounts() /var/www/typo3_src-git/typo3/sysext/core/Classes/Core/Bootstrap.php:784 0.2067 18572528 5. TYPO3\CMS\Core\Authentication\BackendUserAuthentication->getFileStorages() /var/www/typo3_src-git/typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1853 0.2067 18572528 6. TYPO3\CMS\Core\Authentication\BackendUserAuthentication->initializeFileStorages() /var/www/typo3_src-git/typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1586 0.2141 19154000 7. TYPO3\CMS\Core\Resource\StorageRepository->findAll() /var/www/typo3_src-git/typo3/sysext/core/Classes/Authentication/BackendUserAuthentication.php:1514 0.2167 19896656 8. TYPO3\CMS\Core\Resource\StorageRepository->createDomainObject() /var/www/typo3_src-git/typo3/sysext/core/Classes/Resource/StorageRepository.php:132 0.2167 19896656 9. TYPO3\CMS\Core\Resource\ResourceFactory->getStorageObject() /var/www/typo3_src-git/typo3/sysext/core/Classes/Resource/StorageRepository.php:196 0.2167 19896816 10. TYPO3\CMS\Core\Resource\ResourceFactory->createStorageObject() /var/www/typo3_src-git/typo3/sysext/core/Classes/Resource/ResourceFactory.php:128 0.2167 19896984 11. TYPO3\CMS\Core\Resource\ResourceFactory->convertFlexFormDataToConfigurationArray() /var/www/typo3_src-git/typo3/sysext/core/Classes/Resource/ResourceFactory.php:212
I really don't know what's going on there. I did not touch any file. I am using Ubuntu 12.04 with latest PHP 5.3 available for it.
Perhaps someone knows the answer to this strange error.
Alex
Updated by Anja Leichsenring almost 12 years ago
Enter the install tool and use in the section Database Analyser the COMPARE function. This solved the problem for me.
Updated by Markus Günther almost 12 years ago
I have installed a brand new TYPO3 Instance for testing it on a Mac OSX 10.8.2 with PHP 5.3 but i can't reproduce this error.
Updated by Nico de Haen almost 12 years ago
I got the same error on a fresh install.
I could fix it by adding changing the XML in the first row of the table sys_file_storage:
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
instead of
<?xml version="1.0" encoding="" standalone="yes" ?>
Updated by Steffen Gebert almost 12 years ago
- Category set to File Abstraction Layer (FAL)
Looks like there's some non-utf8 char in it?
Updated by Andreas Wolf almost 12 years ago
Steffen Gebert wrote:
Looks like there's some non-utf8 char in it?
The record in question is most likely the automatically created default storage pointing to fileadmin/. The error might come from the FlexFormTools::flexArray2Xml(), which is used by the StorageRepository to automatically create that default record.
To all who experienced this error: Could you please execute the following code and paste the result?
// create the FlexForm for the driver configuration
$flexFormData = array(
'data' => array(
'sDEF' => array(
'lDEF' => array(
'basePath' => array('vDEF' => 'fileadmin/'),
'pathType' => array('vDEF' => 'relative')
)
)
)
);
/** @var $flexObj \TYPO3\CMS\Core\Configuration\FlexForm\FlexFormTools */
$flexObj = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance('TYPO3\\CMS\\Core\\Configuration\\FlexForm\\FlexFormTools');
$flexFormXml = $flexObj->flexArray2Xml($flexFormData, TRUE);
echo $flexFormXml;
Updated by Steffen Ritter almost 12 years ago
- Status changed from New to Needs Feedback
the issue was resolved already reading the extbase chat - please report back
Updated by Steffen Ritter almost 12 years ago
- Status changed from Needs Feedback to Rejected
As no feedback present anymore and Alex Schnitzler did say it worked on the sprint in Extbase chat I close this issue
Updated by Georg Ringer over 4 years ago
- Related to Bug #66309: Refindex fixer: crash with broken flexform on deleted page added