Thread

I’ve been wading through the other posts but I can’t seem to figure it out, as my situation is somewhat different.

I run the update.php
It looks like it succesfully updated from 1.52 to 1.60
It takes me to the second step, upgrading it from 1.60 to 1.61

And then throws following error:

Notice: Undefined index: site_name in /home/xxxx/public_html/system/updates/ud_160.php on line 51

Notice: Undefined index: site_name in /home/xxxx/public_html/system/updates/ud_160.php on line 52


Error: The following error was encountered
MySQL ERROR:

Error Number: 1050

Description: Table 'ee_sites' already exists

Query: CREATE TABLE `ee_sites` ( `site_id` int(5) unsigned NOT NULL auto_increment, `site_label` varchar(100) NOT NULL default '', `site_name` varchar(50) NOT NULL default '', `site_description` text NOT NULL, `site_system_preferences` TEXT NOT NULL , `site_mailinglist_preferences` TEXT NOT NULL , `site_member_preferences` TEXT NOT NULL , `site_template_preferences` TEXT NOT NULL , `site_weblog_preferences` TEXT NOT NULL , PRIMARY KEY (`site_id`), KEY `site_name` (`site_name`))

Unlike some other people with the same error/situations, my config.php is adjusted 1.60 and not stuck in 1.52, so:

$conf['app_version'] = "160";
$conf['license_number'] = "";
$conf['debug'] = "0";
$conf['install_lock'] = "1";
$conf['db_hostname'] = "xxx";
$conf['db_username'] = "xxx";
$conf['db_password'] = "xxx";
$conf['db_name'] = "xxx";
$conf['db_type'] = "mysql";
$conf['db_prefix'] = "ee";
$conf['db_conntype'] = "0";
$conf['system_folder'] = "system";
$conf['cp_url'] = "http://xxxx/system/index.php";
$conf['doc_url'] = "http://expressionengine.com/docs/";
$conf['is_system_on'] = "n";
$conf['allow_extensions'] = "y";
$conf['multiple_sites_enabled'] = "n";

The result is that the front-end of the site is still working. But even though it says 160 in the config.sys, in the Control panel it still says ExpressionEngine v 1.5.2 + I can’t access any of the posts.

So I’m pretty much stuck.

I have a backup of everything… but you know… I’d like to upgrade.

Oh yeah, and I was stupid enough to do it on the live site.

Arne, since you do have a backup of everything, the easiest thing would be to put your MySQL database back, and make sure you have a 1.5.2 version of config.php which is set to 666 (assuming you aren’t running Windows) and then do update.php again.

The key is the writeable version of the config.php file.

Make sense?

Hi Sue,

Here’s what I did.

I restored my old database.

Deleted all files in /system.

I uploaded the full EE 1.61 files, uploaded my old config.php files + path.php.

CHMOD777 to the config.php’s + cache dir.

Run update.php

Step 1 goes good (1.52 -> 1.60).
Step 2 (1.60->1.61) again the same error:

Error Number: 1050
Description: Table ‘ee_sites’ already exists

And the config.php is actually updated by update.php and became alot shorter, mentioning : $conf[‘app_version’] = “160”; So it’s permissions must’ve been okay.

Did you use ee_ for your prefix instead of exp_ ?

Hi Sue, yes, seems like it.

Could that be the problem?

I very vaguely remember an issue earlier about prefix problems.

Which build of EE 1.6.1 are you working with?

I downloaded it today, in build_log.txt it says: “Build: 20080118”

Supposedly that problem was fixed earlier, but I’m checking with the crew for more information..

Okay, thanks for looking into this!

Hi Arne -

I spent some time this morning looking into this—I created a 1.5.2 install locally, used “ee” as my table prefix and then went through the update process to bring it up to 1.6.1.

It went off without a hitch for me…and also for another developer working through the process (since I still have my training badge on here…;))

Looking through how the update process happens, the “sites” table is only created in the step that upgrades the site to 1.6, so we’re thinking it may be trying to re-run that update a second time, which would throw the error.

Here’s what we’d like you to do as a way to further investigate:

- Redownload the latest version of EE—just to make sure you’ve got the fresh version and a good download.

- Restore the site back to it’s 1.5.2 state.

- Run the update to the point where it says 1.6.0 has been installed successfully.

- Stop.

- Download config.php from the server, open it with a text editor

- Copy the version number it’s showing and post it here.

I think a good improvement to the EE 1.x line, or to EE 2.0, would be strict separation between user-added expansions, extensions, modules, and plugins, and the ones which come with the system. Under the current scheme it’s too easy to blow away the existing install, and too hard to chase all the add-ons.

I second that motion.  I never, ever understood why user files are mixed with core files in any application.

Because in this case, really, there is no difference between the files. A plugin is a plugin, whether it ships with EE or is added at a lter point. Consequently, it goes into the plugins folder.