Thread

This question may be related to a resolved thread.

I’m trying to update to 1.6.9 from 1.6.8.

I went through the update to a new version procedure and now when running update.php, I’m getting the following error:

Error: The following error was encountered
MySQL ERROR:

Error Number: 1060

Description: Duplicate column name 'username'

Query: ALTER TABLE `exp_password_lockout` ADD `username` VARCHAR(50) NOT NULL AFTER `user_agent`

I had to revert to my backup system.

ExpressionEngine 1.6.8
Build 20100121

What seems to be wrong here?

Kim,

Is your system/config.php writeable with permissions of 666

If you goto your Database Query Form and type in the following

describe exp_password_lockout

Can you see a username row?

CP Home ›  Admin ›  Utilities ›  SQL Manager ›  Database Query Form

Here is what I’ve got from the query:

Field     Type     Null     Key     Default     Extra
login_date     int(10) unsigned     NO     MUL         
ip_address     varchar(16)     NO     MUL     0     
user_agent     varchar(50)     NO     MUL         
username     varchar(50)     NO

For EngineHosting account, does permissions matter? I’ve checked and it’s set as 644.

Kim Ryu Hyun,

I had to revert to my backup system.

When you say revert did you rollback the database aswell. What steps did you take to revert?

That error would only have appeared if a 1.6.9 update was previously attempted at any stage. It looks like your database has already been updated to 1.6.9.

It might now just be a case that you have been upgraded. What version number is in your config file?

For EngineHosting account, does permissions matter? I’ve checked and it’s set as 644.

On EH no you are correct no permissions need to be set

I’m using MySQLDumper to backup and restore my database. Therefore the steps that I’ve taken to revert were:

1. Copy back previous version of system files from EH's .snapshot directory.
2. Restore my previous database using MySQLDumper.

My current config file shows the following:

$conf['app_version'] = "168";

But if you still have

username     varchar(50)     NO

then the initial db changes for 1.6.9 have been done.

If that’s the case should I try to update to 1.6.9 without running the update script?

Yes, assuming you have all of the 1.6.9 files in place, I think you can delete the system/updates/ directory and system/update.php.

Then in config.php make it:

$conf['app_version'] = "169";

You should be up and running on 1.6.9 at that point.

That didn’t do it. So I had to revert back to 1.6.8 once again.

After downgrading, I’m having issues with membership functionalities. I’m not sure it is related but I’m getting a blank error page after registering a test user.

If my database is currently in 1.6.9 state as stated above, how can I revert it back to 1.6.8 compatible state?

Kim Ryu Hyun,

The only sure way to revert is to restore a database backup from your 1.6.8 installation.