Project

General

Profile

Actions

Bug #105536

open

Extbase AbstractValidator:translateErrorMessage() do not accept normal translateKey anymore

Added by André Kraus 3 days ago. Updated 3 days ago.

Status:
Under Review
Priority:
Should have
Assignee:
Category:
Extbase
Target version:
Start date:
2024-11-04
Due date:
% Done:

0%

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

Description

The method ranslateErrorMessage() in TYPO3\CMS\Extbase\Validation\Validator\AbstractValidator has parameter 1 to be the translation key and parameter 2 to be the extension name. So when you translated your error message with key and extension name in the past, you get your intended translation. In TYPO3 v13, there is at the very beginning a if condition, which says

if (!str_starts_with($translateKey, 'LLL:')) {
   return $translateKey;
}

So normal translation keys can not work anymore.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #102326: Allow custom translation keys for extbase validatorsClosedTorben Hansen2023-11-06

Actions
Actions #1

Updated by Torben Hansen 3 days ago

  • Status changed from New to Accepted
  • Assignee set to Torben Hansen
Actions #2

Updated by Torben Hansen 3 days ago

  • Related to Feature #102326: Allow custom translation keys for extbase validators added
Actions #3

Updated by Gerrit Code Review 3 days ago

  • Status changed from Accepted to Under Review

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

Actions #4

Updated by Gerrit Code Review 3 days ago

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

Actions

Also available in: Atom PDF