Questions around 6.16 to 6.22 upgrade
I am about to embark on upgrading a Drupal 6.16 site to 6.22. I have only recently taken on the existing (6.16) site and I'm still finding my way around a bit. There are a couple of things that I find a bit worrying:- There's no UPGRADE.txt file in Drupal core, I've unpacked the one in the 6.22 tar archive though so I can work from that. It seems fairly straightforward if a bit complex. When logged in as administrator on the site I can't see the Home » Dashboard » Site building » Modules page, though I can get to it by entering the URL directly into my browser's address bar. Is there some sort of configuration option that would enable/disable this? If not how do I get it back? The UPGRADE.txt file step five says "Disable all custom and contributed modules.", how does one know which modules are custom and contributed? Is there any easy/automated way of remembering which modules are enabled so that one can turn on all the right ones again after the upgrade? Or does one just print out the web page and do it manually? -- Chris Green
The Upgrade.txt is mostly about going from D5 to D6, not incremental updates of core in D6. Just download the latest D6 on top of the existing code and run update. You might want to do this in maintenance mode but I have never had a problem just doing it live. On Mon, Jul 18, 2011 at 2:12 PM, Chris G <cl@isbd.net> wrote:
I am about to embark on upgrading a Drupal 6.16 site to 6.22. I have only recently taken on the existing (6.16) site and I'm still finding my way around a bit. There are a couple of things that I find a bit worrying:-
There's no UPGRADE.txt file in Drupal core, I've unpacked the one in the 6.22 tar archive though so I can work from that. It seems fairly straightforward if a bit complex.
When logged in as administrator on the site I can't see the Home » Dashboard » Site building » Modules page, though I can get to it by entering the URL directly into my browser's address bar. Is there some sort of configuration option that would enable/disable this? If not how do I get it back?
The UPGRADE.txt file step five says "Disable all custom and contributed modules.", how does one know which modules are custom and contributed? Is there any easy/automated way of remembering which modules are enabled so that one can turn on all the right ones again after the upgrade? Or does one just print out the web page and do it manually?
-- Chris Green -- [ Drupal support list | http://lists.drupal.org/ ]
The UPGRADE.txt file step five says "Disable all custom and contributed modules.", how does one know which modules are custom and contributed? Is there any easy/automated way of remembering which modules are enabled so that one can turn on all the right ones again after the upgrade? Or does one just print out the web page and do it manually?
Core are in the "core" section. All others are custom and contributed. Yes, just print out the web page and redo manually. Good luck. It's usually very easy BTW.
Hi Chris, The easiest way to upgrade is to copy all files of D6.22 over your existing site, EXCEPT for the sites directory. Delete/remove this from your upgrade and everything will be fine. Good luck Eljay On Mon, Jul 18, 2011 at 8:12 PM, Chris G <cl@isbd.net> wrote:
I am about to embark on upgrading a Drupal 6.16 site to 6.22. I have only recently taken on the existing (6.16) site and I'm still finding my way around a bit. There are a couple of things that I find a bit worrying:-
There's no UPGRADE.txt file in Drupal core, I've unpacked the one in the 6.22 tar archive though so I can work from that. It seems fairly straightforward if a bit complex.
When logged in as administrator on the site I can't see the Home » Dashboard » Site building » Modules page, though I can get to it by entering the URL directly into my browser's address bar. Is there some sort of configuration option that would enable/disable this? If not how do I get it back?
The UPGRADE.txt file step five says "Disable all custom and contributed modules.", how does one know which modules are custom and contributed? Is there any easy/automated way of remembering which modules are enabled so that one can turn on all the right ones again after the upgrade? Or does one just print out the web page and do it manually?
-- Chris Green -- [ Drupal support list | http://lists.drupal.org/ ]
-- Lubbert Jan Bos Mobile:+39 3392403630 Land: +39 0696846044
On Tue, Jul 19, 2011 at 09:21:52AM +0200, L.J.Bos wrote:
Hi Chris, The easiest way to upgrade is to copy all files of D6.22 over your existing site, EXCEPT for the sites directory. Delete/remove this from your upgrade and everything will be fine.
Yes, after backing up that's what I did and it (as far as I can tell so far) seems to have worked perfectly. As my installation is just a simple/single one with just 'all' and 'default' in the sites directory I didn't bother copying out and back. I just copied all the files of drupal-6.22 over my old installation and then ran update.php. The installlation tar file only has the following under sites:- xxxx$ ls -lR .: total 3 drwxr-xr-x 2 globalop 5009 3 May 25 21:43 all drwxr-xr-x 2 globalop 5009 3 May 25 21:43 default ./all: total 1 -rw-r--r-- 1 globalop 5009 311 May 25 21:43 README.txt ./default: total 11 -rw-r--r-- 1 globalop 5009 10310 May 25 21:43 default.settings.php So it's not going to overwrite anything relevant in the existing installation. As an aside the distributed tar archive doesn't lend itself to unpacking directly over an existing installation because it unpacks to a root directory of drupal-6.22. So one has to unpack it and then do a 'cp -R' or something similar to copy over the existing installation. Now on to all the modules that need updating! :-) Thanks for all the help everybody. -- Chris Green
----- Original Message -----
Hi Chris,
Hi Eljay,
The easiest way to upgrade is to copy all files of D6.22 over your existing site, EXCEPT for the sites directory. Delete/remove this from your upgrade and everything will be fine.
Whilst this is true and will probably work as expected 99% of the time, I have had experiences where such changes don't work as expected. And that is not good. This is what I consider to be a "sufficiently paranoid" approach. The core principle is that you can back out of whatever changes you've made. http://www.levlafayette.com/node/177 Hope this helps, -- Lev Lafayette, Systems Administrator, Victorian Partnership for Advanced Computing, lev@vpac.org "If you are sending a reply to a message or a posting be sure you summarize the original at the top of the message, or include just enough text of the original to give a context. This will make sure readers understand when they start to read your response." RFC 1855 110 Victoria Street phone: 03 9925 4909 Carlton South, Victoria 3053, Australia mobile: 0432 255 208
participants (5)
-
Chris G -
Fred Jones -
L.J.Bos -
Lev Lafayette -
Walt Daniels