Steps to Reproduce:
- Add configuration for a new project to translatewiki.net
- Update the server - twn-update-config
- Run autoimport
- Once its done, go to Translate a message on Translatewiki.net
Actual Results:
While translating the message, none of the translation aids appear. Reviewing the browser's network request reveals the following response from the translation aid API,
{ "error": { "code": "nomessagefortitle", "info": "Title does not correspond to a translatable message", "*": "See https://translatewiki.net/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes." } }
Expected Results:
The translation aid API should work properly.
Additional details:
My snipped chat with @Nikerabbit
Niklas Laxström, [21.05.19 19:27] I wonder if this is related to the fact that the jobqueue has been running for a while and maybe it had cached the message groups Niklas Laxström, [21.05.19 19:28] It might be useful to add an explicit local cache clear for message groups for that job Abijeet Patro, [21.05.19 19:30] autoimport doesn't currently trigger a recache? Niklas Laxström, [21.05.19 19:31] I believe it does, but the jobqueue process has a in process cache that doesn't get invalidated by that Niklas Laxström, [21.05.19 19:33] Alternative to dropping local caches would be to do it conditionally based on something like isValid() check on the global cache. But I don't know if such thing exists. Niklas Laxström, [21.05.19 19:34] if we are pedantic, I should say datacenter-local cache instead of global :) Abijeet Patro, [21.05.19 19:37] After running createMessageIndex.php, translationaid API works fine. Niklas Laxström, [21.05.19 19:38] Yep, so we are quite sure that outdated messageindex was the reason