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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Framework and .NET Validator Control problemDNN Framework and .NET Validator Control problem
Previous
 
Next
New Post
1/24/2006 12:06 PM
 
I have posted this in the Extend IT! Forum, but thought I would try here as well, in case someone with similar experience visits this forum and not the other. My apologies in advance for double posting. Here goes: 

I am having a problem with a RegularExpressionValidator not working properly in a module on our DNN portal. I want to make sure there is not a known issue with .net validators and DNN framework so I'll know how to proceed with this issue.

We have an outside vendor that has developed a portal application for us, but we also do some module development. The vendor has used DNN version 1.x. They have informed me that there were no changes made to the Framework aside from changing the name of the namespace, but they did make some minor changes to some of the core DNN modules.

Here is a description of the problem. I originally developed this module as an .aspx page. The regularExpressionValidator worked normally as it should on the original .aspx page. Then I was asked to place it on the portal. I first converted to code to a control, tested it locally on my development machine, and the validator still worked as it should - if you put an incorrectly formatted number in a certain textbox, as soon as you leave the textbox, the validator's error message appears and you can't submit the form. Then, I added the required changes to the control to place it on the portal and once on the portal, the validator no longer works correctly. On the portal if you type an incorrectly formatted number into the textbox you don't get the error message until you actually submit the page. Also, it doesn't prevent the code in the submit button control from executing, it simply displays the validator's error message, but the code continues to execute as if there is no error. Does anyone know if there are any known issues with the earlier version of DNN framework and .NET validator controls? It will make a difference as to how I proceed. If I need to plan on validating by another method, that's fine, I can think of a couple of different things to do, but I still would like to know if DNN framework has known issues with .NET validator controls because we are planning on adding quite a few modules to our portal. We don't have control over when we can upgrade the DNN framework because it is part of our vendor-supplied software.

Sincerest thanks in advance to anyone who can offer insight!

Patricia Norris - .NET Programmer/Analyst - St Lucie County School Board

 
New Post
1/25/2006 6:00 PM
 

I am not aware of any issues with validators, we use them throughout the portal without issue e.g. take a look at \controls\Address.ascx and \controls\Address.ascx.vb

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/26/2006 11:26 AM
 

Thank you so much for your response! I will take a look at these. I have recently set up a DNN development environment that I can work on myself, but our vendor-supplied version is 1.1.? and I don't have the download to set up that version for testing. I have recently received their source code and am working on setting it up for development and testing in-house. They are going to upgrade their product to use DNN 3 or 4 and maybe the validator issue I'm having will clear up at that time. In the meantime, I will go ahead and change my code to validate by some other means.

Thanks again for your response - it's really nice to know there are people available to help out. I'm really looking forward to learning more about, and developing with DNN and am appreciative of all of you who are willing to share your experience and expertise. Cheers to you,

Patricia Norris, .NET Programmer/Analyst - St Lucie County School Board

 
New Post
1/26/2006 11:56 AM
 

I've just checked the 1.10e release out of our source code repository to check, and it also used validators, so it's likely to be an issue your vendor introduced, possibly a javascript error in the page. We don't distribute versions of DNN that old, as there were some security issues that were addressed in later versions, but if you're stuck I could probably give you a copy of 1.10e to compare and determine what changes were made (purely for research purposes - and not for deployment)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/17/2006 5:20 PM
 
cathal wrote

I am not aware of any issues with validators, we use them throughout the portal without issue e.g. take a look at \controls\Address.ascx and \controls\Address.ascx.vb

Cathal

Hi, I'm using a couple of RequiredFieldValidators and CustomValidators in my modules and they work fine in my development machine and in the tesing machine. The strangest thing happens when I upload the module to the production server: Every client-side validation stops working. I assume there's a misconfiguration on the server but I can't figure out what is it. ¿Has anyone had the same problem? ¿Does it have to do with the AutoEventWireUp directive? Please enlighten me!

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Framework and .NET Validator Control problemDNN Framework and .NET Validator Control problem


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