Details
-
Type:
Improvement
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Won't Fix
-
Affects Version/s: 3.1.5, 3.1.6, 3.1.7, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.4.alpha, 3.4.beta, 3.4.0, 4.1.0, Unscheduled
-
Fix Version/s: 4.4.0
-
Component/s: CiviCRM Profile
-
Labels:None
Description
Right now, if a profile form is deployed on a site that is outside of the civicrm installation, say
you have Civi installed on http://www.exampleA.com
and you have deployed a profile form to
The form validation still takes place on http://www.exampleA.com, this is not ideal because
1) It takes the user away from http://www.exampleB.com which is where the form snippet is on which confuses user.
2) It creates inconsistent browsing experience especially if site A looks very much different from site B.
The suggestion I have would be simple javascript validation on the client side + the existing server side validation on the original site where CiviCRM resides. If that's the case most people who failed out some invalid information on the form will get some kind of alert via javascript but not be taken off the site.
The javascript could just be generated and placed in the form snippet.
Hope this makes sense,
Originally forum post: http://forum.civicrm.org/index.php/topic,18187.0.html