Project

General

Profile

Actions

Bug #99190

closed

PHP Warning: Undefined array key 1 in /typo3/sysext/core/Classes/Localization/LanguageService.php line 240

Added by Tee Ohh almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-11-25
Due date:
% Done:

100%

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

Description

If I have a translation file for CSH with an translation unit id without a dot, the TYPO3 backend throws a warning. I know that this translation unit id is wrong, but before PHP 8.1 it just didn't show the CSH.
Warning

PHP Warning: Undefined array key 1 in /typo3/sysext/core/Classes/Localization/LanguageService.php line 240

Example
<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<xliff version="1.0">
    <file source-language="en" datatype="plaintext" original="messages" date="2022-11-25T12:30:00Z" product-name="my_ext_key">
        <header/>
        <body>
            <trans-unit id="my_field.description">
                <source>This works</source>
            </trans-unit>
            <trans-unit id="my_field">
                <source>This failed</source>
            </trans-unit>
        </body>
    </file>
</xliff>


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #98713: Undefined array key 1 in LanguageServiceClosed2022-10-24

Actions
Actions #1

Updated by Stefan Bürk almost 2 years ago

  • Is duplicate of Bug #98713: Undefined array key 1 in LanguageService added
Actions #2

Updated by Gerrit Code Review almost 2 years ago

  • Status changed from New to Under Review

Patch set 1 for branch 11.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/76838

Actions #3

Updated by Stefan Bürk almost 2 years ago

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

Updated by Benni Mack almost 2 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF