Thread

Forget my last comment ... I’ve gone through the content and tons of stuff is missing - including everything from the last six or seven weeks. Plus fields in entries older than that have been truncated; whole articles reduced to a sentence or two. I think we need to restore the database and go back to 1.X ... again.

Wow. Yikes. That explains the problem with related entries. Alrighty, let’s roll back to the most recent good backup you have. Get that in working order, that’s top priority.

Then ask EH to set up an exact duplicate of your EE install behind a htpasswd protected directory. Turns out the SQL errors I thought I could get around during upgrade were major obstacles, so I’ll need to do some testing on our end to see what’s going on there. I’ll end up working directly with EH to test with that directory, but the initial request to create it should come from you. Make sure they set up an entirely separate directory and database so that neither installation has any relationship with the other.

We’ll get to the bottom of this. My hunch is that there’s a bug somewhere in the upgrade script, but it’ll take some real hunting to find it. I don’t want to toy with your live site any more in an effort to smoke it out.

Thanks again for your patience, Nathan.

Kevin

Okay, cool. Funny - I was just thinking five minutes ago, boy, it would be cool if I had a separate directory for testing before I go crashing my site again.

Should I ask for the restore or will you?

Again, Kevin, you’ve been an exemplar of good tech support/customer service.

Thanks,
Nathan

Nathan—

Sorry it took a minute to get back to this thread. If you would ask EH for the restore and to set up the testing directory, that would be amazing. It’s important that request get to EH from the client directly. Once we get both those things done, I’ll begin collaborating with them on any restores that need to happen in the testing directory as we bork upgrades in our search for the bug.

Thanks so much for the kind words. I assure you, they don’t fall on deaf ears! 😊

Kevin

The requests have been made ...

Thanks for the update; keep us posted please!

Hi, Nathan.

Looks like your 1.x content is back. Did you work with anyone in particular over at EngineHosting?

Smarty Pants (v.1.0)
SmartyPants translates plain ASCII punctuation into �smart� typographic punctuation HTML entities.   
Widon’t (v.1.0)

These two plugins—are they required for 2.x?

It looks like you’re still adding content, at least you did so this morning.

Looks like your 1.x content is back. Did you work with anyone in particular over at EngineHosting?

A couple of people over there helped with that, but Kevin on your side knows all.

Smarty Pants (v.1.0)
Widon’t (v.1.0)
These two plugins—are they required for 2.x?

There are 2.0-compatible versions of both. I had them working before I realized the database was completely screwed.

It looks like you’re still adding content, at least you did so this morning.

Yep. The site is live.

When do you want to attempt the upgrade again? Since you added a new entry, it wouldn’t hurt to export again.

Hey Nathan—

Wow… so it looks like we’ve figured it out. Here’s the problem: the error we were getting that said the database table ‘exp_snippets’ already existed? It’s because it already existed.

Ta da!

I can’t be 100% sure of the reasons why, but I strongly suspect it’s because an upgrade had been tried on the database once before, failed for whatever reason, and then rolled back. Now, to get the database back to working order for EE1.x, one would just import the backup, the SQL dump. The problem is that importing the database backup doesn’t remove those new EE2-only tables.

So when the upgrade installer hits an error because it says such and such table already exists, it really means it. I upgraded the sandboxed version of your site, but before I did so, I made sure to remove all the EE2-only tables from the database. Then the upgrade went off without a hitch. For reference, the EE2-only tables that I removed are:

exp_accessories
exp_channel_data
exp_channel_entries_autosave
exp_channel_fields
exp_channel_member_groups
exp_channel_titles
exp_channels
exp_comment_subscriptions
exp_cp_search_index
exp_fieldtypes
exp_layout_publish
exp_snippets

I’m talking with the dev team about how we can improve the installer to avoid this problem, but at the very least, I’ll be adding this information to the upgrade troubleshooting article here.

Give the sandboxed version of your site a go and let me know if everything checks out (after template changes, etc).

Things are looking a lot better than last time - at appears all database entries have moved over successfully - but I’m still having a problem with related entries. Either the data doesn’t show up, or the page blows up with the same PHP error I was getting earlier in the thread. Will have more info tomorrow morning.

I think I’ve solved the related entries problem. It looks like the update didn’t change all the weblog= parameters to channel= ones. Once I fixed those the related entry problems went away.

Still testing ... I want to go through this with the proverbial fine tooth comb before saying it’s all okay.

I’ve got just about everything working. The new versions of a lot of the templates were based on old 1.X versions that the update found who knows where. Some didn’t have changes I made a year or more ago. So I had to copy the current versions in and redo all the weblog—> channel changes and anything else I’d fixed before I discovered the aged templates.

Also, as I mentioned before, some of the weblog= parameters weren’t changed to channel= ones. I have a channel/weblog/section called “weblog”; I wonder if this confused the update.

I will do some final tests tomorrow, and then we can talk about getting my production site on 2.X.

Thanks,
Nathan

At last, at last, fourstory.org is updated to 2.X. I couldn’t have done it without the incredible tech support (and customer service) provided by Kevin Smith. He has been an absolute gem during this frustrating back-and-forth. I couldn’t have done it without him.

You may now close this thread ...

This is great! Glad to see it finally come together, Nathan. Thanks for your patience through all this. And just for the record, this experience has helped inform us about how we can make the upgrade process better.

Closing this one out. As always, feel free to return anytime you need support!