Hi!
I am happy to announce some new features now available in the Moodle plugins directory. I am particularly happy today for these, not only because they were lurking on the todo list for a while. But primarily because they were often suggested by you - the marvelous Moodle community members Let's have a look what just landed.
Plugin translation stats
There is a new tab Translations on every plugin's page. It gives the information about the number of text strings defined by the plugin and registered with the AMOS - the Moodle translation tool. And even more, there is also a chart with translations stats of the given plugin. That is, into what languages the plugin is translated and what is the translation completeness ratio.
The existing link to contribute translations for the given plugin has been moved from the Useful links section on the plugin's main page to this new Translations page.
Strings are registered asynchronously with AMOS
Originally, the strings defined by the plugin were registered automatically as a part of releasing a new plugin version (or editing the existing version record). This could occasionally lead to delays in the release process as the maintainer had to wait for the AMOS to process the new strings. If there was a problem with strings registration, it was not logged. Making it more challenging for the maintainer to remember what the error message was.
Recently, this integration with AMOS has been rewritten so that it happens asynchronously in the background via a scheduled task. Every time a new plugin version is released, or the existing version record is updated, the plugin is marked as "Pending" and it is scheduled for re-check with AMOS. Shortly, typically within minutes, a scheduled task runs in the background that processes such pending plugins.
Starting from today, the plugin's Developer zone page contains a log of all these asynchronous updates of the plugin's strings with AMOS - together with their status. This allows the maintainers to make sure the plugin strings are registered correctly and are ready to be translated by the community translators.
Public list of not yet approved plugins
This idea has been reopened again during the recent discussions in this forum. Shortly, a new report is now available at Plugins > Reports > Not yet approved plugins page. All the plugins that have been submitted to the Plugins directory but are not yet approved, are listed there. Together with the links to the approval issue in the tracker and the plugin's native Git repository. Please refer to the other thread for details on why and when this can be useful.
Improved display of the plugin's previous versions
And yet another suggestion was brought in during the great DevJam session at the Moodle MootDE17 in Mannheim. Alexander Bias, a recognized Moodle community developer, came with solid reasons why the current display of all the plugin versions - including all those very old or even hidden ones - is not helpful and makes the page confusing. Especially for plugins with a long development history with many releases.
Finally, today's update brings a new display of the plugin's previous versions. Their list is now presented via a drop-down menu. It still allows the user to find details about a particular legacy version if it is needed. But the list of these versions is not that prominent any more and the users are encouraged to download and install latest versions only, as it should be.
Many thanks everybody for your useful suggestions and ideas on how to make Moodle even more awesome project
Kudos to David Mudrák for the many improvements.
Awesome !
The list of available translations will be very useful for Moodler administrators with multi-lingual sites and sites using a main language different to English, who are contemplating installing additional plugins.
One minor issue I noticed when I checked the Translations tab for the qtype ordering plugin:
Number of strings defined by the plugin: 48
But AMOS only shows 47 English language strings available for translation.
And four languages show a 98% percentage of language strings translated.
Most other plugins I have checked show perfect 100% percentages.
Very well spotted Germán! Thanks for raising it.
The one extra string is
$string['pluginname_link'] = 'question/type/ordering';
present in the English language pack only. By design, strings ending with the "_link" suffix are not available for translations in AMOS. This is to make sure that they contain the correct value in all languages. The value is then used to construct the "More help" links in the help tooltips.
These strings are currently present in the English pack statistics by mistake. I'll look at that ASAP.
Thanks again for letting me know.
It should be fixed now.
Thanks David for all these nice improvments
Concerning the Public list of not yet approved plugins, it's nice to be able to sort it.
But seeing the big number of elements, it would be still better to also be able to filter/search in it.
Séverin
Thanks Séverin.
it would be still better to also be able to filter/search in it
Meanwhile, if you really need it, click the number of the plugins in the report description to show them all, and then use the browser's "Search in page" feature.
Hi David,
I am afraid that some very successful plugins, such as the HotPot plugin, have so many translations that it is impossible to figure out the languages supported. Can this be fixed ?
Can this be fixed ?
As far as I know, it is the default behaviour of the core charts API. I am not aware of a simple way to fix it.