Thread

Hi,

I’m having problems upgrading from 1.5.1 to 1.6.0

I was running core 1.5.1 without problems, but every time I try to upgrade to 1.5.2 I end up with nothing (blankness on system and site)

I thought maybe downloading 1.6.0 might help, but after following the upgrade instructions (without any errors) all I get is:

MySQL ERROR:

Error Number: 1054

Description: Unknown column 'site_id' in 'where clause'

Query: SELECT template_data FROM exp_m_specialty_templates WHERE site_id = '1' AND template_name = 'message_template'

I can roll back to 1.5.1 - I’ve got quite good at this 😊 but I can’t get 1.6.0 installed :(

I even bought the license (I was waiting til closer to site live time, but purchased in order to try and get this working)

Anyone got any thoughts/insight on what to try next?

I’m using Mark Huot’s tome module (upgraded from pages) if that might make any difference (though again I followed the upgrade instructions without error…)

That error message indicates that you have not visited update.php and clicked the Update link on that page.  What happens when you visit /system/update.php?

It takes me through updating from 1.5.1 to 1.5.2 to 1.6.0 then gives me the option to optimise. It updates my config.php version to 160 too. Then I get the error

anyone?

If not, is there a guide to migrating content/templates from one install to another?

I’m pulling my hair out about this

I can’t figure how that would get skipped- though I think it was possible on the very first release of 1.6.  Do you have the very latest version of 1.6?  It’s build 20070627.  I’d try rolling it back one more time, being SURE you’re using the very latest build (not just version) and see if it works this time.

If you already tried it with the very latest build?  I’ll walk you through the db so we can see where/what got skipped.  But since it completed and allowed you to optimize, nothing should have been skipped using the very latest.  So- I’m hoping you ran this with the first build!

Can you post your config.php file here please?  Remove sensitive information like your database password and system folder and such.  And then with a tool such as phpMyAdmin, can you look to see if you have a table named exp_category_field_data?  Or I suppose on your installation using a custom prefix it would be exp_m_category_field_data.

Aha, I’ve sorted it. On a hunch (following on from your post Derek) I changed all the tables to exp rather than exp_m and it all worked.

Guess the updater doesn’t like my custom table prefix.

Did you want me to post a bug report?

Yes please, stickmus; thank you!