Difference between revisions of "Pages:Custom Forms"

From Whirlwind eCommerce Wiki
Jump to: navigation, search
(New page: Custom forms allow page content managers to create forms on the fly in the WYSIWYG editor. A knowledge of HTML form coding is required to do this. When a custom form is submitted by a webs...)
 
Line 7: Line 7:
 
;fa: This field should ALWAYS have a value of "USER.formSubmit" - which tells the system this is a custom form that needs to be processed.
 
;fa: This field should ALWAYS have a value of "USER.formSubmit" - which tells the system this is a custom form that needs to be processed.
 
;formType: This field's value is used to classify and organize the form submissions made through this form. For instance, enter "newsletter" as the value if this form is being used to register for the newsletter; or enter "catalog request" as the value if this is a catalog request form. This value can later be used when looking up the form in [[Form Submissions]] so you can filter only certain forms.
 
;formType: This field's value is used to classify and organize the form submissions made through this form. For instance, enter "newsletter" as the value if this form is being used to register for the newsletter; or enter "catalog request" as the value if this is a catalog request form. This value can later be used when looking up the form in [[Form Submissions]] so you can filter only certain forms.
;emailTo: A comma delimited list of email addresses that will receive this form's contents upon submission
+
;emailTo: A comma delimited list of email addresses that will receive this form's contents upon submission. Use to send yourself and others notifications of these forms as they are submitted. Leave empty if there are no recipients.
 +
;redirect: The URL where the visitor should be directed to following submission of the form. For each custom form it is recommended you create an accompanying page that will display a thank you or confirmation message. This page should be where the visitor is directed to using the 'redirect' field following form submission.
 +
 
 +
===CORE FIELDS===
 +
Core fields are visitor-populated fields that can be used to organize and classify form submissions. The emailAddress field in particular is required if you wish to include the subscribe option (which allows visitors to subscribe to the newsletter when this form is submitted).
 +
;firstName: A text field with a maxlength of 50
 +
;lastName: A text field with a maxlength of 50
 +
;emailAddress: A text field with a maxlength of 255
 +
;subscribe: A checkbox with a value of 1 (if checked, this will pass and trigger the newsletter registration process for the entered emailAddress)

Revision as of 20:21, 31 October 2008

Custom forms allow page content managers to create forms on the fly in the WYSIWYG editor. A knowledge of HTML form coding is required to do this. When a custom form is submitted by a website visitor, it is emailed to specified recipients (using the emailTo field below) AND it is placed into the database accessible via Form Submissions in system administration.

Each form has required hidden fields, core fields and custom fields:

REQUIRED HIDDEN FIELDS

Required hidden fields send data to the system that tells it how to process the form. The required hidden fields are as follows:

fa
This field should ALWAYS have a value of "USER.formSubmit" - which tells the system this is a custom form that needs to be processed.
formType
This field's value is used to classify and organize the form submissions made through this form. For instance, enter "newsletter" as the value if this form is being used to register for the newsletter; or enter "catalog request" as the value if this is a catalog request form. This value can later be used when looking up the form in Form Submissions so you can filter only certain forms.
emailTo
A comma delimited list of email addresses that will receive this form's contents upon submission. Use to send yourself and others notifications of these forms as they are submitted. Leave empty if there are no recipients.
redirect
The URL where the visitor should be directed to following submission of the form. For each custom form it is recommended you create an accompanying page that will display a thank you or confirmation message. This page should be where the visitor is directed to using the 'redirect' field following form submission.

CORE FIELDS

Core fields are visitor-populated fields that can be used to organize and classify form submissions. The emailAddress field in particular is required if you wish to include the subscribe option (which allows visitors to subscribe to the newsletter when this form is submitted).

firstName
A text field with a maxlength of 50
lastName
A text field with a maxlength of 50
emailAddress
A text field with a maxlength of 255
subscribe
A checkbox with a value of 1 (if checked, this will pass and trigger the newsletter registration process for the entered emailAddress)