Thread

Hello,

Performing a upgrade, I click through the prompts, and then the process just stalls.

I let it run for a while and then decide to stop it because it seems like it’s not going to happen.  I get no status reports.

If I follow the back prompt, I get this error

A Database Error Occurred

Error Number: 1060

Duplicate column name ‘field_content_type’

ALTER TABLE `exp_weblog_fields` ADD COLUMN `field_content_type` VARCHAR(20) NOT NULL default ‘any’

Filename: updates/ud_200.php

Line Number: 1700

I saw your advice here, http://ellislab.com/forums/viewthread/217943/

commenting out the method that fires the sql gets me a blank screen.

Should I give it more time to run?
DB is about 80mb

Any advice?

Thanks,

Jim

Update:
I ran the compatibility wizard just for fun and got back all yes’s

I restored the database back to the 1.7.1 state.

Started the upgrade again and it just sits there, no messages, errors nothing, just spins.

I was at least getting errors to work off before.  I tried commenting out the trouble spots as mentioned in other posts, I got so far and things again just stopped.

All I can think of is trying this on another server and see what happens.

Jim

By some quirk of fate I managed to make it all the way to the end, 2.5.2

And now I have this little gem.

An Error Was Encountered

Site Error: Unable to Load Site Preferences; Invalid Preference Data

I am closer! But yet so far….......

Jim

Hello Jim,

I am sorry to hear you are running into this problem.

Invalid Preference Data, that typically means that your database or your config.php file are not quite right.

Can you paste in a few lines from your config file, I just want to make sure it’s formatted right for 2.X.

Thank you,

This is as far as I got on the last attempt:

/*
|—————————————————————————————————————
| ExpressionEngine Config Items
|—————————————————————————————————————
|
| The following items are for use with ExpressionEngine.  The rest of
| the config items are for use with CodeIgniter, some of which are not
| observed by ExpressionEngine, e.g. ‘permitted_uri_chars’
|
*/

$config[‘app_version’] = “210”;
$config[‘install_lock’] = ‘1’;
$config[‘license_number’] = ‘7676-7068-9623-9430’;
$config[‘debug’] = ‘1’;
$config[‘cp_url’] = ‘http://123456/ap3bwsys/index.php’;
$config[‘doc_url’] = ‘http://expressionengine.com/docs/’;
$config[‘is_system_on’] = ‘y’;
$config[‘allow_extensions’] = ‘y’;
$config[‘manual_templates_move’] = ‘y’;
$config[‘ignore_templates’] = ‘y’;
$config[‘db_hostname’] = ‘12345’;
$config[‘db_username’] = ‘12345’;
$config[‘db_password’] = ‘12345’;
$config[‘db_name’] = ‘12345’;
$config[‘db_type’] = ‘mysql’;
$config[‘db_prefix’] = ‘exp’;
$config[‘db_conntype’] = ‘0’;
$config[‘enable_db_caching’] = ‘n’;
$config[‘enable_sql_caching’] = ‘n’;
$config[‘disable_tag_caching’] = ‘y’;
$config[‘system_folder’] = ‘ap3bwsys’;
$config[‘cookie_prefix’] = ‘’;
$config[‘multiple_sites_enabled’] = ‘y’;

$config[‘trackbacks_to_comments’] = ‘n’;
$config[‘archive_trackbacks’] = ‘n’;

// END EE config items

I again got the invalid prefs message.
Looking at the site data, it was not encoded, so I forced a base64_encode and got a little farther, but not much.

Thanks,

Jim

Hello Jim,

What are you seeing now that you have gotten further?

You mentioned that you got all the way to 2.5.2 but the config file thinks you are on 2.1.0.

I think you may want to follow these steps and try the upgrade again.

I am so sorry this has proven to be such a pain.

Cheers,

That was my second attempt that reached 2.1.0

I have finally made it to a working install of 2.5.2

It was a very long and painstaking process.

It stalled frequently.
I followed the errors and commented out sections of the updater files as needed to move forward.  Then restarted.  I also compared the database adjustments the updater was trying to make to the database before commenting out any sql.

Another issue I got at the end was that the site preferences data was corrupt and some of it did not get converted.

I noticed that the strip_slashes portion was causing a problem in u200 when I followed that method.

What I did was restore my sites table from backup and then manually base64 encoded each column, without strip slashes and was finally able to get to the control panel.

So at the moment, I’m up and running.

Jim

Hey Jim

I am glad that you are back up and running and I am sorry about all the hassle. The update process needs works and I know the Engineers have it on their radar.

Again, really sorry for the troubles here but really glad you are back in business.

If you need anything else, please just let me know by opening a new thread.

Cheers,