[wp-meta] [Making WordPress.org] #3385: Show latest plugin import errors on GlotPress project page

Making WordPress.org noreply at wordpress.org
Wed Jan 31 05:26:35 UTC 2018


#3385: Show latest plugin import errors on GlotPress project page
--------------------------------------+-------------------------
 Reporter:  SergeyBiryukov            |       Owner:
     Type:  enhancement               |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  Translate Site & Plugins  |  Resolution:  maybelater
 Keywords:                            |
--------------------------------------+-------------------------

Comment (by SergeyBiryukov):

 Replying to [comment:4 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.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3385#comment:6>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list