I uploaded all required files, checked permissions and began the update as instructed. The wizard returned this message:

MySQL ERROR:

Error Number: 1060

Description: Duplicate column name ‘comment_expiration’

Query: ALTER TABLE exp_weblogs ADD COLUMN comment_expiration int(4) unsigned NOT NULL default ‘0’

What gives?

Simon

BTW this is a different upgrade (and different problem) to the one I posted previously. However the hosting company and hence the servers are the same.

Simon

It sounds like the update script has already been run on that database.  “comment_expiration” is the first column/field that the update script tries to add, so it’s choking because the column already exists.

Are you positive you’re trying to run the update on the correct database/installation?  Are you sure you haven’t already run the update?

No - it was indeed version 1.0 - I’ve just run the entire update process again - and this time it worked flawlessly. Now it’s version 1.1

Simon

I’m encountering a very similar problem. I just tried to update from version 1.0 to 1.1. I carefully did everything as listed. Made sure to upload the appropriate files in ascii or binary, etc. Then I go to run the upload script and it tells me that I’m running Public Beta 2 and would I like to upgrade to version 1.0. Huh? I was definitely running version 1.0.

So I hit the update button, and I get this error message:

MySQL ERROR:

Error Number: 1060

Description: Duplicate column name ‘exclude_from_moderation’

Query: ALTER TABLE exp_member_groups ADD COLUMN exclude_from_moderation char(1) NOT NULL default ‘n’

I can still access the control panel (which now, incidentally, says I’m using version 1.1), but the entire weblog is just a blank white page when I try to pull it up. Help!!!

Would there be any way to simply get the weblog to appear again? The sql database is intact. The control panel works fine. But the weblog has become the blank white page of nothingness. I remember that this happened to me a couple of times when I was using pMachine, and I had to reset the sql database somehow. Would something similar be required here?

Discovered why the weblog is blank. All the templates have been erased. The code is still in the sql database, but it’s not appearing in the control panel. Must be something to do with the incomplete update process. Maybe I’ll try uploading the version 1.1 files again and trying the update again, though I don’t see why it would work this time.

Hello. Anyone there? Maybe I should post this in the technical support forum instead. Anyway, I’ve hit a wall, so to speak. I’ve checked and double-checked that I uploaded all the version 1.1 files correctly, and that they’re all set to correct permissions. But still the update script insists on saying that I was running the public beta and then tries to update me to version 1.0, only to yield a MYSQL error.

I guess I could manually copy all the templates from the mysql database back into the control panel. But I’m worried that even if that worked, it would leave some underlying update issue unresolved.

Tried pasting the correct code back into the templates. When I hit update it just reverted to blank again.

So evidently the update process has messed up something. I can’t figure out what. In the meantime, my site is down, so I’m panicking a little bit because I can’t think of anything else to do to fix it.

Could there have been a problem with the update script itself?

Well, I figured out what was wrong. Thank god. In the config.php file (which, of course, I had been very careful not to overwrite) it was incorrectly listing my application version as being public beta 2:
$conf[‘app_version’] = “009”;

This was confusing the upgrade program, since the version on my server was 1.0.

So I manually changed the config.php file so that it listed the correct version (100). And then, hey presto, the upgrade script ran without any problems, and all my templates and category groups magically reappeared.

The config.php file now lists the correct version (110).

I have no idea why it wasn’t listing the correct version before.

Glad you got it all figured out, Alex.  I hope your one-sided conversation wasn’t too frustrating for you.