Thread

This question may be related to a resolved thread.

Hi gang,
I noticed some people had a similar problem updating from earlier versions, so thought I’d report it here so you know that it doesn’t seem to be resolved.

I’m attempting to upgrade from 2.13 build 20101220 to 2.14beta. When updating, I got the error 1060 ‘Duplicate column name’ in ud_212.php…

I found the threads related to the same problem on earlier builds (one of which is quoted below).

So, I commented out the offending line (as the other posts indicated), ran the update again, and got the same error but on a different line, so I commented out the other. Then the next error was the same, but for ud_009.php. I gave up at that point.

I rolled back, so in a way this isn’t an open issue, but since this seems to be a recurring problem I’m fearful of updating again, yet of course, I’d love to take advantage of all those bug fixes. So I would like to get a response as to what the problem could be or if it’s been fixed so I can at least update when 2.14 is released.

This is a quote from the earlier post linked to above, which is what I did with no luck to solve the problem:

I “fixed” it by altering the update code (ud_212.php)

The commented lines should fix the problem. For me it was not only the show_sidebar but also the two other lines. Good luck!

function do_update()
    {
//        $Q[] = "ALTER TABLE exp_members ADD show_sidebar char(1) NOT NULL default 'y' AFTER quick_tabs";        
//        $Q[] = "ALTER TABLE exp_member_fields ADD m_field_cp_reg char(1) NOT NULL default 'n' AFTER m_field_reg";
        $Q[] = "ALTER TABLE exp_accessories CHANGE member_groups member_groups varchar(255) NOT NULL";
//        $Q[] = "ALTER TABLE exp_member_groups ADD can_edit_html_buttons char(1) NOT NULL DEFAULT 'n' AFTER can_view_profiles";
        $Q[] = "UPDATE exp_member_groups SET can_edit_html_buttons = 'y' WHERE can_access_cp = 'y'";

Hi budparr,

This error is typically just a symptom with various possible underlying causes. Something’s up here though, since if you were already at 2.1.3, EE would not be using ud_212.php. Some questions:

1. What was the value of app_version in your pre-upgrade config.php file?
2. What browser are you using to perform the upgrade? If Firefox, restore your database to the pre-upgrade state and run the installer/updater again using Chrome or Safari. You may get a different error.

Hi Brandon,

app_version in the config file: 213

I was using Safari.

So you’re saying I should just try again?

budparr,

Role it back at least so we can check a few things first with you regarding what’s in your config etc

I rolled it back before I even made the post. This is encouraging, as I had gathered from the earlier posts that it wasn’t something localized. So, I’m attaching my config file with personal info taken out (and the <? removed from the first line so it will upload here).

Yes, I’d say please try again. If you are on 2.1.3 already, and your config.php says so, EE should only run ud_214.php during the upgrade which will not change your database structure.

Just to update you guys - I did the upgrade again, this time changing my config file back to the basic config file (mine was supercharged, you could call it, trying to develop something along the lines of Erskine’s from their eeci talk). Once I changed the config file back, I had no problem.

On my end I have to figure out what the heck in my config file could be causing that because the app_version was indeed set correctly. If you happen to have any insights, I’m happy to hear them, otherwise, thanks for your help.

Bud

Hi, Bud. Troubleshooting what went wrong with your custom config.php file would be a CodeShare issue, I can move this thread over, or you can open a new one.. which would you prefer?

I’ll open a new one, thanks.

Good stuff. Closing this one out. Feel free to start a new thread if you have any more questions