Show latest plugin import errors on GlotPress project page

[SergeyBiryukov]

When a plugin cannot be translated, there's a notice on the project page:

This plugin is not properly prepared for localization (View detailed logs on Slack). If you would like to translate this plugin, please contact the author.

To find out what's wrong, one has to search the #meta-language-packs channel on Slack for a message like this:

Plugin is not compatible with language packs: Missing text domain in header. (1.98s)

It would save a lot of time for both plugin authors and users contacting them if the message was displayed on the project page itself, without having to search Slack.

[obenland]

Example:
​https://translate.wordpress.org/projects/wp-plugins/lazyeater
​https://wordpress.slack.com/archives/C0E7F4RND/p1516212814000798

[casiepa]

I see multiple ways of showing this:

• In a table, something like ​https://plugins.trac.wordpress.org/log/bbpress/
• The last 3 messages could be added to the plugins api: ​https://api.wordpress.org/plugins/info/1.1/?action=plugin_information&request[slug]=bbpress or to ​https://api.wordpress.org/translations/plugins/1.0/?slug=bbpress

But whatever the way, it would be an enormous help if we could link to it in a unique way somewhere on wordpress.org (so out of slack).

[ocean90]

We're using Slack because it allows us to store and search the data quite easily. I'm currently not convinced that this is important enough to store the same data in another way so that's accessible there.

I'd rather drop the errors related to missing/invalid text domains and convert those to warnings and let the import happening.

[casiepa]

@ocean90,

Thanks for checking this one out, pity it won't be resolved now.

Not all plugin authors are on slack, so I was hoping to be able to change the message like on ​https://translate.wordpress.org/projects/wp-plugins/wd-twitter-feed to something more useful without the need for slack.

[SergeyBiryukov]

Replying to ocean90:

We're using Slack because it allows us to store and search the data quite easily. I'm currently not convinced that this is important enough to store the same data in another way so that's accessible there.

It works fine for logging purposes, not so much for explaining the issue to plugin authors, which can be time-consuming as is, especially if they're not on Slack.

Displaying the notice in plain text on the project page would make the issue more obvious, save a lot of back-and-forth, and result in more time spent on actual translations.

But I guess someone would have to write a patch first :)

I'd rather drop the errors related to missing/invalid text domains and convert those to warnings and let the import happening.

Missing or invalid text domain generally means the plugin won't be able to use the translations properly, so that seems like it would cause even more confusion when trying to find and explain the issue.

[SergeyBiryukov]

Related: #1675

[SergeyBiryukov]

Related: #4455

[ocean90]

#4976 was marked as a duplicate.