- 🇫🇷France fmb Perpinyà, Catalonia, EU
Will be dealt with in 📌 Finalize l10n_packager route /downloads. Active .
The front page stats (l10n_community_welcome_page()) uses l10n_community_get_l10n_packager_string_count() on localize.drupal.org to display stats of the featured project. l10n_community_get_l10n_packager_string_count() in turn picks the last release that has .po files exported with this query:
if (empty($rid)) {
$rid = db_query("SELECT pf.rid FROM {l10n_server_release} sr INNER JOIN {l10n_packager_file} pf ON sr.rid = pf.rid WHERE pid = :pid ORDER BY pf.rid DESC LIMIT 0, 1", array(':pid' => $pid))->fetchField();
}
This is unfortunate for projects with multiple active release branches like core. The front page may show D6, D7 or D8 stats based on which release is the latest at the time (which is mostly arbitrary). So Drupal may show as VERY WELL translated (D6) or mostly well translated (D7) or not so much translated (D8). We should figure out a way to improve this so the stats don't fluctuate so much depending on last releases.
The trick is the module obviously wants to be agnostic of what projects it is being used for, so maybe we need to add something like a 'release series' input field to the featured release settings to limit which releases are looked at for the last ones. And also ideally print the information on which release was taken into account above or below the stats for clarity and transparency.
Closed: duplicate
3.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Will be dealt with in 📌 Finalize l10n_packager route /downloads. Active .