Bug #17905

t3lib_div::readLLXMLfile does not use localized content anymore

Added by Oliver Hader almost 12 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Must have
Assignee:
Category:
Communication
Target version:
-
Start date:
2007-12-11
Due date:
% Done:

0%

TYPO3 Version:
4.1
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

In bug #17894 the localization of other languages (besides the 'default' language) should be move to an external file to prevent loading unused string data.
If this file generated by t3lib_div::llXmlAutoFileName doesn't exist, the localized part is set to an empty array at the end of t3lib_div::readLLXMLfile.

The solution is to check whether this external file exists.

Affects TYPO3 4.1.4 and Trunk when locallang.xml files of extensions were modified locally or extension were updated from TER and have a modified locallang.xml.

(issue imported from #M6924)

0006924_v3.patch View (2.5 KB) Administrator Admin, 2007-12-12 11:12

0006924_v4_v2.patch View (3.86 KB) Administrator Admin, 2007-12-12 17:57

0006924_v2.patch View (1.29 KB) Administrator Admin, 2007-12-13 21:28


Related issues

Related to TYPO3 Core - Bug #17894: Translated language files are not loaded Closed 2007-12-06

History

#1 Updated by Oliver Hader almost 12 years ago

The v3 patch modifies the following:
  • update readLLXMLfile's "version" from 2.2 to 2.3 and forces a new hash
  • changes from shortMD5 (10 bytes) to md5 (32 bytes)
  • removes a deprecated check against length of filenames to be lower than 60 bytes

#2 Updated by Oliver Hader almost 12 years ago

Committed to SVN:
  • TYPO3_4-1 (rev. 2826)
  • Trunk (rev. 2827)

(the file "0006924_v2.patch" was taken for comit)

#3 Updated by Oliver Hader almost 12 years ago

Fixed in TYPO3 4.1.5 (hotfix for 4.1.4)

Also available in: Atom PDF