Can anyone shed some light on why DotNetNuke comes configured with request validation and event validation disabled? They're both off at the web.config level for a default install which seems to be a regressive approach. Are there any sound reasons for this and what is the functional impact on DotNetNuke if they're turned back on?
Obviously appropriate input validation should be happening in code anyway but the native .NET framework behaviour is always a nice fallback.
I'm using some of the typical ASP.NET's Validation Controls in my website. Now I'm trying to disable the JavaScript in my browser to test my application and of course the Validation Controls no longer works. I think it's best to try to make them work using one of the solutions down here instead of reinvesting the wheel and build a validation layer for the page or my objects -Am I thinking right?-
What do you think of these options and why:
Include in clicked button's event a code to check if the page is valid and if not explicitly call the Page.Validate(); method Check if whether the JavaScript is enabled and if not I should call Page.Validate();
I have a user control with a label and a field. I add the user control dynamically to a page at run time. There could be many user controls which are built dynamically from data I get from the data base. The data describes the label name and if the text box should be completed.. ie is it required. I have a submit on the main page which has a validation group.All the validators on the user controls have the same validation group. So far so good I hope.
The user control has a RequiredFieldValidator for the text box and looks all like this. The validator is enabled by default.
When I dynamically load the control I check a parameter to tell me if the field is required or not. The paramater is from the database which represents the control that I am about to draw. If the Field NOT a required field I disable the validation in the page_preRender.. also tried it in load.
So far so good. This all works on the client side validation for only the user controls with the Display Required set to true, leaving the Validator enabled.however on posting page from a submit button which I have wired to the same validation group as the user controls, I check the IsValid on the submit and if its false I dont save anything. But when the page re-renders on the client.. I have error messages on all the user controls, saying that they are required... even though I disabled some of them that where not required. the View state is default on the control which I assume to be on.
I also tried not redrawing the controls with the validators, by enclosing the code in a if(!IsPostBack)
why the validators fire when they are disabled on the first page load but dont get disabled on the postback.
I am trying to make ONE thing work. The form currently have TWO Textboxes and ONE CustomValidator(connected to the first textbox). I simply want once I enter less than 4 characters in the first Textbox and tab out to the second Textbox and if Javascript is DISABLED then the server side code should stop me. I can achieve what I am trying to do if I use a button but I need to do it in the fashion I am trying decribing because if I have for example 20 textboxes on the form I want the user to see after each data entry that his validation was successful or not. Here is a sample of my code.
Using MicrosoftMvcValidation.js, it seems like disabled html elements are validated on the client-side. I am not sure how much sense that makes given that such elements will not be submitted by the form and I probably consider it a bug. (By the way, MicrosoftMvcJQueryValidation.js does not validate disabled elements.)
Is there any way I can disable (pun intended) the validation of disabled elements? E.g., assuming I have a reference to an html element in javascript, is there some way I can "remove" it or disable it from the client-side validation machinery?
I have an aspx page that contains a checkbox, and a button. The button is disabled by default until the user checks the checkbox. It looks like when I add the attribute enabled="false" to the button, it removes the validation. When the button is enabled, I still want the validation to work. Here is the code and markup for the different parts.
Checkbox:
<asp:CheckBox runat="server" ID="termsCheckBox" /> <label style="display: inline;"> I agree to the Terms & Conditions</label> [code]....
I'm using DotNetNuke 4.8.x and want to utilize jQuery. Could anyone possibly suggest me on what is the best way to integrate jQuery into DNN? I won't be able to upgrade DNN version to 5 which has built-in support for jQuery.
We are in the process of implementing a CMS for our project which currently extensively uses asp.net master pages and css. Also the application is data-driven and controls like gridview and listview are used. After a little search we zeroed on two CMS dotnetnuke and umbraco. Now my question is:
Which one of the two CMS is best suited and easy to use?
Do they support integration of existing code and UI's
I want to create a new module in DNN (VB) ... that;
1. does not use DAL or DAL+ 2. has only one view.ascx control 3. It has to be a compiled module
I do not need DB connectivity and any bells and whistles just one view control. I thought it would be simple but googling for a day now and it seems very complicated.
I have the development environment already set up with;
1. DNN Starter kit 2. VS 2008 3. SQL server 4. DNN up and running in IIS 5. the project builds successfully
If anyone knows a way I can build a module using the DNN Dynamic Module Template in VS 2008 and then strip off the DAL and all the unnecessary layers and extra controls until I have only a working view.ascx that just prints out "Hello World!" to the screen ...
I am getting started with DotNetNuke and when I try to use jQuery the same way I use it in any standard ASP.NET page it does not work. For example I am trying to use uploadify which uses jQuery and flash. I can't even get the cancel button to show in the control.
By now I understand there must be a workaround and it is different than simple asp.net
I've Googled, Binged, and here at StackOverflow, looked through the related questions and searched, but I'm not finding what I'm looking for. I've also searched documentation on DNN.
What I'm looking for is any guidance (tutorials, blogs, step-by-step instructions for setting up a repository) etc from people who are experienced in using DotNetNuke with SVN.
We use SVN for all our source control, and have no problem with standard applications, because we pretty much built the repository and directory structure to work with our processes. This means when we do web sites, in Visual Studio, we do file based web sites, rather than setting them up in the local IIS. It just makes things easier for us.
However, with DNN, it appears that even if you get the source code, it is expecting to be set up in the local IIS, which means additional headaches for us.
For example, we are moving all of our source code off our local C drives, and onto a shared drive on a server. This is to enable backups in addition to our normal source control. (This was a management decision). So that means that we need to change the virtual web app when we make the move.
Has anyone come up with a good way to work around this? Can DNN be set up so that the developer web server in Visual Studio can be used, so that we can treat it just like any normal web app? Am I missing something obvious?
I'm creating a new DotNetNuke module and in the past I inherited from PortalModuleBase. I'm aware that there's a replacement for this now. Can someone tell me what it is? I've had a brief search for it but I haven't found what it is.
I've been tasked with looking into performance tuning my company's intranet server. It runs DotNetNuke which suffers from poor performance. It also runs a number of other web apps (mix of asp and asp.net).
Could anybody give me a brief list of common performance tweaks that can be made to IIS6?
In dotnetnuke, I have two sites located on different location. Now I want to point these two sites to the same database. Is it possible to point to same database.
I even tried pointing it from web.config, but thats not working. I don't want to work with child portals, because i have already created site on other location and all the source codes are under that, but when I create child Portal, it creates new portalnumber folder under portals, and it just has two folders in it, Users and Cache, I dont understand how to place codes, as DNN creates lots of folders while creating new site, which are missing here.
I want to create a module that can send a message to another module in different tab.I don't know the target tab Id but I know the target module name. Is there any way to do such a thing?Is Dot net nuke support messaging?
i installed dotnetnuke in my system, installation is completed successfully, now i want to change skin settings according to my requirement like changing colors,font,logs like that can u help me how can i do this in dotnetnuke.
I am very new to dotnetnuke. and want to know. steps to create and build a webapplication in dotnetnuke.how can we add module using dotnetnuke.how can we handle database in sqlsever 2005 or later on it.
As part of a redesign for one of my clients I'd like to move them to DotNetNuke to gain the CMS and blogging features. Their existing site has some custom ecommerce functionality that an off-the-shelf package just can't handle, so I'm inclined to leave it and just re-skin to match the new site.
The challenge is making this all fit together.
I could create two physical web sites in IIS, for example:
www.website.com <-- DNN install
and
shop.website.com <-- Existing ecommerce
This would keep things isolated, but I see a problem with the SSL certificate. It's tied to www.website.com, so now I'd either need two -- one for www. and one for shop. -- or I need a wildcard certificate. Either adds ongoing expenses for the client.
I could try to encapsulate the existing site into a DNN module, but that seems like a lot of work. I could also try doing something tricky with iframes, but again I think this would just further complicate things.
But it doesn't work. I can't even manually navigate to this page. Opening new window work but it opens the same page in that new window. So, how to display content from SomePage.aspx in this new window?
