Bug #33227

Regression in language handling introduced by locallangXmlOverride fix

Added by Susanne Moog almost 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
Category:
-
Target version:
Start date:
2012-01-16
Due date:
% Done:

100%

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

Description

Since the fix for #32573 there is a regression in the language handling of TYPO3. If you request a translated string in a language where no translation is available you used to get the default language labels in the [target] array attribute of the LOCAL_LANG array for that language. After the fix you only get the [source] element filled. Which seems logically more correct but breaks extensions (like extbase/fluid) that rely on always having the [target] attribute filled.

Example:
locallang.xml with

        <languageKey index="default" type="array">
            <label index="label1">This is label #1</label>
            <label index="label2">This is label #2</label>
            <label index="label3">This is label #3</label>
        </languageKey>

request language (config.language) = de

expected result (before the fix of #32573):

array(
  0 => array(
    'source' => 'This is label #1',
    'target' => 'This is label #2'
  )
)

current result (after #32573):

array(
  0 => array(
    'source' => 'This is label #1'
  )
)
#1

Updated by Gerrit Code Review almost 10 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/7820

#2

Updated by Gerrit Code Review almost 10 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/7820

#3

Updated by Gerrit Code Review almost 10 years ago

Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/8611

#4

Updated by Nils Seinschedt almost 10 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
#5

Updated by Xavier Perseguers almost 10 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF