Magento

I’m upgrading a site running 1.0.1987 to 1.1.2, and following the wiki’s instructions, I uploaded the new files, overwriting the old, and removed the var/cache and var/session directories.  Then, I pointed my browser at the homepage, and I got the following error:

Does anyone know if I perhaps missed a step in the upgrade process or if the wiki article on upgrading left something out?

Thanks,
Scott

-- SEE BELOW FOR SOLUTION—

The same thing happened to me after I upgraded from that version to 1.1.1

I decided it would be faster to reinstall cleanly than try to fix the error athough it took much longer than I thought.
I’m not going to upgrade until I either get connect/downloader properly and flawlessly configured or until I find
a post or someone can confidently write instructions on how to upgrade.  Being on godaddy might be one
of the problems it crashed but I still do not want to start over.

Hmm, that’s strange.  I’m on my own server, which I’ve set up specifically to run Magento (all required and recommended Apache/PHP modules), so at least in my case it isn’t a hosting issue.  If that upgrade process isn’t correct for the 1.1 trunk, I wish they’d updated the wiki with the release.  Anybody else have any ideas?

Yeah you are missing a column has_options in that table.
What I’d recommend is just edit your database table directly, and add a has_options table in there.

It’s basically a smallint(1) default 0 column at the end of your catalog_product_entity table (if my memory serves me correct).

And if you got a half-baked upgrade, I’m pretty sure you going to have to go through a whole lot of editing and commenting out those things that give you errors in the mysql-upgrade-* php files. Just do exactly what it tells you to do.

But if you ever run into, can’t create tables error, you’ll likely want to have another magento install somewhere on a separate database, and copy over that table to your existing database.

I decided to manually FTP all the files of the new version to the server, rather than unpack the tar ball, and this time it worked.  It looks like if you unpack the installation, some files don’t overwrite.  After FTPing all the files, I hit the homepage again, and this time it loaded fine. 

SimpleHelix - I bet you’re right about that, but the database modifications were supposed to be performed by the script, and if I’d done that manually without re-uploading the files, I might have just covered up the real problem without knowing it.  Many thanks though for the insight.  It got me to looking more closely at the files and led me to the solution.

-Scott

If that’s the case, now *you* are getting me to think too =)
I guess then when you upgrade with Magento Connect, it doesn’t overwrite some files then that means?