1.6 to 1.6.1 - be careful

[michaelwalker]

I just 'upgraded' my 1.6. to 1.6.1., following the instructions in the file doc/UPGRADE.txt to the letter - and the process has totally nuked my existing site.  I have no modules (other than core) no users, no header, no footer - nothing but a straight out-of-the-box new installation.  Terrific.

[cb2004]

Did you take a backup? If you followed the documentation to the letter you would of taken a backup so your fine.

[michaelwalker]

Did you take a backup? If you followed the documentation to the letter you would of taken a backup so your fine.

Yes, I did, thanks, but I don't think that's the point: First, this shouldn't happen and, second, even if I restore the backup, I'm not going to be upgraded to 1.6.1

[Jos]

Pitty it didn't work that well for you. Yesterday I updated 5 sites on various platforms, without any problem whatsoever...

Nevertheless, every update has to be done with care, so your warning is good, but already done by the documentation

[Nullig]

I've updated 46 sites so far and they're all fine.

Nullig

[jmcgin51]

I've done one, and had no issues.

@michaelwalker - did you do a full install/upgrade to 1.6.1 or just the diff?

[Dr.CSS]

Sorry but the only way that can happen is if you did /install/ and not install/upgrade.php, did you by chance have to put the DB information in on step 5?...

[replytomk3]

That is why those things are done first on XAMPP, not a live server.

[michaelwalker]

Sorry but the only way that can happen is if you did /install/ and not install/upgrade.php, did you by chance have to put the DB information in on step 5?...

I could have sworn I didn't, but, like you, I cannot see any other way it would/could have happened.  btw - I used the full dl, not the diff.