Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module validation issueModule validation issue
Previous
 
Next
New Post
4/2/2008 3:30 AM
 

Hi All,

I am migrating a module that was developed for a .net web site to DNN.

The control validates the field values on the before allowing a submit with control validators.

The issue is that the control validators appear to be validated prior to the page being loaded. So the first time the page loads all the validation field error messages are showing.

Im not sure what can be causing this, can anyone assist.

Many thanks,

Rod

 
New Post
4/2/2008 5:55 AM
 

maybe some other control is trigering the validation? You can make sure that only your module triggers your validation by using unique validation group names (i usually give the validation group name the name of the clientid of the module (you must do that server side though...)


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
New Post
4/9/2008 1:27 AM
 

Thanks Eric,

I found the problem.

The Image Button used to go to the page, posted back to a different page.

So I guess DNN sees that as a postback and validated the controls.

I will have to redirect instead of using a postback url.

Strangely this control has been migrated from a normal 2.0 site, where the issue did not occur.

 
New Post
4/9/2008 10:42 AM
 

Rod,

The easy fix for this would be to sepecify a validationGroup for all controls.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
4/10/2008 5:29 AM
 

Mitch Sellers wrote

Rod,

The easy fix for this would be to sepecify a validationGroup for all controls.

Thanks for repeating what i said Mitch :)

Rod: this probably happens because you migrated the control from "normal" asp.net 2.0 page to DNN (which is also perfectly normal ASP.NET 2.0!). it is caused by putting multiple controls on the same page. In ASP.NET 2.0 you can define validationgroups, which will make sure that only the controls inside the module are validated. You have to make sure that the validation group name you use is unique on the page, this is why i always use the module's client id (which is guaranteed unique on the page)


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module validation issueModule validation issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out