11 translation projects are showed on the http://drupal.org/project/usage page, and some of them even have usage count.
So how they ended up on this list and how they can have usage count?

Arabic Translation
Bahasa Malaysia Translation
Polish translation
Turkish Translation (Türkçe çevirisi)
Thai Translation
Catalan translation
Norwegian Nynorsk translation
Czech translation
Belarusian Drupal Translation
Punjabi Translation
French translation

Comments

dww’s picture

Status: Active » Closed (works as designed)

For example, the Arabic translation ("ar") has two records over the past few weeks, both from the same IP, with two different site keys. A few possible explanations for this:

A) Someone intentionally attempting to game the system.

B) A bug in a .info file (e.g. in a site-specific module) that includes "project = ar" which causes update status to query for that. Since translations actually *do* have releases, there are release history XML files available, so updates.drupal.org happily serves up the request and records a usage instance.

I suppose we could special case something here on drupal.org to exclude translations from the usage overview page, and not inject the "view usage stats" links on translation projects and releases...

I'm not even sure the best thing to patch for the usage overview page -- it's not a view, but a (very complex) query built programatically in project_usage itself. It goes through db_rewrite_sql(), so in theory we could have a drupalorg_db_rewrite_sql() function that tries to alter it. Fun! At least there's hook_project_page_link_alter() which you could patch in drupalorg.module to remove the "View usage statistics" link on translation project pages. The link on release nodes comes from project_release_view() (hook_view()) and I don't know the best/easiest way to alter that).

Perhaps we need a setting in project_usage for a way to ignore certain classes of project (based on the project taxonomy?).

Alternatively, we could hack project-usage-process.php to just ignore translation projects and remove those from the usage data entirely.

I'm not terribly inspired to spend time doing any of this. Feel free to set this back to "needs review" with a patch if you are. ;)

Cheers,
-Derek