A very common support request is along the lines of “how can I give my users a login and password to access their profile?” Often, they are just looking for how to use the plugin as a way to register members who would have special privileges. The plugin wasn’t designed for this kind of thing; it doesn’t have any way of logging a user in, checking to see if they’ve logged in or giving them certain capabilities.
We don’t have to work too hard to get these kinds of features, though: they are already there, built into WordPress. By using a couple of plugins, you can create a custom user role that works exactly as you need. I usually suggest “User Role Editor” and “Front End Users” to set that up.
Participants Database can work very well with WP users, but it can be a little tricky figuring out how the two functionalities will work together. In this post, I lay out a simple scheme that can serve as a starting point for your own integration. What I describe here won’t require much coding, but you’ll probably need to get deeper into the code if you want to take things beyond this.
Relating Records to Users
The easiest part is relating a record to a user. When a user is logged in, several pieces of information about them is available. All we need to do is capture a bit of information that will identify the user and store that with the record. I’ll provide an example of how to do that.
Create a field to hold the user login. Title it “User Login” and the name will end up being “user_login.” Set the form element type to “hidden field.” Set the default to
current_user->user_login That will grab the “user_login” property of the current_user object when a new record is created. If your application allows users to create multiple records, they will all be associated with the user through this value. Be sure to set the field to appear in the signup form by checking the “signup” checkbox.
Of course, for this to work, your signup form has to be accessible only to logged-in users.
Showing a List of the User’s Records
It’s not difficult to filter a list display so that it only shows records that relate to a particular user. We need to do this in PHP, but it isn’t too complicated. If you know your way around WordPress templates, you can do this in a template. While that may be the best way to do this, it is a complicated subject on it’s own, so we’ll take a simpler way. You can use PHP directly in your content by installing a plugin: “Insert PHP” is a good, simple choice.
The trick is to use a dynamic value to set the “filter” attribute of the list shortcode. We get the current user’s login and use that value to show only those records that were created by that user. Put this code into the content where you want the list to appear:
echo do_shortcode('[pdb_list filter="user_login=' . $current_user->user_login . '"]');
The way this works is the “do_shortcode” function simply executes the shortcode defined by the string in it’s argument. By assembling that string with a PHP variable, we get a dynamically-generated shortcode. This basic technique can open up a lot of possibilities without doing much coding at all. And, of course, you can use a custom list template with this or any other shortcode attributes you want.
You may want to combine this with: Adding an Edit Record Link to the Frontend List
If the page is visited by a user that is not logged in, no records will be listed, but you may want to put this where only logged-in users will be.
Showing the User an Editable Record
If each user only has one record associated with them, you’ll probably want a way to let them edit it. Showing a single, editable record is a bit trickier because we need to find the record id of the user’s record, but the plugin has methods to help us do that.
Here is the code:
echo do_shortcode('[pdb_record record_id="' . Participants_Db::get_record_id_by_term('user_login', $current_user->user_login, true) . '"]');
The core of this is the call to Participants_Db::get_record_id_by_term() to which we supply the name of the field (or term) to look at and the value to match. The method returns a single id number, if there are multiple matches, the first in the series is returned. (This method can also deliver an array of matching id numbers, if you want to do something with all the records that match. Change the third argument to false.)
The rest is just using that value to select the record to show in the shortcode.
You can probably figure out how to show a user’s single record with what I’ve described here. With the right template, that could be something like a user profile or dashboard page.