Hi Everyone,

I have just started a project where the client is keen to use the latest version of Dot Net Nuke (v5.2.1) but is legally obliged to have all functionality accessible with javascript enabled or disabled. This project will include custom module development that requires the user to submit form data.

My preliminary research seems to indicate that postbacks are impossible with javascript disabled. If use a vanilla install of Dot Net Nuke and create a module that purely contains an <input type="submit" /> tag. Clicking the resulting button will postback as expected with javascript enabled, but will generate a critical exception with javascript disabled.

What I am searching for is either:

1) A solution (if one exists) that would allow me to make these postbacks successfully with javascript disabled.

2) Some official documentation (including content on this website) that states the hard requirement to have javascript enabled that I can provide to my client to help convince them of the infeasibility of Dot Net Nuke for their requirements. Failing that, even a response from someone working at Dot Net Nuke would suffice.

I have studied the stack trace generated by the critical exception and removed code in the DNN site where I thought it might solve the problem, but this just causes critical exceptions with different stack traces.

During my search for option 2, I came across the forum entry www.dotnetnuke.com/Community/Forums/t... where on the 2nd page darragh says:

However I cannot find where this trouble ticket is located. If I could find this response from Cathal Connolly in its original form, I believe this would be enough evidence.

Can anyone help me with either of these possible solutions?

the trouble ticket is in an issue tracker that only PE customers have access to. However the statement is correct, we have neither tested or support DotNetNuke with javascript disabled. In addition, as virtually all modules utilise postbacks or/and MS Ajax (or other libraries such as telerik which make extensive javascript usage), even if we made changes to the core, modules would fail. At this point in time we've seen little demand for a non-js supported version of DotNetNuke - if over time this changes we may come back and reevaluate this.

Thanks,

Cathal