• Home
  • blog
  • How to Develop a Membership Site With WordPress: Part 3

How to Develop a Membership Site With WordPress: Part 3

Category: Uncategorized
Final product image
What You’ll Be Creating

Earlier on in the series we covered how to customise the WordPress login and registration forms. We then added some custom fields to our registration form. Today, in the third and final part of this series, we will be covering how to develop a “my account” section for your site’s users whereby users can edit their profile information. 

Page Setup

The first thing we want to do is create a Page Template to house our content. I like to prefix my page templates with the word “template”. So my file is called template-user-profile.php and the opening PHP looks like this: 

I’ve saved this in the root of my theme directory. If you are unfamiliar with WordPress Page Templates I suggest you read the link above. They are extremely handy.

Now let’s head to the WordPress back end and make a page named “profile”, and in the Page Attributes meta box assign it our newly created page template. Once you have published this page, you should have a blank page on the front end: http://yourdomain/profile

User Profile

Now to inject some content into our page. We want the structure to be page content (i.e. whatever is written in the WordPress WYSIWYG) and then our profile form to follow. 

It’s often helpful to get the code from page.php and use that as a starting point for your Page Templates. This code differs a bit depending on your theme, but it will most likely contain a loop that spits out some page content. The content part is normally fetched using the WordPress function get_template_part(). Right underneath where the content has been retrieved, let’s insert our form HTML. So to recap:

  1. Copy and paste the code from page.php into our Page Template.
  2. Find where the content is being output.
  3. Right under that, insert the following code and then we’ll walk through it:

There’s nothing crazy going on here: the form is using Bootstrap markup as our theme is built on Bootstrap. Other things to note are that the form is being sent using the POST method and we have included a wp_nonce_field—this is a type of security token that helps prevent malicious attacks. If you are unfamiliar with WordPress’s Nonces, I’d suggest having a read of this article

Retrieving the Data

With that in place, you should have a form on the front of the site, but it’s not doing much. We want it to display the data we have for the logged-in user. You may have noticed the value attributes in our form are echoing out some PHP. 

value="<?php echo $user_info->first_name; ?>"

Right now that $user_info object does not exist as we have not written the code yet, so let’s start there. Paste the following code before our form in template-user-profile.php.

Using some WordPress native functions, it gets the current user’s ID, and with that we are able to get the user’s data. This is stored in an object called $user_info, and as demonstrated above we can retrieve user data quite easily. To see all the data stored in that object, you can run a var_dump like so: <?php var_dump($user_info); ?>. This can be useful for debugging or just to see what you can access. 

Processing the Data

There is one final piece to the puzzle, and that’s to process the data, thus allowing users to edit their profiles. In order to keep things organised, I have put the membership code into a file aptly named membership.php. This is in the lib directory and has been included in our functions.php file. Once you have done this, open your newly created membership.php file in a code editor, and let’s make the function that will process the users’ data. 

First, let’s quickly run through the logic. When the submit button is hit, we want to check that our nonce field has been sent—this checks that the data is coming from the right place. 

If that condition is met, we want to get the current user’s ID as we will need this to store the data against. Then we want to arrange our data into a structure WordPress likes—in this case it’s an array with specific keys. Before saving the data, we also want to validate and sanitize it. And lastly we want to display messages to our user, either of success or errors.

And the code for all that looks something like this:

Now you might notice that the data is being saved using three different WordPress functions:

  • update_user_meta() for the Twitter name
  • wp_set_password() for the password
  • wp_update_user() for the remaining data

And you are right to question this. Basically the custom meta data (the Twitter name) needs to be processed using the relative function and not the general update user function. As for the password, while it can work with wp_update_user(), I have had issues with it and prefer to use this method. Remember this is only a guide, and often the code is aimed at demonstrating different methods for achieving your requirements. 

Okay, so now we have our function to process the data, but it’s not being called anywhere. At the end of our function you can see there is an action associated with it. So to call that function we just need to use the WordPress provided: do_action();. So paste this line above your form in the User profile page template we created earlier:

<?php do_action( 'tutsplus_process_user_profile' ); ?>

With that in place, when we submit our form it should run through our function and process the data. 

Error and Success Messages

Error and Success Messages

Our profile form should save or reject the data now. Perhaps the two passwords were not the same and did not save. There are no messages to provide user feedback. Let’s save our users some grief and give them some messages. 

In our tutsplus_process_user_profile() function you may have noticed it appends different query strings to the URL depending on the result of the processing. So if everything is saved and successful then our URL will be appended with ?profile-updated=true, and these vary based on the results. What we need to do is trigger a message based on these responses. 

Below I have used a filter to grab onto the content, and through the magic of $_GET we can check the parameters and spit out what we need to. 

Okay, not quite there—we are using a function called tutsplus_get_message_markup() above, but we have not yet defined it. It takes in two parameters:

  • a string: the message to display
  • a string: the severity of alert to show based on Bootstrap  

So let’s define our tutsplus_get_message_markup() function:

Great. Now our members can see if their data is being saved or not. 

Extra Credit

So now we have a working prototype for a membership site. Much of this functionality ships with WordPress, but we’ve styled and tweaked it to make it a better experience for our users. So now let’s just dot our ‘I’s and cross our ‘T’s to improve the experience just that little bit more. 

Firstly, we want to keep non-logged-in users from being able to access the profile page. A simple redirect to the home page will do. I’ve made a function that does just that, and I call it on pages I want to be accessed exclusively by logged-in users. 

Here’s the function, which is placed in membership.php: 

Now we can simply call the function at the top of our User Profile page template. 

Next up we want to keep users—well, subscribers—out of the admin area. And on top of that, let’s remove the admin bar for logged-in users. Again let’s put this in our membership.php.

And finally, it’s not very easy to navigate the login/logout screens. Let’s add some user-specific navigation. What I’ve done is create a function that outputs the relevant code, and this is then called in our templates/header.php where the main navigation is rendered. 


WordPress is an amazing foundation for a membership application. It already has so much of the functionality associated with this type of application. On top of that, the folks at WordPress have made it pretty easy to hook onto events and filter content so we can extend what is already there. 

I hope this has provided you with the methods, ideas and knowledge to develop your own membership sites. This is by no means a full guide on this topic, but rather it serves as a foundation.

Any feedback is welcome, and I shall do my best to answer any questions in the comments.

Things to Note

Please note: if you are downloading the code from the GitHub repository, it includes all the files to get your theme up and running. The idea is that you can grab the repo and just run the necessary Gulp and Bower commands and you’ll be away! If you just want the files that contain code specific to this series, the files are listed below: