Bug #16010
closed
"Cannot use string offset as an array" when update a translation
0%
Description
Ext Manager => Translation handling => Update from repository
Fatal error: Cannot use string offset as an array in /home/typo3-4.0.0/typo3/mod/tools/em/class.em_index.php on line 1204
See attached screenshot.
The problematic line seems to be :
if($localmd5 != $translationStatusArr[$lang]['md5']) {(issue imported from #M3188)
Files
Updated by Thomas Born about 18 years ago
We use Typo3 4.0 on IIS on Server 2003 with mysql-essential-5.0.19 and php-5.1.2 and have the same error message:
Fatal error: Cannot use string offset as an array in C:\Inetpub\wwwroot\typo3_src-4.0\typo3\mod\tools\em\class.em_index.php on line 1204
Updated by Nick Weisser about 18 years ago
I have the same error message, but in relation to class.t3lib_flexformtools.php.
I'm using TYPO3 4.0 final with TemplaVoila 0.6.1. When I'm inserting a new content element on a page chosing e.g. text w/image in the content element wizard (or any other element type) i get this error message:
Fatal error: Cannot use string offset as an array in /home/mydomain.com/ftp/www/typo3_src-4.0/t3lib/class.t3lib_flexformtools.php on line 145
The same thing happens when a content element is deleted and upon entering the "page properties" of standard page in the page tree. Strangely enough the page properties can be entered when the page is of type "not in menu".
Under TYPO3 4.0 beta2 everything was o.k.
PHP Version 5.1.2
MySQL 4.1.18
Updated by old_Nurn123 almost 18 years ago
Nothing new on that ?
That's a very critical feature => I can't use Typo3 4.0 on my server because of this (because I can't impose to my customers tu use an English interface !)
Updated by Karsten Dambekalns almost 18 years ago
Please have a look at bug #16220 and the patch attached there. Further discussion should be done there. Thanks.