Responsive layouts are increasingly a necessity in current web design. More and more people will access your site using devices with small screens, and really, screens of a wide variety of sizes and aspect ratios. A responsive layout is a layout that can accommodate all the possible devices: it is responsive to the size and… (read)
Sometimes it’s necessary to create a custom form element to handle a specific need for a UI element in a Participants Database form. The means for doing that have been set up in the plugin, you’ll definitely need some coding skills to get this done, so this post will only briefly cover the basic steps… (read)
When a Participants Database signup form is submitted, it can be checked against the database for an existing record that matches the new submission. If you need to check multiple fields for a match because you don’t have a single field that uniquely identifies a record, here’s how you do that.
I sometimes get requests for adding the ability to delete records from the frontend record edit interface. This is so a person with a private edit link can go to their record page and delete it, or so someone who is managing records from the frontend can delete a record. The best way to do it:… (read)
This article demonstrates how to set up a list search the works on only one field, eliminating the field selector dropdown.
Version 1.5.2 introduced the ability to create forms across multiple pages. By defining the “action” attribute, the user is taken to another form page after each page is submitted. Each page shows a different part of the form by setting the fields or group to show in the shortcode on that page.
Here is a step-by-step breakdown of how that is done.
In this post, I document a feature that you can take advantage of when defining labels for selectors like radio buttons, dropdowns and checkboxes. Each of the selections you define can have a separate value and title, which is the printed value the user sees. The “value” is what is actually stored in the database.… (read)