Increase list of plugin stats

[casiepa]

Some locales have translated the top200 plugins and are now looking for a way to move forward. Can the top200 be increased to top400? In one list or even in 2 pages.

​https://translate.wordpress.org/locale/es-ve/default/stats/plugins/

[nilovelez]

That would be really useful, as some teams have already translated the full top 200!

Even top 300 would be nice.

As for the themes, a list of the top popular themes (or a toggle between popular/most install) would be great.

[YordanSoares]

This would be great! Both teams from es_ES and es_VE locales are keeping the list of plugins and themes up to date. It would be very useful to be able to see the top 300, 400 or 500 (if is possible), maybe paging every 100 or 200 plugins to limit the query. It can be a separate list, if necessary.

Ahead of the opposing opinions to this proposal, as it could be to avoid discouraging the locals who still have many themes and plugins to translate, I suggest managing the access to these bigger lists (if separated) in a private or hidden way, maybe placing the link in the handbook, but not in the GlotPress menu.

We want to have an updated overview and not have to be updating the remaining strings manually using the plugin and themes API, which is how we've been doing it for the plugins and themes that don't reach the top lists. The issue with this method is that the plugins and themes are updated frequently in a short time, sometimes in less than a week, and the exported list, usually a spreadsheet, becomes outdated.

[dd32]

In 9957:

Translate: Show up to 500 items on the per-locale plugin/theme stats overview.

Plugins API is limited to 250 items per page, so we request two pages.

This results in 418 Plugins and 383 Themes being listed. Not all plugins/themes have active Translation projects.

Fixes #5249.

[ramiy]

Why increase the total number? We can add pagination?

[dd32]

Replying to ramiy:

Why increase the total number? We can add pagination?

Was easier to just increase the number in the 5 minutes I had for the ticket, pagination isn't as easy to add sometimes, every page would have a different item count, it'd still have been limited to 1 or 2 pages, as we don't want to have a huge number of pages that make internal api requests, etc.

If it needs increasing in the future, pagination would make sense to look into at that point.