By mentat-1 on

Hi,

For this upgrade I installed a new 4.5.1 site and from my old 4.3 site I dumped the users, comments, and node tables then imported them into the 4.5.1 DB (a fun process). Almost everything works fine (I can see all the nodes---and comments from the admin->comments area), but I can't insert. It looks like there is a new table in 4.5 that keeps a count of nodes and comments---so it looks like I'm going to have to run a manual update on that. If anyone has any ideas on what to do (ie, what the node_comment_statistics table needs to look like and if I need to fix up any other tables), that would rock!

Thanks,

jesse

Comments

Jhef.Vicedo’s picture

Jhef.Vicedo commented

It would be better to upload from 4.3 to 4.4 then 4.5

there are lot of changes since 4.3

Work smarter, not harder!

jhefmv [at] gmail [dot] com
Work smarter, not harder!

JoeBala’s picture

JoeBala commented

Will any version of 4.4 do the job?

All I need is to backup conf.php and DB, extract the 4.4 version, link it to the DB and run update.php?
After that, repeat process for 4.5?
Correct?

--joe--

sepeck’s picture

sepeck commented

*cough* TEST SITE *cough*

I would copy the entire www directory and set up a local test site (change base url to your local name). Note any custom/contrib modules. Import your production sites db to your local system.

Turn off any contrib modules and update to the highest level 4.4x series. Check if there are any upgrade paths to any contrib modules you are using. Get it working

Repeat with upgrade from 4.4x to 4.5x(2) and modules. Test again.

You wrote all the steps down right? Well at least you have seperate copies of your backups in anycase....right?

Now, assuming everything went well, you can either go through the whole process again with your production site, OR you can 'restore' to working upgraded test site to your production server.

Now, since you have just performed a backup recovery process (that you wrote down right?), if you FUBAR your production site, you have a known good backup and restore process available to get you up and running when you try and figure out what went wrong.

Doing it this way will reduce the chance of a panic'd posting in the forums about how your production site is down as something went wrong and you neglected to have backups first or forgot to write soemthing down or forgot to read the part where it says to manually create tables during the upgrade....etc...etc...etc.... :)

-sp
---------
Test site...always start with a test site.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Taran’s picture

Taran commented

I am updating from 4.3.1 to 4.5.0 on easylum.net, and followed all the instructions. I click the link to update the script at http://www.easylum.net/update.php, and I get a blank page. I double checked conf.php. Everything looks right.

This doesn't make sense to me.

sepeck’s picture

sepeck commented

I am assuming that you are disabling the contrib modules before you do, on a test site :)

In any case, there is some tables you have to manually create for 4.4 to 4.5 upgrade. Did you create those tables?

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Aran Deltac’s picture

Aran Deltac commented

Looks like 4.6.0 will be out soon, so you might want to consider waiting for it as long as you are on the upgrade path. Although, as jhefmv24 said, it may help to upgrade version to version until you get to your target version.

--
http://www.electroniclife.org/