I think half my troubles are because I have been using firefox in the install.

If you try to get to http://localhost/localstart.asp with firefox it will give you errors.

If you do it in IE it works .....

Grrrrrr ..put it in the manual please ! .. might have saved a couple of smashed windows around here ! ... (just kidding .. but I felt like it)

Well it was a problem for me I can guarrantee you that ... side by side on the same page using the same url with nothing changing .. firefox gave errors .. whereas IE did not.

I grant you it may not be a DNN thing .. it may just be a IIS/firefox thing, as that localstart.asp is the default web sites page for IIS 5 ....

Generally speaking though .. IE seems to work better with DNN sites though. For example I downloaded the H2O module from onyaktech.com using firefox and it did not name the file correctly ... it downloaded as H2O .. with nothing else .. not even the zip extention. When I used IE it named the file correctly ie: H2O v2[1].3  PA (DNN 3.1).zip. The pdf manual also had the same problem.

All said and done .. I now have a working install but the only way I could get past the errors was by dropping firefox .... problem solved ... pitty .. because I love firefox!

 

 

Hello,

I would just confirm that the browser's behaviour may be different according to the code behind.

I also confirm what Fireant notices about the window popup interactivity -this popup may be opened by clicking on the Directory icon relative to the Authors field on the Search page accessed by clicking on the adhoc button at the top of any forum post on this site (forums.dotnetnuke.com) for example. A further analysis mentions an Event objet undefined at the level of the JScript file called for this forum.

As it may be known, the model event is differently defined from MS IE to Mozilla Firefox: the 1st uses a self-made model ("IE DOM") whereas the 2nd follows the W3C DOM specification. Many other similar differences could be easily found by a quick comparison between the 2 models.

According to my experience in .NET (programming), many JScript developers believe that they program "universal" Javascript -and I will not reproach that to them as I know that they do so because they have been said that it is the right way to do. In fact there are Javascript (as originally named by Netscape's funders) and JScript which is similar to Javascript but is MS-browser specific. I firstly discovered this difference when displaying ASP(.NET or not) websites excessively using JScript (and more accurately objects not "compliant" to Javascript). The typical example is the document.all("anyElementId") (MS IE-specific) face to document.getElementById("anyElementId") (W3C reference, also admitted by JScript -i.e. MS IE-specific script).

As a conclusion, I would modestly encourage JScript developers to use W3C compliant DOM as much as they may be aware of -that is what I am trying to do each time I have to write Javascript code or to "correct" JScript code written by previous authors when maintaining customer's companies' webapps.

I hope this may bring you a piece of clarification. Thanks for your attention.

Regards,
NHa from Lyon /France.