Hello, I’m the author of…


I’m the author of Leyka pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.

Some time ago, we successfully migrated our plugin localizations to the GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details..

But now we see a problem with dev and stable localesLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ refreshing. Any commit to the plugin folders in WordPress repository (be it trunk or tags) doesn’t trigger the plugin code rescanning to find new lines.

At the same time, Loco Translate and PoEdit see all lines changes. E.g., right now in the Loco Translate the plugin trunk folder includes 1023 lines (77 are not translated yet). But the GlotPress plugin directory sees only 964 lines (all of them are translated).

We’ve tried exporting the current *.po file and importing it in GlotPress plugin directory, but to no effect. GlotPress tells that “0 new lines imported”.

What are we doing wrong, and how can we initiate the plugin locales refresh?

Thanks in advance.