Here is a copy of the upgrading process from drupal 5rc1 (It's the same text for the previous versions, as far as I can tell). I've intermixed it with my comments, though the entire 'upgrade.txt' document has been reproduced.
// $Id: UPGRADE.txt,v 1.3 2006/07/10 19:27:52 dries Exp $
UPGRADING
---------1. Backup your database and Drupal directory - especially your
sites-directory which contains your configuration file and
any added modules and themes.
This makes absolute sense and easy to follow.
As an aside, a question arises though, how is it known what the added modules and themes have been. I suppose this is more an issue after successful upgrade and probably will stand out as the themes and/or modules not there.
2. Log on as the user with user ID 1.
This is where I'm lost. Is this indicating to log into the old version of drupal (the one about to be upgraded) as the user that created it, user 1. Why? The following points or instructions, as far as I can glean, only involve the use of an FTP program to delete and upload files.
3. Remove all the old Drupal files then unpack the new Drupal
files into the directory that you run Drupal from.
If my understanding is correct, effectively delete the root drupal folder that contains all the drupal sub-folders and files. At this point, I'm at a loss as to why Point 2 above is made (logging into the old drupal site as user 1).
4. Modify the new configuration file to make sure
it has the latest and correct information.
I think at this point, it should be explained what the latest and correct information is.
5. Run update.php by visiting http://www.example.com/update.php.
This is self explanatory.
I followed all above instruction for upgrading 4.6.10 to 5rc1. It failed or I failed, it didn't work. Thankfully I'm only messing with a trial setup at the moment. I ended up installing afresh 5rc1.
Is it just me or could the above upgrading instructions be expanded upon. I'm raising this now as I can see that sometime down the track I'll have to upgrade my live site.
Comments or suggestions please.
________________________________
Steven Taylor
Melbourne, Australia.
Comments
So you can run update.php
The reason you're supposed to log in before the upgrade as uid 1 (usually the admin user) is so that you can run the update.php script. Unless you play with the code, only the admin user is allowed to run update.php.
In regard to the point about updating to the latest correct information, I agree that's a little fuzzy. It's a generic upgrade procedure and just sort of cover the generic issues. Two things that help:
1. Read the release notes for all the intervening releases to see what's changed.
2. compare the newly distributed configuration file to the old one you had before - usually anything new that's required will jump out at you there.
My guess from what you say here is that what broke your upgrade is probably that you didn't
copy over the old contents of your files or sites directories, or you didn't upgrade any contributed modules to the new updated versions. Or you were set to use a theme that isn't one of the default themes in the new version - you don't say what was broken after the upgrade so it's hard to guess.
Also - it's possible that you've got a theme problem - its usually a good idea to set your default theme to Bluemarine before upgrading, otherwise there's some chance that you will end up with no theme after the upgrade.
I think that trying to upgrade through so many revisions in one swoop (and to a non-release version to boot) is probably dangerous.
Steve Hanson
Principal Consultant Cruiskeen Consulting LLC
http://www.cruiskeenconsulting.com
Steve Hanson
Publisher Eye On Dunn County
https://eyeondunn.com
This is where I'm lost. Is
because only uid 1 can run upgrade.php logging in before hand insures you a browser session. once the old files are deleted and new ones uploaded you have the ability to run http://www.yoursite.com/upgrade.php. If you didnt log in when told to in upgrade.txt then there would be no session alive to run update.php.
Agreed that the upgrade.txt will need some tweaking, though I wouldn't expect it until Drupal is released as final. I've venture a guess that these docs are being fleshed out as the dev's upgrade groups.drupal.org and other sites where upgrading is necessary.
I see
Thanks, your explanations make sense re - lgging in. I didn't think about the later step when running the 'upgrade.php' file, that the browser would remember my login details. As it turned out, after running the 'upgrade.php' file the browser returned error messages relating to 'unable to find table(s)' messages.
___________________________
Steven Taylor
Melbourne, Australia.
subfolder for added modules
I highly recommend installing all added modules (i.e., anything I put in there that didn't come in the core installation) into a new subfolder within the modules folder. I call my subfolder "contrib" and it works a charm; I can remove it during upgrade and then replace the modules with their upgraded counterparts.
I highly recommend
Yes, that makes very good sense.
___________________________
Steven Taylor
Melbourne, Australia.
I've just finished watching
I've just finished watching two videocasts relating to installing 4.7 and upgrading from 4.6 to 4.7. On top of that I've since read the handbook relating to the upgrading process. Why, oh why didn't I read the handbook in the first place. The information contained there seemed to be in enough detail for anybody to follow.
Good work Drupal. Any chance we can go back in time and stop me from starting this thread.
___________________________
Steven Taylor
Melbourne, Australia.
ha!
LOL! Just retain the humility; it stands us all in good stead when asking the inevitable questions. :)
cheers.