Checkout Fields Manager - Field Types
The purpose of Checkout Fields Manager is to give you flexibility in what data you'd like to gather from your customer. With that in mind, CFM offers 22 different field types so that you may ask your questions in the best possible way.
Common Field Elements
While there are very few field options that occur on every field, there are some that are on most fields. Here are examples:
Show field on frontend
This option allows you to show the field either only in the admin or in both the admin and the front of the site. Here's an example of a field in the builder set to only appear on the back end. Also note the Label and Size.
Here's that same field rendering on the Payment Status page:
This field may be used by the administrator while the customer need never know it exists.
Show in exported CSVs
You may choose to include this field in exported CSVs or not
Where should this meta be stored
You may choose to store this meta in the Payment Meta (different values for all orders by a particular user), or User Meta (same value for all orders by a particular user).
* Note that if you do not have "Require Logins" checked in your settings, the option to store the data in User Meta will not appear because your users may not have user accounts in which to store the data. This setting can be found under Dashboard → Downloads → Settings → Misc → Checkout → Require Login
This is the name of the meta field in which you wish to store this data. If you leave it blank when creating the field, one will be created for you.
Note: Do not change this after it's been created, otherwise it will lose the data previously created while using it.
Note: Meta keys may not have spaces. Convention is to replace spaces with an underscore, but a hyphen will also work.
CSS Class Name
This allows you to set a custom CSS class name just for this field.
All fields that are essentially text types have an option for size.
Storing data in user meta
As mentioned above, you have the option to store your field either in Payment Meta or User Meta. Any data stored in User Meta will be attached to the logged in user making the purchase and be available to that user for future use.
An example would be a customer phone number. Once stored in user meta during a transaction, when that customer returns and makes another transaction while logged in their phone number would be already filled in for them.
The customer will also have access to custom fields attached to their user in their Profile Editor, created by the
Note: The option to store data in user meta will only be available if the Require Login option in Downloads → Settings → Misc → Checkout is enabled.
Field Type Options
There are 22 field types to choose from:
This is for developers to add dynamic elements as they want. It provides the chance to add whatever input type you want to add in this form.
Creates a standard generic set of checkboxes.
This field allows you to present a list of countries to the user. The field options include all current countries, and you have the option to add or remove to create a custom list.
This field allows the end user to enter a date, and optionally a time. You may choose in which format dates are stored, whether time may be entered, and whether the start view should be Day, Month, or Year.
This field appears like a normal text field, but validates input, requiring a valid email address.
This field creates a file upload mechanism, and allows you to set a Max. file size, Max. number of files, and allows you to limit file types to these:
- Images (jpg, jpeg, gif, png, bmp)
- Audio (mp3, wav, ogg, wma, mka, m4a, ra, mid, midi)
- Videos (avi, divx, flv, mov, ogv, mkv, mp4, m4v, divx, mpg, mpeg, mpe)
- PDF (pdf)
- Office Documents (doc, ppt, pps, xls, mdb, docx, xlsx, pptx, odt, odp, ods, odg, odc, odb, odf, rtf, txt)
- Zip Archives (zip, gz, gzip, rar, 7z)
- Executable Files (exe)
- CSV (csv)
This field creates a text field with a default size of 40, and does not include options for meta_key or any of the import/export functions. You also may not create more than one First Name field in a form.
This field creates a standard hidden form field. It has ONLY options for meta_key, meta_value, and whether or not to have it be front-end only or both front-end and back-end.
This field creates an empty field that only bots can see, and they will fill it out. If it's filled out, form submission is rejected. More information about honeypot fields.
This field allows you to provide a title and arbitrary HTML.
This field is a plain text field that is for Last Name.
Note: Forms come with a Last Name field that cannot be deleted, and you cannot add a second one, which means you probably will never use this option. Occasionally Last Name fields are removed by accident, this option allows you to restore it.
This field creates a standard multi-select select box. You may specify the default select text and create as many options as you wish.
This field creates a standard set of radio buttons. You may create as many as you wish.
This field creates a reCAPTCHA tool. In order for reCAPTCHA to work you must insert your site key and private key in the EDD settings panel.
This field creates a text field and presents the customer with the option to create as many more as they wish.
This field creates a section break in the form. It allows for a title and description.
This field creates a standard dropdown select field. It functions exactly like the Multi-select above except only one option may be chosen by the customer.
Terms & Cond.
This field allows you to print a block of html containing Terms and Conditions, and also provides a checkbox with a label for the customer to click to agree to.
This field creates a standard html text input field.
This field creates a standard html textarea. You may set a number of columns and rows, placeholder text, a default value, and choose between plain textarea, Rich textarea, or Teeny Rich textarea.
This field creates a standard text input field but validates for a URL.
This field creates a standard text input field but validates for an email address. It is intended to take the email address of a WordPress user.
Note:: Similar to Last Name, this field should already exist in your form, and you may not add a second. This option only exists so that you may replace your email field if it's accidentally removed.
Once a field type is clicked on, it will be added to the main column in the center of the screen and you will be presented with several options for the field. The exact options can vary from field type to field type, but all fields share a few common options:
- Required: Select "Yes" if you want customers to be required to fill out the fields, or "No" if it should be optional
- Field Label: This is the text shown as the primary label for the field on checkout
- Help Text: This is the text added below the field on checkout to serve as a helpful explanation of what the customer should enter
After you have added all of the fields you need, simply like the "Save" button on the right. Your fields will now be displayed on the checkout.
There are a few checkout fields that cannot be modified by this extension, at least at this time:
1. Billing Address fields. These are required by credit card payment gateways and by the EDD tax system, so these are not permitted to be modified.
2. The Credit Card form used by payment gateways that process credit cards. Since it is vital these fields appear exactly as expected by EDD, these fields are not allowed to be modified.