Plugin directory not updating translations

[webdados]

It seems that there's a problem with the plugin directory translations not being updated from the Glotpress strings

Example:
​https://pt.wordpress.org/plugins/shop-as-client/
​https://translate.wordpress.org/locale/pt/default/wp-plugins/shop-as-client

Both development and trunk readme are fully translated for Portuguese (for more than 24 hours now) and the translation is still not updated on the Portuguese version of this plugin page on the repo.

[webdados]

Additional info, maybe this is related to the recent server migrations: ​https://wordpress.slack.com/archives/C02RP50LK/p1518087600000282

[ocean90]

This seems to work now.

[webdados]

This problem persists.

Example: ​https://pt.wordpress.org/plugins/multibanco-ifthen-software-gateway-for-woocommerce/#description

And the first paragraphs of the readme are already translated: ​https://translate.wordpress.org/projects/wp-plugins/multibanco-ifthen-software-gateway-for-woocommerce/dev-readme/pt/default?filters%5Bterm%5D=&filters%5Buser_login%5D=&filters%5Bstatus%5D=current&filter=Filter&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

[webdados]

As stated by @pedromendonca on Slack this should be solved globally and not per plugin: ​https://wordpress.slack.com/archives/C02RP50LK/p1519150166000589?thread_ts=1519116163.000150&cid=C02RP50LK

[pedromendonca]

I wonder if this issue is related to the fact that the Readme is being loaded from the variant AO90 instead of the Default one, as reported in https://meta.trac.wordpress.org/ticket/3472.
This recurrent problem definitely needs a global solution, instead of a fix on demand, per project.

[webdados]

It shouldn't be related because there are strings translated on the AO90 variant that are also not showing, correctly, on the Portuguese page of the plugin: ​https://translate.wordpress.org/projects/wp-plugins/multibanco-ifthen-software-gateway-for-woocommerce/dev-readme/pt/ao90?filters%5Bterm%5D=&filters%5Buser_login%5D=&filters%5Bstatus%5D=current&filter=Filter&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

[ocean90]

In 6701:

Plugin Directory: Use the default translation set of a locale for readme translations.

Fixes #3438.
Fixes #3472.

[webdados]

I'm not sure this will fix the issue with translations not updating at all, as I stated here: https://meta.trac.wordpress.org/timeline?from=2018-02-20T22%3A54%3A50Z&precision=second

I've just translated another string on the mentioned plugin to try to force the update from Glotpress to the repository to happen. Let's wait and see.

[webdados]

For now, what we are sure is that if we change a translation from current to fuzzy and back to current, that translation is automatically added to the plugin page on the repository, in real time.

If we translate a string that has never be translated before, and we leave it current, it does not propagate to the repository in real time. We've made some translations and will wait a few hours before reopening this ticket (if needed).

[pedromendonca]

I've found a small difference in behavior.
Despite translating in dev-readme or stable-readme sub-projects propagates to the other one, translating in dev-readme do not show up in the translated plugin page, but translating in stable-readme works perfectly, real time.

[webdados]

So, we still have some issues:

• When translating on stable-readme all is propagate to dev-readme and goes to the repository automatically

All good

• When translating on dev-readme, it's propagated to stable-readme but does not update the repository

In this case, we then have to go to stable-readme and force the strings to fuzzy and then current again for them to go to the repository

[ocean90]

See #3475.