Thread

I’ve attempted several times to upgrade a site (which also uses MSM) from v2.0.1pb01 build 20100215 to the latest build of 2.1.1. Each time I’ve followed the instructions to the letter, but when I get to step 4, after page 2, when it has said it is updating from one version to the other I get a dead white screen. I waited several minutes just in case it was going to pull a miraculous recovery out of the hat, but no, the upgrade process had indeed died. I then tried to rerun the upgrade script, but as expected it threw errors about tables already existing. I restored the original site and tried the whole process again and got the same problem, and on a third attempt in a different browser the same thing happened again. Any ideas? I need to get the site to the latest version ASAP as the previous versions have all been so buggy and unstable and my client is far from happy at this stage.

I should also point out that the upgrade instructions state in step 2 “upload the following folders from your backed-up files” and then mentions “system/expressionengine/config/” which doesn’t make sense since that will override newer versions of files such as captcha.php and countries.php which have been updated in later versions. Surely it should just say to restore config.php and database.php?

The error I received in the browser when re-running the upgrade script was:

A Database Error Occurred

Error Number: 1050

Table 'exp_comment_subscriptions' already exists

CREATE TABLE `exp_comment_subscriptions` ( `subscription_id` int(10) UNSIGNED AUTO_INCREMENT, `entry_id` int(10) UNSIGNED, `member_id` int(10) DEFAULT '0', `email` varchar(50), `subscription_date` varchar(10), `notification_sent` char(1) DEFAULT 'n', `hash` varchar(15), PRIMARY KEY `subscription_id` (`subscription_id`), KEY `entry_id` (`entry_id`), KEY `member_id` (`member_id`) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Filename: updates/ud_211.php

Line Number: 101

In case anyone else comes up against the same problem, I switched on error reporting (set $debug = 1 in index.php), and it showed that the problem was with Solspace’s Freeform module. I had v3.0.0 installed, and the latest was v3.0.3. Between these versions EE2.1 came along and the BASEPATH constant which was used in the Freeform files needed to be updated to PATH_THIRD. I updated Freeform to v3.0.3 and then did the upgrade and all went fine. However, then I had to reinstall the MSM files also.

This brought back up site 1, but site 2 wasn’t working till I updated according to the footnotes at http://ellislab.com/expressionengine/user-guide/cp/sites/domainsetup.html.

Thankfully all working now, but I have to say I dread to think I may ever have to do another upgrade of EE versions - this has been a nightmare, and all in all has taken a complete evening (6 hours).

I also regret to say that these forums are not of the help they used to be. I got a much appreciated tip from a fellow forum user to switch on debugging - apart from that I’ve been on my own. It’s been at least 7 hours since I raised this post and I have had no response from EE staff - not what I expect from commercial product support.

Although I can’t comment on your particular situation, I feel the need to chime in and say that I also followed the instructions for updating from 2.1 to 2.1.1 and had a partially-broken control panel due to (damaged?) language files.

To fix it I had to re-upload the language files from the new version, even though the upgrade docs said to upload the language files from my backup ... that step is a bit confusing and contradictory, in my opinion.

dsloan, we apologize for the delay in answering your message.

I should also point out that the upgrade instructions state in step 2 “upload the following folders from your backed-up files” and then mentions “system/expressionengine/config/” which doesn’t make sense since that will override newer versions of files such as captcha.php and countries.php which have been updated in later versions. Surely it should just say to restore config.php and database.php? [/code]

Good catch. I’ll mention this to our documentation writers. In the mean time, I posted a bug report on your behalf.

dsloan, did you mention this fix over on the Solspace forums as well?

Hi Sue,

I have now posted an entry on the Solspace forums for others in the same predicament as I was. I have linked back to this forum post, and a relevant blog entry on your site re: third party development paths.

http://www.solspace.com/forums/viewthread/5994/

Thanks,
Diarmid

Thank *you* for posting over there, I’m sure it will help others with the same problem. Don’t hesitate to post again as needed.