Translate: /projects/meta/ shows 208 locales with all-zero stats

[motylanogha]

​https://translate.wordpress.org/projects/meta/ renders a locale table of 208 rows in which every single counter is zero. I checked programmatically rather than by eye: 208 locale rows, 0 of them with a non-zero value in translated, fuzzy, untranslated or waiting.

It is reachable from the breadcrumb on every Meta sub-project page, e.g. on /projects/meta/wordcamp/:

<ul class="breadcrumb"><li><a href="/projects/">Projects</a></li><li><a href="/projects/meta/">Meta</a></li><li>WordCamp.org</li></ul>

so a translator following it lands on a page implying that nothing in Meta is translated at all, which is false: /projects/meta/wordcamp/ alone has 179 locales, 140 with non-zero counts.

This is a data anomaly rather than a rendering bug

The Meta parent project has translation sets attached while carrying no originals of its own. The other container projects have none, which is why they render no such table:

URL	Result
/projects/meta/pl/default/	200, empty translation table
/projects/wp/pl/default/	404
/projects/wp-plugins/pl/default/	404

And on the project pages themselves:

Page	percent cells rendered	of which 0%
/projects/wp/	0	0
/projects/wp-plugins/	0	0
/projects/wp-themes/	0	0
/projects/meta/	208	208

So Meta is the only one of the four container projects with translation sets on the parent. GlotPress renders the table because the sets exist; they are simply empty, because the parent has no originals.

Suggested fix

Two options, and I think both are worth doing:

1. Data, and it fixes this immediately: remove the empty translation sets from the Meta parent project. /projects/meta/ then behaves like /projects/wp/ -- sub-project list only, no misleading table. No code change.
2. Upstream, and it fixes the class of problem: have GlotPress skip the translation-set table when the project has no originals. Any install with container projects benefits, and it stops the same thing recurring if sets are ever created on a parent again.

I have not touched anything; option 1 needs someone with access to the projects. Happy to open the GlotPress issue for option 2 if that seems worthwhile.

Filed alongside #8396, which is a separate problem on the same set of pages.

[ocean90]

Thanks! This is expected, and we use it to easily set up new projects. There's nothing that needs to be 'fixed'.