I am looking at a site which is currently running 5.19 and we would like to bring it to 6.x or 7.x. Before diving in, I would like to research module availability and status to see whether 7.x is a reasonable target and whether or not there were any issues about modules we are using that have fallen by the way side.
I have the list of installed modules on the current site, their versions, and whether or not they are enabled. I am having trouble matching this to module names on the current list of modules. E.g., we have a thing that shows up on our module page as ImageMagick Advanced Options, but when I look on the drupal.org module index all I see is ImageMagick and that appears to be a 7.x only module. Huh? How do I find out what name to look under on Drupal to find out what we have installed.
I also don't seem to be able to find a list of modules in core to see if something we used to use a contributed module for is now in core.
Comments
Have you tried running the
Have you tried running the upgrade status module? http://drupal.org/project/upgrade_status
No, I haven't. I am used to
No, I haven't. I am used to that functionality from Drupal 6, but even if I could get the other admins to install it on the D5 system, I'm not sure that it would give me what I need ... which is to provide us with a map which shows for each existing module, whether or not there are releases for D6 and D7, what the nature is of those releases (dev, alpha, beta, released), the maintenance status, and the number of sites using the module. This will determine whether or not it is reasonable to move to D7 at this point and what modules we might have to decommission or replace. I am simultaneously considering the modules in use at my other four sites which are on D6 now to see what modules might be good additions to this site. So, having a clear map connecting module name on Admin Modules page to the name on the Modules index of Drupal.org and the directory name of the installed software would be a big plus.
And, of course, having a clear way to know whether something had moved into core would help too.
What file do I look at in any
What file do I look at in any given modules directory to find what modules it corresponds to?
_
You should be able to match the directory names of the modules to their drupal.org url, for example, the 'cck' module maps to http://drupal.org/project/cck.
That works for many, but
That works for many, but there are cases of multiple modules on the admin module list but only one directory. I *think* I have all the pairings now, but it seems like there should be some easier way to be definitive. E.g., there are two directories in sites/all/modules related to images - img and img_assist, but the admin modules page shows 6 modules in the image category. I can guess confidently that Image Assist is img_assist and I can guess that the other 5 are all in img since they are the same version, but it would be nice to be more sure.
Oh, and it is http://drupal.org/project/image not http://drupal.org/project/img
_
Each project can consist of multiple individual modules, true-- but they still belong to the same drupal.org project (unless of course you just happened to copy additional unrelated modules to the directory of a different module).
The 'packages' listing at admin/build/modules is completely different and a method of categorizing projects loosely based on functionality.
You can also go the update status listing and open the link associated with the module name--that will lead you directly to the appropriate drupal.org project page.
Yes, but my problem was in
Yes, but my problem was in trying to develop a matrix of what did we have installed now, what were we actually using, and what was the status of those modules in D6 and D7. I.e., I wanted to see whether D7 was a reasonable target, what modules were not available, what was and wasn't being actively maintained, what might be available but at a questionable release level, etc. With this we hoped to plan a migration including evaluating replacements, discarding unused code, etc. To do that I needed a way to go from the module name on the admin modules page to the project page on Drupal.org. I *think* I have a reasonable map now, but it took a lot of guessing.
And the update status listing is not a standard feature of D5. I know there is a contrib module which does something like what is in D6, but it is not currently installed at this site. I am used to it from my D6 sites and am looking forward to having it available.