Order of the plugins is different compared to the plugin list

Thank you for reporting this. By default, the list should be sorted alphabetically, just like on the Plugins screen. What differences are you seeing?

In Plugin Report, we’re using a javascript sorting mechanism that lets you sort based on a number of columns. Because this is not the same code as WP uses, small differences are probably to be expected.

The big difference has to do with plugin names that use spaces and characters like “-“.

Causing things like, in plugin report:

Word Balloon
WP-Optimize – Clean, Compress, Cache
WP Cloud Plugin Share-One-Drive (OneDrive & SharePoint)
wpDataTables – Tables & Table Charts
WP External Links
WP Menu Icons
WP Search Insights – Privacy-Friendly Search Analytics
WP Tabs Pro
WP Toolbelt

And in the WP plugin list it goes:

Word Balloon
WP Cloud Plugin Share-One-Drive (OneDrive & SharePoint)
WP External Links
WP Menu Icons
WP Search Insights – Privacy-Friendly Search Analytics
WP Tabs Pro
WP Toolbelt
WP-Optimize – Clean, Compress, Cache
wpDataTables – Tables & Table Charts

I’d say both are not ideal, but I’ll add this to my to do list. Perhaps we can tweak the way our plugin sorts so it matched with WP’s results.

Totally agreed. I know the pain of the system like this. At the school I work for, we have this system for our physical library and the book names with “-” and things like that… Urgh, it’s annoying.

Hi @nekojonez

can you please try to sort the table again (click on the triangle in the header of teh name column *two* times – first for reverting sort order and then for correct sort order).

Maybe this is just the unsorted list and there is nothing wrong with the sorting itself … and we just forgot to add the default sorting column.

Thanks in advance!

All the best
Torsten

There will be still differences if the plugin name is translated. “Plugin Report” just uses the original name at the moment.

So sorry for the late reply.
But yes, that fixed it.

Also, I’m luck since my locale (nl_NL & nl_BE) has agreed to not translate plugin names ??

Hi @nekojonez

thanks for confirming my assumption! This will be an easy fix then ??

We have the same policy about not translating plugin names, but sometimes plugin authors use the same string in their plugin (and this time it needs translation), so that the plugin name gets translated also (one of the use cases for context sensitive translations).

Or the translator/editor made a mistake and translated the name by mistake.

All the best
Torsten

I just released version 1.9 of the plugin with fixes to address this issue.

Amazing. ??

So @roytanck I’m placing my suggestions for the Dutch translation and I noticed you might have made a typo in the latest changelog… ?? “inf available” … Isn’t there an “n” too much?

Ah yes, thank you. Corrected for version 1.9.1 which also fixes another small issue.

Oh, let’s close this topic as solved.