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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Custom Registration Form Field Does Not Validate for Required After UpgradeCustom Registration Form Field Does Not Validate for Required After Upgrade
Previous
 
Next
New Post
1/25/2016 3:46 PM
 

I am upgrading a DNN site from version 5.06.00 to version 7.03.02. I followed the recommended upgrade path, and worked out all of the kinks with the custom modules. The registration form has a custom boolean field is required to be set to TRUE. This used to validate correctly pre-upgrade, but now it is not post-upgrade. The user can submit the form without selecting the "TRUE" radio button.

The custom field is displaying properly. The required asterisk is also displaying. The DOM even has an error message element with the correct custom required message:

<span class='dnnFormMessage dnnFormError'>[required message]</span>

However, this field is set to "display:none" by default and never displays as inline like the other error message elements.

I am not a DNN expert and I did not create this site. I am upgrading it for a client and don't know a ton about how these custom fields all work. I see the custom field enabled in Admin > Site Settings > User Account Settings > Profile Settings. I also see a file called "Profile.ascx.Portal-0.resx" that contains the custom field's main text, help text, and required text. It lives in DesktopModules\Admin\Security\App_LocalResources. I don't know what else I would need to configure or check that would be different from version 5.6 to 7.3.

Thanks for your help!

 
New Post
1/26/2016 3:20 AM
 
the message is set to be hidden, because it should get visible by using JavaScript. Enable "show script errors" in your browser to get the error displayed and fix it. In many cases this is caused by skin code or other modules on the same page.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/26/2016 10:37 AM
 

Thanks so much for your time and help.

Sorry, I understand that the error message should be hidden by default and that JS would be showing it when it feels it is necessary.  I guess my question is - what configurations do I have to make in DNN so that it knows what that necessary condition is?  I want to tell it , "not only is this field required, but you must pick the TRUE option and not the FALSE option for this to be considered a valid form."  Is that what selecting  a TRUE/FALSE required custom field does by default?

By "enable show script errors," do you mean have the developer tools open in the browser and show the console tab?  If so, I am doing that with Chrome and not getting any errors logged to the console.  I have just verified that this is also the case for Firefox and IE.  If you meant something different, how do I go about doing what you're saying?

I can get on board with the theory that some external JS is affecting this page.  During the upgrade process, I was pleasantly surprised at how smoothly the VB and other code transferred, until I ran into all sorts of custom JS issues.  I learned all kinds of things about JavaScript I never knew, like referring to data attributes used to be case insensitive, and how to make web service calls pre-AJAX!  I ended up having to rewrite all of that, but everything except this page seems to be functioning pretty well.  

I think a good next step would be to try disabling any external JS references one by one and see if I can isolate the cause.  If you can think of anything else I need to configure DNN-wise, please let me know.

Thanks again!

 

 
New Post
1/26/2016 11:03 AM
 

Update:  disabling all third-party scripts makes no difference on that page.  I also tried adding another custom Boolean field, and it behaves the same as the previous one.  Now I am beginning to think it is behaving correctly based on how it is configured.  The form automatically populates the FALSE radio button, so maybe it never shows the required error message because a value exists?  This was not the case for the old DNN version, but it kinda makes sense.  Is there a way to tell DNN that TRUE must be picked for the form to be considered valid, or am I on the wrong track here?

Thank you.

 
New Post
1/27/2016 3:58 AM
 
I am not aware of a behavioral change of the boolean property type - required meant "yes" before and AFAIK still does. I need to check on a recent install myself.

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Custom Registration Form Field Does Not Validate for Required After UpgradeCustom Registration Form Field Does Not Validate for Required After Upgrade


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out