Hi

OK, but I'll have to wait until I get a chance to try the upgrade again, I had to revert back to 5.6.3. Obviously though, DNN 5.6.3 has no trouble with any Javascript for the postback, so it cannot really be a browser issue surely. The incorrect rendering of the button in Firefox does point to a minor skin/css issue with the button in Firefox, but the button would normally still be expected to work, and as I mentioned, the correctly rendered button in IE does not work either. SQL is not the issue here though, I'm on 2008.

I was wondering if there were any requirements to manually update the default skin, perhaps there is an issue with some component of the Entropy skin getting overlooked in the upgrade - how much does the default skin get changed during the upgrade, should it get completely replaced? Of course there is the possibility that this would theoretically affect any and all buttons, not just the Login button, but this is untestable as I can't get in to the site to look at other buttons.

In what ways would it be possible for Javascript requests to get intercepted and obstructed in the DNN 6.0 login control that were not previously present? Has some additional kind of Ajax handler etc been introduced?

Cheers

Greetings again!

Clearly there is something afoot with my configuration, although it should be emphasised that all the previous 5.6.x upgrades have proceeded without similar issues. After another good check through, I honestly think that with regards to the above suggestions, it is 'none of the above' sort of thing to do with the actual procedure of the upgrade etc.

The markup for the troublesome button is as follows:

Login

which seems OK to me, so my current idea is that I think I need to be looking in web.config for some sort of change to the http handlers / modules that is new to DNN 6.0. Any suggestions about which might be the culprit?

Cheers

Hi

I think I worked this one out. It is because when in DEBUG mode, some of the javascript > references, e.g., dnn.modalpopup.js, point to /js/Debug/ which is not included in /js in either the Install or Upgrade packages, for DNN 6.0 at least. A similiar problem is here:

http://www.dotnetnuke.com/Resources/Forums/forumid/107/postid/424834/scope/posts.aspx

Can anyone clarify, is it possible to run in Debug mode without modifying Javascript paths?

PS I still haven't worked out why I got the errors on the three modules at install, Html_Community etc. What are the implications of this problem?

Cheers