Our clients are unable to upgrade to dnn 6.1.0 - as changes somewhere in the core have effect the look / layout and pretty much break what was working perfectly in 5.x and 6.0.x.

Seriously this is not a good look - we had be sweating on some serious issue patches associated with dnn 6.1.0 - ones that clients know about - and now they are seeing - the patch as being available - but we are having to advise them not to go there.

Westa 

Hey Cathal,

Have not done anything to test site but run upgrade. 

After initial upgrade - there was a page of scripting errors in the console.

After some checking - managed at least the dnn core scripts to run  - (admin menu and Manage etc)  by turning off the Hosted jQuery option in Host Settings.

Also set debug=false

Most of the skins we use - have client side scripting to handle user layout options - width , text size - it is that script that appears to be failing of the loading of the correct dynamic css - as none of the changes we make using that popout on the test site are now working.

Though im now not seeing any scripting errors being reported in the console.

As for = enabling the client resource framework ???  how do you achieve that - is it something that can be turned on / off.

Westa

The client dependency framework is not enabled by default -to do so see http://www.dotnetnuke.com/Resources/Video-Library/Viewer/VideoId/335/Enabling-Client-Resource-Management-In-DotNetNuke-61.aspx . It's not enable by default as we expected some issues (see Ian's blog at http://www.dotnetnuke.com/Resources/Blogs/EntryId/3207/DNN-6-1-JS-CSS-File-Combination-Potential-Gotchas.aspx for more details) but if you have enabled it then setting debug=true will disable it (sorry, my original comment said debug=false incorrectly). However based on your answers it's clearly the reordering issue that is at fault here - which has been logged already.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US