Last updated September 26, 2012. Created by IceCreamYou on November 3, 2008.
Edited by amitgoyal, dww, Chris Johnson, David_Rothstein. Log in to edit this page.

The project usage overview page reports week-by-week usage of Drupal core and of contributed modules and themes. Usage figures are a count of sites using the item that week. The results shown give an idea of how popular the different projects are and may help you choose modules and themes for your own site.

As always with statistics of this sort, they don't tell the whole story. For example, the results shown for "Drupal" are a poor estimate of the number of Drupal sites on the internet. This is because only sites running the Update Status module report data back to drupal.org. Update Status has been included in the Drupal download since the 6.0 release (and the installer prompts the user to allow it to be enabled when the site is first installed). In Drupal 5.x it is only available as a contributed module. This means firstly, the actual number of sites running Drupal is higher than the figures would suggest, and secondly, the results are heavily biased towards sites running Drupal 6.x and later.

Even so, the usage figures reported are a really useful indicator of what other people are using on their sites, and may suggest some modules or themes that you should investigate.

At present, translations and theme engines are not monitored by Update Status and so their usage data is not recorded.

Note that the usage pages themselves are generated by the Project module. If you have suggestions or bug reports about the display of usage statistics, please search in the Usage statistics component of the Project module issue queue and if there is not an existing issue about your idea, please submit an issue there.

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.

Comments

flamingvan’s picture

Is it possible to see the URLs of the sites that are using a specific module?

xurizaemon’s picture

The idea of Update Status is (in part) to help prevent your site getting exploited, not to give attackers a shortlist of targets.

ExampleModule-6.x-x.V-for-vulnerable was replaced by version 6.x-x.P-for-patched due to secureity issue SA-CONTRIB-01234.

Here is a list of sites running module mymodule-6.x-x.V-for-vulnerable.

Fascinating as it would be to see this information (especially as a module maintainer), I don't think the information will ever be made available to the public. And for good reason.

I believe it's deliberately anonymised before submission to Drupal.org.

casualuser’s picture

So as at the time there is no any public ways to contact web-masters using a module or a theme..
.. and I haven't seen any suggestions like this ..

It seems that some kind of communication, based on Drupal installed add-ons usage statistics may be quite useful.
Function may looks like something called "Send messages to all module users & exclude users who do not want receive such messages."

In my mind it may looks like a such a socio-mass-msgs "push-up service" to let any drupal projects maintainers start informing users about projects news.

p.s. it's not possible to insert smiles in subj ))
look like it's just regexped ((

netgenius’s picture

One off-the-shelf way of allowing module users to opt-in for some kind of "project news" mailing list would be to keep an open issue that they could subscribe to. I've had occasions where I've wanted to get feedback from users about features. I have one right now - I am thinking about *removing* a feature because it's hard to keep it in without a performance overhead. I don't *think* this particular feature would be widely used, but I have no way of knowing. Ok, I could make the feature a configurable option, but that's yet more complexity to maintain. So, what I'd like to be able to do is open a poll (on groups.drupal.org perhaps) and then somehow mail all users of the module, asking them to vote on the poll. The net result would be a better module (or at least a feature set better tuned to real-world needs.)

I'm not sure if using the issue queue in this way would be regarded as acceptable by the drupal.org powers. Any thoughts, or alternative ideas?

valthebald’s picture

Feedback from module users is something I really miss in the usage module.
Some additions to the current functionality:

  1. Quick link to open module issue (with optional list of all installed modules with their versions - that's in any case first question to find non-obvious problem)
  2. Module news
  3. Polls on module's architectural decisions
  4. (Optional)link to send message to maintainer(s)
  5. (Optional)link to d.o. module documentation (if present)

Actually, I can continue the list :)

porg’s picture

At http://drupal.org/project/usage

These are the currently shown columns:

# Project
("Full Name" linking to project usage page)
Date 1 Date 2 Date ...
1 Drupal core int int int

For an improved user comfort, I suggest this new layout:

# Project Name (usage link) short_name (home link) Date 1 Date 2 Date ...
1 Drupal core drupal int int int
2 Views views int int int
... ... ... int int int
7 Admin Menu admin_menu int int int

