Opened 6 years ago

Closed 4 years ago

Last modified 4 years ago

#3604 closed defect (bug) (fixed)

Translated plugin states 'This plugin is not translated into en_CA yet'

Reported by: garrett-eclipse's profile garrett-eclipse Owned by: dd32's profile dd32
Milestone: Priority: normal
Component: Plugin Directory Keywords:



I've had Wordfence translated for quite some time but whenever I access the plugin page I find the notice;
"This plugin is not translated into English (Canada) yet. Help translate it!"

Plugin Page -

But if you look on translate that locale is 100% and has been for a while (months).


Attachments (2)

Screen Shot 2018-05-03 at 10.32.47 AM.png (347.6 KB) - added by garrett-eclipse 6 years ago.
Wordfence Plugin Page
Screen Shot 2018-05-03 at 10.32.56 AM.png (158.9 KB) - added by garrett-eclipse 6 years ago.
Wordfence Translations

Download all attachments as: .zip

Change History (10)

6 years ago

Wordfence Plugin Page

6 years ago

Wordfence Translations

#1 @ocean90
6 years ago

  • Component changed from Translate Site & Plugins to Plugin Directory
  • Resolution set to invalid
  • Status changed from new to closed

The readme is, but in this case it's about the plugin itself which is sadly not properly prepared for localization. I suggest to contact the plugin author.

#2 @garrett-eclipse
6 years ago

Thanks @ocean90 I didn't realize it was the plugin itself that was a requirement. I've spoken to them before and they're looking into for the future but isn't pressing to them.
I guess the main confusion from a user perspective is going through that link expecting something to translate and finding 100% can be confusing. Can that message be updated when plugin doesn't support localization?

#3 @SergeyBiryukov
6 years ago

The page already says "This plugin is not properly prepared for localization", though I guess the notice could be missed. Maybe it should be red instead of orange?

Or maybe the symbol in Development and Stable columns should be changed to 0% for clarity?

#4 @garrett-eclipse
6 years ago

Thanks @SergeyBiryukov the messaging on the translation page is great. My confusion was more when you're on the plugin page;
"This plugin is not translated into English (Canada) yet. 'Help Translate It'"

This caused me to hop through the link to translate it which is where I found and realized the cause being it not prepared. So if anything the messaging on the plugin page itself could reflect the fact it's not able to be translated due to it not properly being prepared. That way I don't bother diving into the translation as whenever I see that link on a plugin I use I want to go and translate it.

Something like;
"This plugin is not translated into English (Canada) because it's not properly prepared for localization."
*Then drop the link as there's no point trying to 'Help Translate It'

Thanks again,

Last edited 6 years ago by garrett-eclipse (previous) (diff)

#5 @garrett-eclipse
6 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

Reopening to have my last comment taken into account.

#6 @dd32
4 years ago

  • Owner set to dd32
  • Resolution set to fixed
  • Status changed from reopened to closed

In 9667:

Plugin Directory: Only show the "Localise this plugin!" locale banner if the plugin is prepared for translations.

Fixes #3604.

#7 @dd32
4 years ago

In 9668:

Plugin Directory: Switch the locale banner to a GET request and cache the request for up-to 1 hour.

See #3604.

#8 @dd32
4 years ago

In 9669:

Plugin Directory: Locale Banner Caching: Only output a single Vary header, as we don't need CORS for this API endpoint.

See [9668].
See #3604.

Note: See TracTickets for help on using tickets.