A few months ago, I wrote a tutorial on how to automatically send an email when a record is updated. I’ve gotten several requests for something very similar: how to send an email to a person who has signed up, but ONLY after their submission has been approved. This is a good way to avoid… (read)
Sometimes, you want to duplicate a configured installation of Participants Database to another site or server. It can be done, it’s a bit complicated, and you’ll need to be familiar with database tools such as phpMyAdmin. Start by installing the plugin in the new location. Activate it to set up the initial database entries, then… (read)
If you have a database already and want to adapt it for use in the Participants Database plugin, you’ll have to set up the plugin to interface with that data and then import the data itself into the plugin’s main database table. Here’s how you get that done. Start with the User Interface Participants Database… (read)
One of the most frequent support requests I receive for the plugin is: can it do multiple databases? Can multiple instances of the plugin be installed? To both questions, the answer is no, it’s not designed for that, but you can do a lot with this plugin and in most cases it’s not really necessary… (read)
The Participants Database plugin offers a few ways to validate the data that is submitted when a record is created or updated on the frontend. Mostly, it’s either yes or no, but sometimes you need more control over that. This is where what’s known as a “regex” is used. If you just need to validate a… (read)
This post was updated November 6, 2019 to be compatible with current versions of WordPress. A very common support request is along the lines of “how can I give my users access to a set of Participants Database records?” There are basically two ways to do this, depending on what privileges you want to give… (read)
I explain how to set up the “lost private link” functionality.