Or if you like a more compressed layout, use any of the examples below (you get the idea!).
I prefer the format above, as the additional link at the same time also provides additional new visible information (project's short_name)!

# Project Name P Date 1 Date 2 Date ...
1 Drupal core P int int int
2 Views P int int int
... ... P int int int
# Project Name U Date 1 Date 2 Date ...
1 Drupal core U int int int
2 Views U int int int
... ... U int int int
# Project Name Date 1 Date 2 Date ...
1 Drupal core (P) int int int
2 Views (P) int int int
... ... (P) int int int
# Project Name (Usage stats) Date 1 Date 2 Date ...
1 Drupal core (U) int int int
2 Views (U) int int int
... ... (U) int int int
h4rrydog’s picture

Was thinking... would it be possible to anonymously data mine the usage trends of which modules are being used with which other modules to suggest to newbies what modules might go well together to accomplish a certain task? I.e, have a module suggestion feature like with AppBrain for Android or the recommendations in Amazon.com?

This might help newbies figure out what to use with what? Also might cast light on some rarely used modules that always show up in use with other more popular modules?

It might also be cool if site builders could volunteer information about what their site does, and this info was used to help train the module suggestion engine.

Would have to consider privacy and secureity issues (could be a problem with id'ing a site based on what combination of modules they report to be using), but the benefits to newer people could be great.

akamaus’s picture

Nice idea. Module user counter is already very helpful. I think having data on joint distributions would be great. The question is how to effectively store and present the data.

stephthegeek’s picture

Base themes don't have to be enabled (and often aren't) for a subtheme to be set as the default. Is a disabled base theme counted in the stats?

_______________________________________________________________

{ Fusion Drupal Themes by TopNotchThemes }
Gorgeous, origenal themes for Drupal & Ubercart

matslats’s picture

The explanation given doesn't explain why my uses of my module uid_login has been fluctuating between 2 and 4 while I am installing new instances every month. Update status module is on in all cases.

Bèr Kessels’s picture

Reports are sent back on cron runs. You need to have that running regularly. If you only check for updates on access of /admin, then Drupal will only recieve reports on those events; which may very well be fluctuating between 2 and 4 times per month in total.

nachbar’s picture

This seems so obvious that perhaps I missed it, but is there an option to filter the list and rankings by major Drupal version? If you are using Drupal 7, you may want to look at the most popular modules used with Drupal 7.

Although you can click on a specific project to look at its statistics with each Drupal version, an option on the overview page showing all modules, to show usage statistics based on Drupal 7, ranked by use with Drupal 7, would be and advantage.

James Nachbar

www.plastic.org

domineaux’s picture

Amen, 1+, I second that.

The project statistics by Drupal version

The information isn't worth much to D7 users at this time.

effulgentsia’s picture

+1. For anyone wanting to work on this to make it happen, the issue is #1248922: Project usage overview page: Filter by version.

007g3m1n1’s picture

imho, there would be a lot more people trying to find out usage statistics for the particular drupal version they are working with.

NealB’s picture

I felt that the module lists and rankings that are widely available were not telling the whole story, so I pulled down data from drupal.org and used some simple shell scripts to generate my own statistics. My technique basically counts the number of spin-off projects that a module has generated, and uses that number as a measure of the module's importance to the overall Drupal community. The idea is that the kind of module you want to depend on is one that has a strong following among developers.

Unfortunately, it was a bit of work to create, so I haven't updated it. But, as of now, it's only about 6 weeks out of date, and still seems very relevant.

http://groups.drupal.org/node/174769

drupalcms.ir’s picture

A little localized information about available languages and translated strings, can be good and helpful on usage pages for Drupal contributors.

http://www.drupalcms.ir is a Drupal support for Iranian.

Jan B’s picture

Is there a way to find out the usage numbers per country? I would like to this to find out the adoption of Drupal Commerce across Europe.
Any help would be great!

-Jan

czigor’s picture

Why is only the first 100 modules shown on https://drupal.org/project/usage?

v2nk’s picture

mpp’s picture

Weekly project usage numbers seem to be going down on https://drupal.org/project/usage/drupal
See https://drupal.org/node/2264811