Plugin Search: Search by translated plugin name

[SergeyBiryukov]

I've translated my ​Allow Cyrillic Usernames plugin's title into Russian. So far so good.

However, when I ​search by the translated plugin name in the directory, there's only one unrelated match (Pro Related Post Widget).

This would be confusing and unexpected for users. It raises the question of whether translating or transliterating plugin names is a good idea. I think it might be, as long as users can find the plugin by a translated name.

[samuelsidler]

So... this should be working in the new directory, but doesn't appear to be. You can play around ​here.

[SergeyBiryukov]

Replying to samuelsidler:

You can play around ​here.

I can't even find the plugin by the ​original name there :-/ See meta-1496.png​.

[Ipstenu]

This seems to be working now @SergeyBiryukov ?

[SergeyBiryukov]

Replying to Ipstenu:

This seems to be working now @SergeyBiryukov ?

comment:3 appears to be fixed, but the initial issue of searching by a translated plugin name is still relevant.

[SergeyBiryukov]

Related: #2425

[SergeyBiryukov]

Replying to SergeyBiryukov:

comment:3 appears to be fixed

Hmm, search only works in the English directory at the moment, probably because of #2425:

• ​https://wordpress.org/plugins-wp/search/allow+cyrillic+usernames/ -- shows the correct plugin.
• ​https://ru.wordpress.org/plugins-wp/search/allow+cyrillic+usernames/ -- shows "Sorry, but nothing matched your search terms."

[SergeyBiryukov]

Searching by the original name appears to works as expected now in both English and Russian directory.

Searching by the translated name only works in Russian directory:

• ​https://ru.wordpress.org/plugins/search/имена+пользователей+на+кириллице/ -- shows the correct plugin.
• ​https://wordpress.org/plugins/search/имена+пользователей+на+кириллице/ -- shows "Sorry, but nothing matched your search terms."

Given that the English directory only displays the original name, I think that's fine (although it would be great to have a consistent search behaviour on English and local directories).

However, searching by the translated name from WP admin with Russian locale still doesn't work: "No plugins match your request".

[ocean90]

#2812 was marked as a duplicate.

[yoavf]

One more example:

Searching for transliterated Woocommerce "ووكومرس" on ​https://ar.wordpress.org/plugins/search doesn't return "WooComerce" but another plugin that has "ووكومرس" in its tags.

[gibrown]

Thanks @yoavf

It looks like the problem here is that there are no translations for WooCommerce coming through Jetpack onto WP.com.

I'm not sure why. I know these were working at one point and I thought this ticket had even been closed.

[tellyworth]

This looks to be vastly improved as of [6198]. ​https://ru.wordpress.org/plugins/search/Имена+пользователей+на+кириллице/ and ​https://ar.wordpress.org/plugins/search/ووكومرس both appear to show appropriate results.

[SergeyBiryukov]

Replying to tellyworth:

This looks to be vastly improved as of [6198].

• Still no luck when searching for "имена пользователей на кириллице" from WP admin.
• Any chance for the main directory to return appropriate results as well? ​https://wordpress.org/plugins/search/имена+пользователей+на+кириллице/ still shows "Sorry, but nothing matched your search terms."

[felipeelia]

Hi folks. Just passing here to contribute with two examples of plugins with translated names in pt_BR. These can help because we also use the Latin Alphabet and maybe it makes the tests easier.

1. We've translated the "Classic Editor" plugin as "Editor clássico". When we search for "Editor clássico" in the pt_BR directory, the plugin isn't found:

​https://br.wordpress.org/plugins/search/Editor+cl%C3%A1ssico/
but it's the first result when we search for "Classic Editor":
​https://br.wordpress.org/plugins/search/Classic+Editor/

2. As "Editor Clássico" contains that "a-acute" (á), we could imagine that is the problem. But there is a plugin called "Related" that is translated as "Relacionado". Searching for "Related" it's the 11th result:

​https://br.wordpress.org/plugins/search/related/
Searching for "Relacionado" it doesn't even appear in the results:
​https://br.wordpress.org/plugins/search/relacionado/

I hope it helps you, folks, to get this figured out. It's very problematic especially for cases like the Classic Editor, where the user reads the plugin name on a Panel notice, for example, but can't find it while searching for it in the Dashboard.

[SergeyBiryukov]

Related: #4604

[dufresnesteven]

@felipeelia. Can you double check your results? It appears to be working for me.

[felipeelia]

Hi @dufresnesteven,

Yeah, I'm happy to say it is working fine now :) It is worth mentioning that it still does not work on the WP Dashboard though. Thanks!

[dd32]

In 10352:

Plugin Directory: Ensure that all locale translated text gets synced to postmeta so as to get synced to Jetpack ElasticSearch.

See #1496.

[kinging]

This issue still doesn't seem to be resolved...

My plugin, Ivrita is translated to Hebrew as עבריתה, but doesn't show up when searching for it's Hebrew name in he.wordpress.org. It does show up with the Hebrew name when searching by its English name: ​https://he.wordpress.org/plugins/search/Ivrita/

I can see other plugins which can be searched for by their localized names, is there anything I need to do in order to index my plugin's localized name as well?

[dd32]

In 10506:

Plugin Directory: sync_all_translations_to_meta() can't accept a Post ID, only a WP_Post object or plugin slug.

See [10352].
See #1496.

[dd32]

Thanks for the report @kinging It looks like your plugin is now showing up in a translated search: ​https://he.wordpress.org/plugins/search/%D7%A2%D7%91%D7%A8%D7%99%D7%AA%D7%94/

[kinging]

Replying to dd32:

Thanks for the report @kinging It looks like your plugin is now showing up in a translated search: ​https://he.wordpress.org/plugins/search/%D7%A2%D7%91%D7%A8%D7%99%D7%AA%D7%94/

Thanks for the reply. To be honest, I gave up on fixing it so I ended up adding the translated name as a tag in the readme.txt file, which I heard should work (and it does). But up until that moment when I pushed the new readme file, it didn't show up in the searches.

[dd32]

Replying to kinging:

Replying to dd32:

Thanks for the report @kinging It looks like your plugin is now showing up in a translated search: ​https://he.wordpress.org/plugins/search/%D7%A2%D7%91%D7%A8%D7%99%D7%AA%D7%94/

Thanks for the reply. To be honest,

Interesting work around! FWIW it wasn't showing up previous to my above commit if I recall correctly, after fixing that I watched the translated title get ingested into the search engine, and then start returning in results..

I've disabled tags for searching purposes momentarily, and your plugin still continued to get matched, so the translations are now being respected. It was simply that the translations weren't being indexed properly.

[dd32]

Replying to dd32:

I've disabled tags for searching purposes momentarily, and your plugin still continued to get matched, so the translations are now being respected. It was simply that the translations weren't being indexed properly.

I'll clarify that though, I can still see some ways it's not working as intended, text that is in the description of the plugin that should be matching doesn't appear to (but looks like it should be in the index, although i haven't checked directly), so I'll have to look further into that (potentially checking another locale to determine if it's specific to hebrew or translations)

[kinging]

Thank you for your work on this issue! Perhaps your commit and my tag addition happened at the same time :D

If there's anything I can do to help figure this out, e.g. add translations for another locale - let me know.
(Although I'm not the PTE for other locales so it would require someone to approve them)