Thread

Hi Mark,

Is there not an option to download 1.7.1 in your download area? Is the license you’re working with under your account or another account? Let me know where you stand with that and I’ll do what I can to get you through the update process.

Cheers,

I have a single 1.x Commercial license under my accnt (Purchase date: 
2009/04/02). To renew that (to get the latest 1.x?) is $40. I would hope we don’t have to pay that just to get to 2.x.

If I choose to upgrade to 2.x then it naturally brings me to that upgrade path/fee and downloading 2.x. As we know, we have the 2.x download so that’s not the issue, yes?

Is there any way ya all can give me some sort of time line that I can in turn relay back to the client? The general frustration level (as well as loss of face for me) is reaching boiling over level. The feeling I’m getting is that another week just went by and still things aren’t any closer (i.e., I have *nothing* that constitutes a status update for the client). Nor can I bill this out until there’s closure.

It’s a simple question from this end…When? 

My spider senses tell me that 2+ weeks and counting is an awful long upgrade path. My original estimate was 2 hours. Please also consider that I still have steps to complete that are 2.x-centric. Getting a working version of 2.x is close to the end but it’s still not the end. That said, are even close to the beginning of the end? The client isn’t so sure. Nor do I blame them for doubting me. :(

Mark,

I’m going to outline, to the best of my ability, the steps you need to take to complete this process.

The first thing you will need are your backups. I’m sure you took a backup of your database and site files before you attempted any upgrade, as that is outlined as the first step in the upgrade process. Get your site rolled back to that state and ensure everything in working properly. Then, for good measure, capture a backup of your site files and database to ensure you have a known-good working setup.

If you have access to ExpressionEngine 2 through your download account, you also have the option to download EE 1.7.1. To do that, go to the”My Purchases” under the menu in the top right of ExpressionEngine.com, where you see your user name. In your purchases list, click to download EE 2 and on the next page, the license agreement, there will be a radio button option to select 2.x or 1.x. Make sure the radio is set to 1.x, click Accept License and Download.

Once you have a copy of 1.7.1 take the time to first read through the update instructions. Please read each step before attempting the upgrade. Familiarize yourself with the process before you begin. If you have any questions about that process, please post them before you begin.

After the update to 1.7.1 is complete and you have ensured that everything is in working order, capture a backup again. This will now be your known-good fallback position.

Now you can download ExpressionEngine 2. Using the same process for download as above, only this time be sure to select the radio for 2.x and click Accept License and Download. Before you begin, read through and understand the steps outlined in the 1.x to 2.x upgrade instructions. Again, read through the steps and post any questions you might have before attempting the upgrade process. It would also be wise to read through the upgrade troubleshooting wiki *before* you being to familiarize yourself with potential issues.

Once you have successfully upgraded to ExpressionEngine 2.2.2 and ensured that everything is in working order capture a backup again, so that you now have a new known-good before you begin the rest of the work you have to do.

If you explicitly follow these steps and the steps outlined in the upgrade processes, you should have very little trouble. It is imperative to read ahead and understand the steps along the way. Many users use these exact processes everyday with successful results.

Thanks Dan. I’ll give it a go. I just wish this was spelled out sooner. Something went whacky with this update. I get it. It happens.

But 2 weeks to get from that to this is disheartening. If EL wasn’t going to help, even after asking for login credentials, etc. then would could have/should have just skipped that step, eh? I feel like I’ve been waiting for this for 2+ weeks for no real reason. As I’ve already mentioned, expecting me to pursue a path that qualifies as insanity isn’t a reasonable expectation.

Perhaps I’m mistaken. That’s possible. I am certain that my client and I are all pretty frustrated. We opt’ed for new & improved and got punished - to say nothing of the unbillable hours this is sucking out of me.

Rant over. Wish me luck. Pray for me if you think it will help.

Mark,

I apologize for the round-about process that got us to this point. We try to do what we think will bring this to resolution as quickly as possible. Sometimes that is requesting Login, in this instance, that didn’t pan out. Please keep us posted on your progress and good luck.

Hello again Dan

Again, I followed the update (to 1.7.1) instructions as specified. (Please note: I deleted and then re-FTP’ed the list of system folders, as well as update.php - nothing more, nothing less). I then ran mysite.com/system/update.php and this is what I got:

Welcome!

You are currently running ExpressionEngine: Version 1.5.1

If you have followed the Update Instructions and are ready to update your system, please click the link below

Update from Version 1.5.1 to Version 1.5.2

What confuses me is that I was under the impression the update would be to 1.7.1. That is, the version I downloaded per your previous instructions.

None the less I clicked the link for Update from Version 1.5.1 to Version 1.5.2 hoping there was just some sort of bug in the updated UI. That link’s page rendered:

MySQL ERROR:

Error Number: 1060

Description: Duplicate column name ‘ignore_list’

Query: ALTER TABLE exp_members ADD `ignore_list` text not null AFTER `sig_img_height`

I have since “deactivated” the index.html and allowed index.php (i.e., EE) to serve the pages again. The site is still working so the alleged update didn’t do any damage - at least none that I can see.

However…now what??!

Dan - Either I’m a total idiot (which perhaps I suppose is possible) or there’s something VERY atypical here. I’m not pointing fingers. I’m not looking for guilt or blood. I’m just the messenger. I can only tell you what I see. I’m just trying to complete what was expected to be a pretty simple process. 

My expertise in this area is limited. I therefore must ask again, at what point is it worth your time and mine for EL to just go in and have a poke already? Geez, at this point I could have done a clean install of 2.x and just reentered all the custom fields, data, etc. But there’s no time for that now. My effective pay rate of this time suck is making Burger King look like an upward career move :(

If the path we’ve been on was producing results I’d be happy to pursue that same path. No problem, man. However, that doesn’t seem to be the case, yes? Pardon me but the only thing that seems to be progressing is the length of this thread.

The clock is ticking. The client is pissed. And I’m empty handed - both in producing a promised solution, as well as being in a position to invoice this work.

Mark,

Are you sure the database backup is from a time previous to any attempts to upgrade? That error is being generated because the updater has found columns that shouldn’t be there according to the 1.5.1 schema. As for the 1.5.1 -> 1.5.2 version information, ExpressionEngine 1.x steps through updates 1 at a time, you would see each version pass up until you are at 1.7.1

If you don’t have a backup of the database before an update was attempted, you will need to contact a professional via the Job Board that can forensically walk your database back to a 1.5.1 state.

Cheers!

Hi Dan

Before I get time sucked into another lost weekend let me just makes sure I have this right…

- Sack anything and everything I’ve invested in so far and return to square zero.

- Install the original version of EE + site (1.5.x) and get that working.

- If it works…then follow the procedure for upgrading from 1.5.x to 1.7.x.

- If that works…then follow the procedure for upgrading from 1.7.x to 2.x.

Is that correct?

Can I make a suggestion? The 2.x upgrader should issue a warning if pre-1.7.x is a known “bug” in upgrading.

I guess I was under the impression this isn’t rocket science. Evidently, I’m mistaken.

Once again, wish me luck.

Mark,

What you have outlined is a solid plan.

Good Luck!

Dear Dan

Mission accomplished.

Thank you for your persistence and level headed-ness in spite of my jackhole-ness. I bow with guilt and request your forgiveness. Note: I’m not kidding.

If there’s a reward system at EllisLab please feel free to place a star next to your own name. And if you keep a mental score card of people who owe you a beer, you can also add 3+ beers to my tab with you. A smack upside my head might also be in order.

Thanks for your help. I apologize for giving you such a hard time. Yes, I believe it’s necessary I acknowledge the errors of my ways.

Mark

p.s. What it was was the old config.php didn’t have the right version #. When I got the previously supplied error when trying to get to 1.7.1, I kept manually upgrading the version # in the config. Eventually I “caught up” to the right version and then trued up to 1.7.1. From there the road to 2.x was straight forward.

I still have work to do this weekend but at least it (hopefully) won’t entail grey hairs and foul language.

Thanks again.

Hey Mark!

Man, that is great news! I’m so glad you were able to get this going. No need to apologize, I can appreciate your frustration through this process and it was my pleasure to be a part of your success. If you ever need anything in the future, please feel free to start a new thread.

Cheers!