Downloading All Modules
craigmeister429 - November 8, 2005 - 17:54
My boss is going for Drupal in a big way. He wants me to get all of the modules that are currently available on this site. Is there a smart way to do this, i.e. something less tedious than doing all of the DL's individually? I could write a script, I suppose, but don't see how this would be faster than just doing the point and click thing. Is there a master CVS directive I could use?
And a related question: if I get all of the modules downloaded and installed in the modules directory, are there reasons why this would be a foolish thing to do from a performance or other perspective?
Thanks,
Craig
Not recommended
I don't think it would be a good idea to download everything you see and try to install them all. If you go to the CVS, and things are not ready for release, you may end up with more headaches.
=====
Drupal hosting - Up to $70 off, use coupon: HOTPROMO
from a performance
from a performance standpoint, Drupal loads all the .module files (and their includes) on the administration>modules page. Some people have reported memory issues from just having too many modules installed in this directory (not necessarily having them all active).
This shouldn't be a big problem on *other* pages, however, since Drupal will then only load the active modules.
I would also assume that loading all the modules would create quite a bloated database.
-Corey
You probably do not want to do that
There is a good chance if you download all the modules and unpack them the administer -> modules page may not display for lack of memory.
Also, there are modules that provide the same/similiar functionality so you probably only need on of them and the odds are some modules provide functionality you do not need.
I think it would be better to decide what functionality you want and find the modules that will help you achieve that. It would also be good to have a test site, I use one for testing modules that I have not tried before. It is also useful when more than one module sounds like it might fit the bill, download the bunch, enable one, try it out, disable, enable another till you find one that works (or is the closest to what you want).
I once downloaded - by
I once downloaded - by mistake, the entire cvs folder where the modules are, it's in the contributions module.
Is that what you want? download them all?
CVSROOT :pserver:anonymous@cvs.drupal.org:/cvs/drupal
MODULE contributions
By the way, I used Tortoise.
Use 'Export'
If you are going to grab all the CVS modules, best to do an 'export' to avoid grabbing all of the CVS version state information too...
(In tortoise it's an option on the third of the 3 tabs on the checkout dialog.)
David Hamilton
http://www.jiffle.net/
Thanks, that's exactly what I needed to know
I will at least examine the "Find Out Mores" to get only those modules that are compatible with 4.6.3. Your comments indicate I should approach this thing in an intelligent fashion which, alas, is more work than taking the unintelligent route.
Thank you patchwork for providing me with the rope in case I decide to hang myself anyway.
Craig
CVS vs. 4.6 release
One point is that there are considerably more modules under the 'CVS' tab than there are under the official release tab '4.6.x'. I would initially stick to 4.6 releases as that will allow you to avoid a lot of the out-of-date modules, but you may find that some gems are still not released.
During the summer, I read up on all of the 4.6 released modules (which then stood at 149 - FYI there are over 400 in CVS now) and wrote summaries of them, trying to categorise them and sort out the more and less immediately appropriate ones (to our needs). I would offer you that work, but I'm worried that, given Drupal's amazing rate of change, that it might be significantly out of date!
I also wonder that, given you have your own criteria, if it wouldn't be better for you to form your own conclusions. However it might be worth pointing out to you boss that it might take a while :)
David Hamilton
http://www.jiffle.net/