Issue Bug Closed

#82287Better error reporting for language module

Stefan Froemken 09/04/17, 16:09 updated 12/02/25, 14:36

Description

Hello core-Team,

currently the download of translations for TYPO3 does not work:
https://git-t3o.typo3.org/t3o/ter/issues/207

As a user everything seems to work in Language BE Module. The status bar fills up and on some systems the typo3conf/l10n Folder will be filled again.

In source code there are some try-catch where the catch part consists of a simple comment, only:

} catch (Exception $exception) {
    // @todo logging
}

I have debugged AJAX network traffic with Chrome while updating translations. A valid JSON will be response, but its state part is 2 (static::TRANSLATION_FAILED), but the user does not get any useful hints about that.

Switch to “Translation Overview” and try to get a translation for a single extension like “about”. It seems to work. You got success messages. The icon has changed to a success icon. But in the background nothing works.

Would be cool to have valid messages and UX in translation module

Stefan

Reviews 2

Files 1

History 1216

  1. Mathias Brodala commented <span data-processor="relativetime" data-value="2017-09-06T10:18:46+00:00" > 09/06/17, 10:18 </span>

    Alexander Opitz wrote:
    > Duplicate of #82286 ?

    This ticket is more about feedback not a specific error.

  2. Stefan Froemken commented <span data-processor="relativetime" data-value="2017-09-06T12:45:28+00:00" > 09/06/17, 12:45 </span>

    This is not a duplication of #82286. It shows a problem about language files which can not be downloaded. This will be solved today night: https://git-t3o.typo3.org/t3o/ter/issues/207#note_5383

    In my ticket I want to have a better error reporting to the customer/user, as currently everything seems to work (success messages), although it doesn’t in the background.

  3. Benni Mack commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2020-01-09T16:04:13+00:00" > 01/09/20, 16:04 </span>

    Hey Stefan,

    we’ve improved the situation in TYPO3 v9, can you let us know if this has changed for the better?

  4. Stefan Froemken commented <span data-processor="relativetime" data-value="2020-01-10T08:49:19+00:00" > 01/10/20, 08:49 </span>

    Hi Benni,

    I have unplugged my Network Cable and tried it again.
    I see the light blue progress bar, what is OK for me.
    After that I see following:

    Language packs updated
    0 new language packs downloaded, 0 language packs updated, 51 language packs not available

    with a green background, which is IMO wrong.

    Further the message “51 language packs not available” is wrong, too, as there is a german package for “about” available.

    The user still won’t be informed that there is a network error.

    Stefan

  5. Georg Ringer commented and changed status Needs Feedback Accepted TYPO3 Version 8 9 <span data-processor="relativetime" data-value="2020-03-06T21:40:40+00:00" > 03/06/20, 21:40 </span>

    confirmed on master

  6. Gerrit Code Review pushed patch set 1 for main to change 90098 status Accepted Under Review <span data-processor="relativetime" data-value="2025-07-18T15:54:32+00:00" > 07/18/25, 15:54 </span>

  7. Andreas Nedbal commented and changed attached Screenshot 2025-07-18 at 17.56.42.png <span data-processor="relativetime" data-value="2025-07-18T15:59:34+00:00" > 07/18/25, 15:59 </span>

    I fixed this with making the AJAX error handling resilient to actual JS errors (previously it’d catch a response only), so if a NetworkError occurs (when becoming offline for example) this (see attached screenshot) is now displayed.

    To replicate this, open the maintenance module and the language packs selection, have a pack added and before trying to update it, set your network throttling in the DevTools to “Offline” and press the update button. Instead of freezing at “x language packs downloaded”, it will directly show the network error.

  8. Andreas Nedbal commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-07-29T06:15:08+00:00" > 07/29/25, 06:15 </span>

    Applied in changeset commit:57eabf04edea6f6d6f63113d5bc785fb39c693ae.

  9. Benjamin Franzke commented <span data-processor="relativetime" data-value="2025-07-29T06:48:35+00:00" > 07/29/25, 06:48 </span>

    Crosspost of https://review.typo3.org/c/Packages/TYPO3.CMS/+/90098/4#message-60965381823bbbd9d8f9b50f898360bfa5d05df8

    > This patch only fixes the case when the connection from client (browser) to the application server (TYPO3 instance) is broken, but not the case when the connection between TYPO3 instance and TYPO3 language server does not work, that case produces 500 responses.
    >
    > These are actually catched, but the result is shown in a green bar, so that it is hard to detect that a language pack was not just unavailable, but failed to load.
    >
    > > Language packs updated
    > > 0 new language packs downloaded, 0 language packs updated, 0 language packs > skipped, 46 language packs not available
    >
    > We need to differentiate between language packs not being available (404 sent by the language server) and any other 4xx or 5xx or network error that occured when talking to the lanuage server.

    Do we all agree, that this ticket should be re-opened?

  10. Garvin Hicking commented <span data-processor="relativetime" data-value="2025-07-29T07:06:48+00:00" > 07/29/25, 07:06 </span>

    Fine by me to re-open, but we might also open a fresh ticket as a follow-up for the further improvements?