Posted by melban on May 15, 2009 at 2:14am
Last time I tried to update my version of drupal from 6.10 to 6.11 I wiped out all development I'd done because Mac replaced the modules folder with the new one instead of only overwriting existing files. Now 6.12 is out and I need to do this correctly. Who's got the magic tonight?
Comments
Sites/All/Modules
If you put your modules and themes in the Sites/All folder, you can copy over all the files EXCEPT the sites folder. This will keep your settings.php file, all your themes, and modules intact.
I'm guessing you're either copying over all the files, or you are keeping your modules in the root modules folder (which although it would be reasonable to assume that this is where it should go - is actually bad). If you're not currently keeping them in the sites/all folder, open that folder and create a folder called modules and another one called themes and that would be where you should upload your contributed modules and themes to avoid this problem in the future.
http://dudenhofer.com
http://twitter.com/dudenhofer
And another thing.
Aaron is correct.
Another thing commonly done is this:
sites/all/modules/contrib this is where contributed modules go.
sites/all/modules/custom this is where you custom modules go.
Drupal will search up to TWO levels below sites/all for a module folder that contains a .module file.
The same is true for Theme folders and .info files.
I was on a server once that would NOT allow an over-write via cp or mv. I 1st had to delete every core file and folder then bring in the files. In that case I added a new 1st step. I went into sites/all and ran a
tar cf bu-sites-folder.tar sites/*
then deleted all core files and folders [i don't think this applies to you]
then moved in the newest version of Drupal files & folders [either via ftp, cvs, svn, or ssh]
then ran the following 2 commands
mv bu-sites-folder.tar sites/
cd sites
tar xf bu-sites-folder.tar
Now you have restored ALL custom and contrib themes AND modules AND your settings.php
Hope this helps.
btw I'm rather fond of the Acquia Drupal distribution. a] it has so many contrib modules that I typically use, b] you can use SVN to check out the core AND update it in the future. When a new version of Drupal is released I run
svn up
and I'm done.
Check out Acquia SVN download instructions at http://acquia.com/documentation/getting-started/fresh-install/svn
- dv
Thanks for the tips and SOP
Thanks for the tips and SOP suggestions. I was afraid you'd say I should be putting contributed modules in a separate directory also. Wish I'd have known that before I started adding a million different modules to develop this thing. In any case all new sites will be constructed with an upgrade in mind.