Participants Database uses 8 shortcodes to produce different displays. Each can be modified with attributes and customized using a template much as WordPress pages are templated.
The List Shortcode
Shows a filterable list of records, can also include search, sort, and pagination.
The Single Shortcode
Is used to display the values for a single record. It is often used as a detial view that you can click to from the list view.
The Record Edit Shortcode
is used to show an editable record. Usually, a coded URL is used to show the form.
The Signup Form Shortcode
is used to show a signup or registration form that creates a new record. This shortcode also shows the thanks message or the private link recovery form.
The Signup Thanks Shortcode
This is used when you want the user to go to another page after signing up. In that case, it is necessary to use this shortcode to complete the form submission process.
The Search Shortcode
This is used to show a Participants Database record search input when you want it to be somewhere other than at the top of the list display.
The Request Link Shortcode
Use this shortcode only if you want to show the private link recovery form in a different location than the signup form.
The Total Shortcode
is used to show a record count, sum, or other calculation from Participants Database. It is meant to be used inline to show a string or number.
Shortcode attributes provides ways to customize the action of a shortcode.
The table presents a cross-reference to what attribute can be used in what shortcode. Titles link to more info on that item.
template – name of the template to use to display this shortcode. All shortcodes use templates that can be customized and stored with your WP theme. Read about custom templates here…
fields – comma-separated list of field names to include, in the order given.*For the “total” shortcode, this attribute defines the names of the fields that will be totaled to calculate the output of the shortcode. The totaling function will attempt to interpret the values as numbers. If you are using fields that need to be totaled, it’s best to store them without denominations or units.
action – sets the next page after a form submission, overriding the “thanks page” setting for the signup form. This attribute is used to create multiple-page forms: after submitting, the user is taken to the page named in the “action” attribute.
filter – for the list shortcode, defines a set of filters to use on the list before display. The filters are a series of statements such as: state=NY&rating>4 Full explanation of list filters here…
orderby – for lists, determines which fields will used to order the list. Several fields can be used: separate multiple field names with commas. The list will be ordered starting with the first field, then each following field.
single_record_link – for the list shortcode, this sets the target page for single record links in the list. You can use a post ID or the page slug. Single record links must be configured in the list settings.
target_instance – when using the search shortcode, it is sometimes necessary to target the search results to a specific instance of the list on the page. For instance, if there are two list shortcodes on a page, each will have an instance number, which can be seen in the HTML as a class name such as “pdb-instance-1” for instance 1. The search shortcode can then target a specific list instance to show it’s results with a number in this attribute.
target_page – formerly known as “action” this is used with the search shortcode to define which page the search results will be shown on. “Action” still works, so if that’s what you’re using, you can leave it.
search_fields – comma-separated list of fields to use in the search field selector dropdown. If there is only one field, the dropdown is not shown, and all searches will be performed on that one field.
edit_record_page allows you to set the record edit page for a signup shortcode. This is the page (with the [pdb_record] shortcode) their private link will go to.