detect non-projects and fail gracefully

[NewAmsterdamIdeas]

This module came in very handy for me in compiling data about a website for a security review. I used it in combination with the node_import module to generate a listing of stats for all of the contrib modules in use on the website.

I did notice some bugginess when the module tries to import information about projects that don't have a corresponding project page on Drupal.org. The buggy imports occurred because I compiled my list of modules via a database query to the system table, and some of the modules listed there are submodules of projects rather than actual projects in their own right. JQuery barfed when it tried to retrieve the stats for those modules. I think it would be a good idea to have some failover code that does a better job of handling situations when someone has tried to reference a project page on Drupal that doesn't exist. Wish I had time to write the patch myself, but I thought I should at least post the suggestion.

Thanks again for a great module.

[greggles]

Thanks, @sheldonrampton :)

I gave this a new title, hopefully it matches what you think should happen. It would be great if you could share the script you used for importing. I'm sure lots of other users of the module will want to do that as well.