Here is what I want:

I want the 1.5.2 installation that was working, but that gave this error after uploading files and visiting update.php.  Make sense?

not quite yet, to my feeble brain at this hour.

The original site worked. I can give you that, and the upload is nearly done that puts it in place.

The failure occurred this way.  I removed and replaced the directories and file that the 1.6 upgrade instructions say.  Then I tried to run update.php.  It failed with the missing table error.  I can give you that version too - in fact it’s already in place.

With these two, I think you can see everything - except for running them.  That would be a little more complicated to arrange.  Not impossible, but I need some thinking for it, and sleep is well needed.

Big prob at moment is believe it or not getting ftp working again.  I use a secure shell instead…

Does this help/offer to you?

Best,
Clive

The failure occurred this way.  I removed and replaced the directories and file that the 1.6 upgrade instructions say.  Then I tried to run update.php.  It failed with the missing table error.  I can give you that version too - in fact it’s already in place.

That’s the one.  As long as it doesn’t have the database manipulations you tried to fix it with =)

no problem on that database messing.  I simply looked at the upgrade script, and copy-pasted its SQl into phpmyadmin to create the missing table.  Similarly to make the first row. 

It’s gone now, as I dropped the table.  The original site doesn’t care one way or another of course.  But I think you can’t see any of this in the files anyway…;)

Just abou tthere - I hope.

Ok.  I have it.  Somebody really screwed up the ftp config on this server, but solved.

I will PM you the login details, but it is ordinary ftp.

When you login, you’ll see two directories.

ee_orig—this is the original EECore1.5.2 that works.  You will find a few zipfiles, etc.. - I left the mess just as it was.

ee_upd—this is the EECore after I cleaned and replaced as the instructions say, with the pieces from EECore1.6.

That’s it, and now I PM you….

C.

I looked again, and in ee_upd you will find an extra directory, ee16, which was the fresh unzip of EECore1.6 that I stole the upgrade parts from, per the instructions.

Let me know you can get in the ftp, and I will go to sleep…

C.

I just PM’d asking this.  I got it thanks =)

Just as a note I do need the URL to access these, the domain you sent/ee_orig just 404s.  Thanks =)

and I think I just pm’d the rest you need.

I’ve also put the index.php back in - so the website itself which you now have tries to run.  It gives the same error as the update.php script - for the missing should-have-been-created new sites table.

Listen, as the birds are singing outside already, I could give you direct access to the real working site, as discovered through the funny ftp.

I will do that and pm you the ftp for that.  This will let you work against the real database, when you want to. 

Please rest also - again this is not a crisis situation, just that we both got wrapped up in it.

Best,
Clive

I want to get this fixed, and figure out what’s going on. Lets keep it in PMs for now, I’ve just messaged you with some confusion. =)

Narration - a quick note, another customer with this problem resolved it by deleting system/updates and system/update.php and re-uploading them - so that is definitely worth a shot. =)

*bounces* I got it, I got it!!!!!!!!!!!!!!!!!!!!!!!

Ok - here is the problem.  You had a .htaccess file in your system directory, it contained a mod_rewrite that was causing everything to look at your main index.php - so you were essentially visiting your site without running update.php and you couldn’t get to update.php with that mod_rewrite.

I backed up your .htaccess file to my hard-drive and nuked it out of your system directory.

You can now visit update.php and the page will load - I have not clicked the link to run the actual update, because I didn’t want to steal that joyful moment from you. *winks*

Go do it and tell me how it turns out.  Go go go go!

Oh, and by the way - how did I figure out it was the .htaccess? I uploaded license.txt to your system directory and tried to visit it and got that MySQL error - so I *knew* that your site was processing files it shouldn’t have been. =)

Ok, I C

Let me try that update.php—pants—

Lisa, you have been a jewel about this.

Back in a flash,
Clive

Ok, I have to say here that Lisa has been the shining jewel here.  And I just got bunted from the Private Message system, having ‘sent more than I’m allowed in 24 hours’— hmm.

So I will just have to put the appreciation here.

She found the problem - a slightly ‘leftover’ .htaccess file I had put in the system folder.

...never in a million years…it was very hidden.

Once ‘nuked’, as she put it, I could update successfully, with no database errors.

This went very smoothly, but then the site had only white screen to show.  This is because I didn’t realize to remove the Pages things from our friend before upgrading.

Since upgrade is really simple, especially direct on a Unix system, I’m just going to put back the original site one more time from backups, _remove_ Pages from our nice friend, and then upgrade again.  That part will take about 5 minutes.

That’s what I’m doing, then.

Birds sing in the trees in the courtyard, or tweet anyway, as the light is here.

Thank you, Lisa.  Really appreciated, and the experience of your professionalism there.

Take care, and make up your own rest debt, please

with nice thoughts, from Basel on the Rhine,
Clive