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.

 

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

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.

 

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.   

 

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.