I’m thinking it’s time for me to upgrade my Drupal installation for this site to the latest and greatest. My only concern is being able to actually do an ‘upgrade’. I’ve think I tried it before without any success so I’m a little hesitant, but I would like to get up to date, if for no other reason that to get some of the new themes. :)
Anyways, I likely wont do anything until this weekend but stay tuned for a new ‘look and feel’ which will be coming soon.
I attempted a drupal upgrade myself and got in a lot of hot water. First of all, a lot of the formatting changed (all my posts became double spaced, for example). As well, my theme got really screwed up and a lot of my custom modules failed to re-appear. When I tried to restore my mySQL database was blasted away.
Fortunately I’d backed everything up so I was able to get it back to normal eventually. But some effort will be required to get the upgrade right.
Andy was right on the money, you need to be very careful.
I had a lot of trouble my first time and it ended up failing on creating the TABLE ‘menu’. I thought it was because I selected upgrading from the wrong date so I restored everything and tried again. This time it failed on the same TABLE so I figured something was up.
I did a little more digging and found that the Navigation module that I had installed created a few tables, one of which was ‘menu’. Bingo! I removed that table (and the other that were created when the Navigation module was added) and tried the upgrade again.
This time the upgade went all the way to the end, but I still got an error on the second last upgrade step. Specifically update_128 in the updates.inc file seemed to give me some grief. Here is the what update_128 does:
ALTER TABLE {term_node} ADD PRIMARY KEY (tid,nid)
It failed giving this error:
ERROR 1062: Duplicate entry ‘0-45′ for key 1
I’m not sure if update_129 (the last update) actually worked or not.
When I checked out the admin pages on the site after the upgrade there were all sorts of PHP errors listed in the logs. I didn’t like the looks of that so I opted to go back to 4.4.0 for now. I think what I’ll probably do is upgrade to 4.5.0 sometime soon and then try the upgrade to 4.6.0 a little later.
You might not want to go straight to 4.6 from 4.4. It might be easier to go to 4.5 first.
Also, make sure you have versions of all your contrib modules on hand. And yes, themes have changed, so you’ll need to go with a default theme.
As long as it works, the errors shouldn’t be a problem (they are logged from the install), except it looks like you have a duplicate taxonomy term.