Thread

I just uploaded 1.6.0 to my site.

When I point to system/update.php I simply get a blank screen back.

I have a feeling this is obvious. And maybe it’s simply late on a Sunday. But I don’t see it yet.

Any place in particular I might start debugging?

Thanks.

Walt

Make sure that you have system/updates/ directory uploaded and try re-uploading the update.php file as well.  If neither of those work we may need to try to get some error reporting going to see what is wrong.

It was an upload problem.

I re-uploaded in the AM and update.php is now running for me.

However on the step to go to 1.6 it just hung.

Now if I try to access my CP or one of my sites I get the following SQL Error -

MySQL ERROR:

Error Number: 1054

Description: Unknown column 'g.site_id' in 'where clause'

Query: SELECT m.weblog_id, m.tmpl_group_id, m.username, m.screen_name, m.member_id, m.email, m.url, m.location, m.join_date, m.last_visit, m.last_activity, m.total_entries, m.total_comments, m.total_forum_posts, m.total_forum_topics, m.last_forum_post_date, m.language, m.timezone, m.daylight_savings, m.time_format, m.profile_theme, m.forum_theme, m.private_messages, m.accept_messages, m.last_view_bulletins, m.last_bulletin_date, m.display_signatures, m.display_avatars, m.last_email_date, m.notify_by_default, m.ignore_list, g.* FROM exp_members AS m, exp_member_groups AS g WHERE g.site_id = '1' AND unique_id = '' AND password = '' AND m.group_id = g.group_id

It looks likely that all of the db alterations didn’t happen.  What version did you upgrade from?  And do you have access to something like phpmyadmin?  And… to be clear on what’s up- you click each link in the upgrade path- and when you clicked the 1.6.0 link- it hung how?  White screened or….?

Also- if you pull down a copy of system/config.php- what app_version is it showing?

It looks likely that all of the db alterations didn’t happen.  What version did you upgrade from? ?

I believe it was 1.5.2.

And do you have access to something like phpmyadmin?

Yes I do. My host provides phpadmin thru their control panel. It’s a windows site btw.

And… to be clear on what’s up- you click each link in the upgrade path- and when you clicked the 1.6.0 link- it hung how?  White screened or….?

Exactly, I clicked on the links up to 1.6.0. It didn’t white screen. It was the update screen, but blank.

Also- if you pull down a copy of system/config.php- what app_version is it showing?

$conf[‘app_version’] = “152”;

Now, if I rerun the update I am told I am starting from 1.5.2 again, which makes sense given the above. And I get the following error.

MySQL ERROR:

Error Number: 1050

Description: Table 'exp_sites' already exists

Query: CREATE TABLE `exp_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`))

This is going to further complicate things. But I will ask anyway. I am currently running 4 blogs out of this instance. So the idea of purchasing Multi-site intrigues me greatly.

One of the blogs is dead. But it happens to be the site in which I actually have EE installed. What I really would like to do is -

1. Install EE in one of the other domains. Perhaps from scratch?
2. Install Multi-site.
3. Recover the other 3 blogs from the original instance and not lose what I already have. Especially in regards to a photo gallery I have in one.

Would that be possible? Because I fear the current instance is nuked.

Thanks.

Walt

Poot- it looks like the database changes failed halfway through- it could even have been a memory or timeout issue- though I’d have expected a white screen- but I could be expecting wrong.

The glitch is- the first half of the alterations happened- thus when you try to redo, you run into the problem of tables already being added/altered.  BUT since it didn’t finish- looks like it failed at LEAST by the point it adds the site_id field to a bunch of tables- you get errors.

It’s possible to manually do the missed additions, but looking at the code it looks rather messy in this instance.  I think the best thing to do is put up your backup copy of the database and your backup copy of config.php- then try to rerun it again.  If you have solid backups, that’s going to be the easiest option.  Unless the script fails halfway through again- and we’ll be in the same position.  At which point I’ll be suspecting a memory or time out issue- which we can work around in various ways.

