By domineaux on
Coming from Xoops it was a non-brainer. All modules go in modules folder.
So I've been poking them into the Core/modules folder.
Been reading where others place 3rd party modules in Core/sites/all/modules
No problems with this, but I'm beginning to wonder if I should change it before the site gets to big.
Why the extra folders for 3rd party stuff?
It is easy to recall all the modules intalled, and if I don't remember them all I have to do is go into the modules enabler/disabler.
Comments
=-=
seperating the core module from the contrib modules makes for easier upgrade/update.
a user updating/upgrading can then safely DELETE the modules folder without fear of removing contrib modules.
This also allows for multisites to use modules that are in the all folder and not have to upload them to EVERY site.
modules in /all/ will be used on ALL sites
sites/default/modules allow modules to run only on the default (1st install)
sites/somesite.com/modules would be modules that only run on somesite.com and not on all other sites associated with a multisite install.
The above explainations should make clearer the decicison to keep core modules and contrib modules seperated.
In drupal 4.7.x all modules went in the core modules folder, this proved painful when upgrade instructions stated to DELETE the modules folder and all contrib modules were also deleted.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Got it - good explanation
Thanks
if it's such a good idea
Hi all,
If it is such a good idea to keep the third party modules seperate from the core modules, why doesn't it state in the module readme's to put the mods in the sites/all modules folder????
Surely this should be a standard instruction for the likes of myself and domineaux and anyone else that just happens to be starting out with Drupal.
..
You would need to ask that modules maintainer that question.
This is mentioned in the Getting Started book here
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
This also allows for
So basically what this says is that I can have drupal installed on one site and use that same installation for all sites? Not sure how that works and am interested in learning more. I currently have it installed on 4 different sites and that does take up extra storage space. I am not currently anywhere close to my limit, however who knows in the future.
Contact me if you can give me more help
Thanks
Sue
www.sueswebdesigns.suesman.net
me too
That does sound pretty interesting. How would it work?
Well, Drupal 5.5 is 2.9
Well, Drupal 5.5 is 2.9 megabytes. If that's taxing your disk space, you should really find another host - anything less than a gigabyte (350 Drupal installs) of space is horribly undersized from a host.
There are much better reasons than storage space - probably the biggest of which is upgrading. Running Drupal off one codebase means you only need to update modules and Drupal once, instead of for each site. Big time saver.
This Google query should get you started with Drupal multisite capability.
=-=
There is a plethora of documentation on using Drupal to run multisites. use multisite as a search term in drupal search and google search. Also read the install.txt file
If you ask a specific question, I'll be glad to answer but I don't want to reguritate information that can be found right here on drupal.org.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )