Project

General

Profile

Actions

Bug #16144

closed

Fatal php error during BE Login when a l10n xml file is faulty

Added by Alexander Bergmann over 18 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2006-05-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Typo3 4.0 will throw an fatal php error during BE login when:
- a l10n xml file is faulty
- the language for the user is not english

Error message:
Fatal error: Cannot use string offset as an array in PATH\t3lib\class.t3lib_div.php on line 3596

Download the translation files for the language of your choice
Set the default language to the choosen language.

Reload the backend to check if the check wheater the translation works before we start producing bugs.

Edit a l10n XML file.
Remove all content so that the filesize becomes 0 Bytes or edit it in a way that renders the XML invalid.

Reload the backend -> Now you should whitness the fatal error.

If not: remove the cached translation files from /typo3temp/llxml/

Neither "Check status against repository" nor "Update from repository" within the Translation handeling section of the extension manager are able to detect the faulty xml file.

Reproduced with PHP 5.1.1 and 5.1.2 on Win32 and Unix
(issue imported from #M3480)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #19241: no details with error message 'is no TYPO3 language file'ClosedBenni Mack2008-08-21

Actions
Actions #1

Updated by Alexander Opitz over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • PHP Version deleted (5)

The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?

IMHO this was fixed.

Actions #2

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback for over 90 days.

Actions

Also available in: Atom PDF