Now- as to switching to use the site expansion….  I think what I’d do is get the update done first- all right and tight.  I’m not sure how you have your multi-domains set up now, but I don’t think it will be difficult to switch things around so your ‘main’ site differs.  Alternative is to backup to 1.5.2, switch things around domain wise, THEN update.  I suspect it’s going to come down to a personal preference issue (I’m impatient and would want to be able to play with 1.6 asap rather than dink around with domain issues.  A more practical person might get the domains squared away now on a version they are completely comfortable with- then do the upgrade.)

Make sense?

OK.

The backup I have is the one I did through CP Utilities prior to initiating the upgrade.

Cool. Something new to try! So I assume -

1. I unzip the backup created in CP/Admin/Utilities. Which extracts the .SQL created in the back up step.
2. I go into phpadmin on my host control panel.
3. There is a SQL Query button there that allows me to import a text file. I assume import a text file refers to importing a SQL text file (i.e. not a exported data file).
4. I run that imported query to do the restore?

Thanks!

Short answer is- yes.  Long answer- I always get very paranoid about making sure the backup is good before I commit to it.  I’d make a second backup of the db in its current state- I’d do it via phpmyadmin.  Just in case. 

And if I’m feeling particularly paranoid?  I’d create a new db, import the backup file into it instead.  Then I’d edit my config to use that new db.  I’d leave the old db alone.  If I need to switch back to it- it’s a simple matter of editing the config file again.

Doesn’t hurt to be super-paranoid when you’re playing with your entire site.  Me?  I’d create the new db- import the backup- change the config.

Me?  I’d create the new db- import the backup- change the config.

Thanks.

Went the route you suggested.

1. Created a new db.
2. Imported the backup.
3. Edited my backup copy of config.php to point to the new db.
4. Uploaded the edited copy of config.php to /system

Now I assume my next step is one of the following -

1. I could reupload the original 1.5.0 (P.S. it was actually 1.5.0 I was running) software up to my server and try to see if the restore took correctly. Then try to do the upgrade.
2. I could try to run the upgrade directly.

I would actually prefer to do the latter. Move on to 1.6.0 then worry about whether I want to change the domain structure.

Regardless, before I run the upgrade is there anything I could do to try to trace/debug/etc. in an attempt to see where I am failing (assuming I fail again)?

Thanks for all the help!

Walt

I personally would do the later as well.  If it fails again?  I’ll probably ask the crew to step in.  Or- if you have control over things?  I might up the php memory allotment to say 32mb, to eliminate memory issues.  If it’s the default 8mb?  It’s possible that’s an issue.  Can’t remember how to change the timeout- but that could be an issue.  Or- it could totally be something else, like evil gremlins.

But me, I’d cross my fingers and just run the update- making sure you keep a clean copy of the current config- and that it shows you running 1.5.0- so it starts in the right place.  Hopefully it will go through this time.  If not- we’ll dig in and force the issue.

I personally would do the later as well.  If it fails again?  I’ll probably ask the crew to step in.  Or- if you have control over things?  I might up the php memory allotment to say 32mb, to eliminate memory issues.  If it’s the default 8mb?  It’s possible that’s an issue.  Can’t remember how to change the timeout- but that could be an issue.  Or- it could totally be something else, like evil gremlins.

But me, I’d cross my fingers and just run the update- making sure you keep a clean copy of the current config- and that it shows you running 1.5.0- so it starts in the right place.  Hopefully it will go through this time.  If not- we’ll dig in and force the issue.

Went the latter. The upgrade completed successfully.

My sites look fine. I optimized as the upgrade suggested.

The only strange thing I am encountering now is that the Control Panel is unstyled. Looks like raw HTML as if there is no CSS associated with it. Belay that. Reviewed the other threads and found the solution. My default theme folder was hosed.

Thoughts?

Thanks again!

Walt