Recently Viewed...
DNN Modules
SnowCovered Top Sellers

Live Content uses Web 2.0 approach to provide a Rich User Interface and streamlines content presentation by overlaying content on current page. Overlay images, videos, audio, text/html content, flash, dotnetnuke modules, and external content. Experience the demo...

Gloss is the first ALL COLORS! skin, featuring a powerful XML-based flash and being 100% W3C CSS XHMTL1.0 compliant. Tune it yourself on the fly, changing colors, backgrounds, containers, text color and size, width and more! Brilliant!

Ultra Video Gallery is a brother product of Ultra Media Gallery, UVG allows you to add videos in various format and automatically convert them to flv format, you also can add videos from embed code and play them in our integrated flash video player.

'Relationship Building' and 'Communication' are two essential nuts and bolts for a business to prosper. This module allows you to bridge both of these and easily generate continuous awareness of your web site, products and services. Your prospects and customers will greatly appreciate this featur

Powerful, Ajax Enabled, Easy to Use. Document Management has never been better. Open-DocumentLibrary allows DotNetNuke users to share and manage documents in a flexible, intelligent way, offering granular control over Folder and Document access.

In this day and age, knowing as much detailed information as possible about your customer, prospect or web site user is essential. Thankfully, the new 'Dynamics Forms' module from Data Springs, makes it easier than ever to segment your data collection efforts.

Ultra Media Gallery is the most popular photo gallery and media gallery solution for DotNetNuke, UMG offers 10 different flash player to browse your gallery with completely different user interface experience.

Capture your users attention, enrich your site with multimedia flash, and create and opt in distribution list for your DNN site. These are just a few of the many features the Data Springs Module Collection can provide you.

The Catalyst skins are professionally designed, coded and packaged by a team of DotNetNuke experts. The skins are available in 12 great colours. This skin is easily customisable with our unique DrNuke EasyMod technology. Try our demo!

ALL NEW ! - Minimalist includes skin packs in 12 great colors. Each color has Flat, Gradient and Glass versions. Feature rich XML Flash header, perfect for just about any purpose. 9 Different menu options in each skin pack; 3 horizontal menus, 3 vertical menus and 3 all-new Twin level menus . . .

    |   Register   |   Thursday, December 04, 2008   
Data Springs Product Forums...
Subject: 3 DF Modules on Same Page: Validation for all triggere
Prev Next
You are not authorized to post a reply.

Author Messages
John
Posts:44
paddling down the creek
paddling down the creek

08/07/2007 8:46 PM  

I created 3 different forms on the same page, which I plan to keep hidden, given that I am using the forms on another page.

As I went to do the final validation checks, I struggled to find out why the data were not saving, as no errors were displaying when I populated the text fields required. The I scrolled up and noticed that the submit button for the latter form was trigger the validations on the former forms.

I have "City" as a field in all three modules, though the short variable name for each is different (e.g., hotcity, flightcity, etc).

Is there an easy workaround for this, save changing the "city" label for each module to different names? I thought having the variable name different would suffice.

If this is not possible, I can simply create 3 hidden pages and keep each page limited to one module, but thought I would ask, as there could be an easier fix.

 

Chad
Posts:2271
river guide
river guide

08/10/2007 9:11 AM  
John,

Are you moving thiese into a tabs module, is that the reason for this? Wasn't sure on the exact implementation but it sounds like you might have to either a. move them to seperate pages or b. turn off server side validation.

Also, in the next release there will be new options to put the error summary at the bottom, change the stylesheet class for fields in error, set focus on a field thats in error, etc... These are all upcoming in the next release...

-Chad
John
Posts:44
paddling down the creek
paddling down the creek

08/10/2007 10:36 AM  

Welcomed additions, Chad.  Thanks.

Yea, I am dropping them into tabs, but first building them on a hidden page with just the forms.  2 modules worked fine, but once I added the third to the page with the same field name (though different shortnames for the variable), that's when it triggered the errors on all 3 modules. Three "city" fields were too much, I guess. 

...not a show stopper; I'll start by turning of server-side validation (though I think this required for some of the fields..date, perhaps?), and if that doesn't work, I'll simply move them to 3 different pages to ensure all is well.

 

John
Posts:44
paddling down the creek
paddling down the creek

08/10/2007 1:00 PM  

I now see why the errors display in different places and at different times.

The 'Client-side' errors display first, it seems; therefore, the two short text fields I have display the "Required" prior to triggering the server-side errors. These client-side errors display to the right of the field.

After the user clears these by entering some text, then the server-side errors trigger (I am just clicking submit on a blank form and working through the errors, so all should trigger for testing).  These errors display on the top of the form.

I thought I could just disable client-side and then perhaps the text box errors would display up top with the rest, but to no avail.

Nonetheless, I moved the forms to different pages and all works well.  Thanks, Chad.

Given that different types of forms require different types of validations, perhaps this is not doable, but having all errors either display to the right of the field or on top (or bottom in future releases) would be godsend.   

 

John
Posts:44
paddling down the creek
paddling down the creek

08/10/2007 7:38 PM  

Now it is a show-stopper.

Despite moving the form modules to 3 different pages, when the 3 sets of forms are on the same page, clicking save for one form will trigger the validations for all 3 forms.

I thought perhaps it was related to having the "city" field in all 3 forms, but I changed both the variable name and then the wording (i.e., City (Hotel), City (Rental Car),etc) and it still triggers the validations for each and form displayed on the page.

 

You are not authorized to post a reply.
Forums > Product Discussion - DotNetNuke Modules > Dynamic Forms > 3 DF Modules on Same Page: Validation for all triggere



ActiveForums 3.7

Copyright 2005 - 2008 by Data Springs, Inc.
Terms Of Use | Privacy Statement