Badges has been recently added to core components, however AMOS still consider it as non standard plugin, at least checking today. I'm missing something ?
Hi Andrea
we've the same problem with behat.php. Seems that some developer have added lang files at the wrong location or some other processes have changed.
Ralf
No. AMOS just does not detect standard components automatically yet. They must be white-listed manually. I found couple of other missing standard components (like cachelock and cachestore plugin types) and fixed them now. Thanks for the report.
Hello David
thanks for the information. One additional question:
Can we start translation of new core lang files if they are defined as contrib before you've whitlisted them. Will they also appear as standard lang package files afterwards? Or should we wait until you've whitelisted them?
Ralf
Yes. You can safely work on any component in AMOS. If it is put to the "standard components" whitelist or not does not have any consequence on translation data or their distribution. The translation is not lost. The only two things it affects are:
- Standard components are displayed as such in the Translator filter form field
- Their strings are counted into the translation stats at download.moodle.org pages
All your translations, be it for standard modules or not, are included in generated ZIP files. So sites have them available even if they do not have those add-ons installed. It was designed this way so that when a contributed add-on is installed, it is immediately available in the localised version (if such translation exists).
So shortly, yes. You can translate any component in AMOS even before it is whitelisted.
Hi David,
I think tinymce_ctrlhelp , theme_simple and tinymce_spellcheckers might also be unrecognized core components of Moodle 2.5dev. They just appeared in one 2.5dev update yesterday.
Thanks in advance for your help
Hi David,
I think that theme_clean might also be a core component of 2.5dev.
Thanks in advance for your help.
Hi German. You're just too quick It's fixed now, thanks.