[META] Porting localization server module to Drupal 9

Created on 8 April 2022, over 2 years ago
Updated 20 October 2023, about 1 year ago

Problem/Motivation

Localize is still using D7, we need to migrate it to D9. One of the main blocker for this is the l10n_server module. This issue focuses on porting this module to D9.

Proposed resolution

There are currently 3 different contexts, using each a dedicated connector:

File upload (eg drupal.8.7.po): l10n_gettext
Folder containing tar.gz files: l10n_drupal
Pulling a .tsv file from drupal.org: l10n_drupal_rest (this is the one used on localize.drupal.org)

The core feature that we want to focus on at the moment is the l10n_drupal_rest connector, as it is the only one coming from drupal.org and it allows Localize to get the full list of existing projects ( https://www.drupal.org/files/releases.tsv β†’ ).

There is a strong dependency to l10n_community within the current code, but its features are specific to localize.drupal.org: it displays the latest Drupal core translation status and data. So we agreed that there is no need to require it within l10n_server for now, we will port the code without these features - they should probably live in a dedicated localize module.

Development setup

We have a D9 platform branch here πŸ“Œ Create a new D9 platform Closed: outdated to simplify the team work.
Please see the README: https://git.drupalcode.org/issue/localizedrupalorg-3273538/-/tree/327353...

Remaining tasks

Others:

πŸ“Œ Task
Status

Closed: outdated

Version

3.0

Component

Code

Created by

πŸ‡«πŸ‡·France nicoloye

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024