WordPress.org

Making WordPress.org

Opened 21 months ago

Closed 21 months ago

Last modified 5 months ago

#3385 closed enhancement (maybelater)

Show latest plugin import errors on GlotPress project page

Reported by: SergeyBiryukov Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

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.

Change History (8)

This ticket was mentioned in Slack in #meta-i18n by sergey. View the logs.


21 months ago

#3 @casiepa
21 months ago

I see multiple ways of showing this:

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).

#4 follow-up: @ocean90
21 months ago

  • Resolution set to maybelater
  • Status changed from new to closed

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.

#5 @casiepa
21 months ago

@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.

#6 in reply to: ↑ 4 @SergeyBiryukov
21 months ago

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.

Note: See TracTickets for help on using tickets.