Been reading a number of posts in forums today that have the same sort of feel.  Yes this is a know problem but it will be better in dnn601.

Given the number of real issues in 600 and the suggestions that 601 wont be out for another couple of weeks - one has to be thinking that such comments are not really helpful.

dnn600 was released with a lot of hype and fanfare - but with some seriously bad flaws or in some cases just dumb omissions - the radeditor provider not in the upgrade.zip for one.

It would seem that dnn corp needs to make a decision regarding dnn600 - its obviously broken for a large number of people - and leaving it in the wild for another couple of weeks - to annoy and frustrate many more users with failed upgrades is maybe not a good idea.

It seems to me - that maybe it would be better pulled from distribution until a more stable 6.0.1 build it ready - or a least make some changes to the download page to make potential downloaders aware of the possible issue in advance.

Right now - its a bit like a game of Russian roulette - download the upgrade and spin the wheel to see how many work days you loose - trying to get a fully functional site after upgrade.

Just my two cents.

Westa 

Sadly the list of bugs would suggest otherwise - guess you dont have a site that relies on the terms and privacy pages using the container you selected for all your edit/admin pages - instead of selecting whatever container the current page happens to have set as its default.

Or run round in circles for hours trying to work out if its a skin or some other element thats stopping your Admin file manager working - when it turns out that the whitespace filter eating javascript seems to be the cause of the problems.  

Or been caught up in the - missing debug scripts - why were this not in the install questions.

And just the fact that you and others had too blog on the stuff-up with the radeditor in upgrades would suggest that things could have gone much better.

See most people dont spend 5 hours reading thru forums to find out what is broken before downloading what is supposed to be a working release - they expect things to be good from the get go - their mistake it suppose - silly them.

My point in the original post was - there are a heap of document issues with the current set of upgrade.zip files - that are breaking many sites.
Would it not be best to at least make it CLEAR on the download page that there are ISSUE which people should be aware of before starting the upgrade process - geee a wiki link with all the issues would be a start - and the work arounds.

Sometimes it does not hurt to be proactive with end users - they tend to get less grumpy that way - tell people clearly you may have issues and let them go from there.

There are any number of threads on the forums currently from people who cant upgrade - the process fails - maybe by at least getting them some guidance in a consolidated form - as opposed to needed to wade thru pages of threads would be a good place to start..

Westa

PS - I dont disagree at all with the test it first on a offline site process - but fwiw - many end users dont actually have that option, they host sites with online providers - and dont have any backend or offline setups to test out these things - in many cases they dont even have a webserver on their local computers.