Bug #6725

FE translation may use wrong language when a BE session is active

Added by Martin Kutschker about 3 years ago. Updated over 2 years ago.

Status:Resolved Start date:2010-03-06
Priority:Must have Due date:
Assignee:- % Done:

100%
Category:-
Target version:Extbase 1.0.2
Has patch: Tags:
Votes: 0

Description

The language of a BE session and the FE language may differ, so $LANG and §TSFE main their own "lang" property.

To fix the issue a small change tp Tx_Extbase_Utility_Localization is necessary.

    protected function translateFileReference($key) {
        if (TYPO3_MODE === 'FE') {
            return $GLOBALS['TSFE']->sL($key);
        } elseif (is_object($GLOBALS['LANG'])) {
            $value = $GLOBALS['LANG']->sL($key);
            return $value !== '' ? $value : NULL;
         } else {
            return $key;
        }
     }

Associated revisions

Revision 0e13a80a
Added by Jochen Rau about 3 years ago

[+BUGFIX] Extbase (Utility): Extbase uses the right BE charset now when forceCharset is not used. Thanks to Martin Kutschker who provided the patch. Resolves #6236.
[+BUGFIX] Extbase (Utility): Fixed broken charset conversion in BE. Thanks to Martin Kutschker who provided the patch. Resolves #6385.
[+BUGFIX] Extbase (Utility): FE translation now uses the right language when a BE session is active. Thanks to Martin Kutschker who provided the patch. Resolves #6725.

History

#1
Updated by Jochen Rau about 3 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1984.

Also available in: Atom PDF