Project

General

Profile

Actions

Bug #104498

closed

Language update for local extensions produces warnings in logs

Added by Florian Seirer 4 months ago. Updated 4 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Localization
Target version:
-
Start date:
2024-07-29
Due date:
% Done:

0%

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

Description

Updating the language packs in the install tool or with the scheduler task produces warnings in the log:

component="TYPO3.CMS.Install.Service.LanguagePackService": Requesting https://localize.typo3.org/xliff/s/o/solrfal-l10n/solrfal-l10n-de.zip was not successful, got status code 404 (Not Found) - {"request":"https://localize.typo3.org/xliff/s/o/solrfal-l10n/solrfal-l10n-de.zip","status":404,"reason":"Not Found"}

No error is visible in the backend. The flash message from the language updater just counts them as "not available".

Local extensions (not from TER or github, etc.) are usually hosted privately and have their own language files included, so it's not necessary to fetch them from the external localization server where they obviously don't exist. I'm not sure if this is the case for every extension.

Is there a way to disable the language pack updater for local extensions and prevent log entries like this?

Actions #1

Updated by Chris Müller 4 months ago

AFAIK there is no way to deactivate the update of language packs for specific extensions in v11. With v12 an event has been introduced which enables you to do that:
https://docs.typo3.org/m/typo3/reference-coreapi/12.4/en-us/ApiOverview/Events/Events/Install/ModifyLanguagePacksEvent.html

Actions #2

Updated by Garvin Hicking 4 months ago

  • Status changed from New to Closed

I checked back with Georg Ringer who's working also on the Crowdin Translations. We think giving feedback even about possibly local extensions not being fetchable can yield valid feedback and it's currently not planned to drop the feedback about fetch failures here.
We hope with Chris' very helpful comment you can individually suppress these messages for you. Because of that we're closing the issue. If you feel this is a mistake, please let Georg or me know, thanks!

Actions

Also available in: Atom PDF