Limiting The Visibility Of Posts In WordPress Via Usernames

Controlling who is able to view a post is a simple task once the system is established. Limiting access to certain users has several applications, such as enabling a design studio to distribute artwork to its various clients, or enabling a small school to arrange for homework to be posted online using a cheap and easy solution.

The easiest method to get this system working is to make the recipients of the information “subscribers” (since they need not be able to post) and the distributors of information “authors” (since they should only be able to edit their own posts). This system eliminates several headaches for the website owner by managing who has access to particular posts. The username would be used to identify who is allowed to view certain posts, since it is unique and, for the most part, constant.

The Basics

What Will You Need?

• WordPress 3.1 or later
• Members of various roles
• The ability to modify your theme’s files
• Basic knowledge of PHP and MySQL

What Is a Username?

In general, a username is a means by which to identify and verify a user. It is not the only way to identify a user, but remembering a username is easier for the person logging in than having to remember a random user ID. A username can be made unique to an individual, unlike a person’s name or email address (family members may share the same name, or even the same email address). This ease of use and uniqueness is why usernames are used on most websites that require people to sign up in order to access the website or certain of its features.
To WordPress, a username is means of identifying a user. Paired with a password, a username enables someone to access their profile and, depending on their permissions within WordPress, to access to the administrative pages of the website. A username can be used for many functions in the operation and management of a website, such as karma, prestige, user roles and expulsion.
A WordPress username is unique and impossible for the average user to change. Thus, the system is a potentially reliable means of identifying individuals. This reliability is important for a system in which a post must be visible to only a few people. The permissions of a post should not alter merely because someone has changed their name or email address.

The user page in a WordPress installation. Note that “Usernames cannot be changed.”

Setting Up The Back End

In order for an author to be able to set permissions for visibility, a method of selecting users must be set up on the post editing page. We could accomplish this by one of several methods, one of the easiest and most efficient of which is to create a meta box (or widget) in the post editing page that allows the author to add custom information, as required by a theme or plugin. This information enables us to tell the theme which members should have viewing rights to particular posts.

A Basic Custom Meta Box

Let’s assume we’re dealing with a website for a music school named “ Fancy Flautists.” We will use the name flautist_access in the code for the back end to distinguish it from other custom functions. Justin’s code is a great starting point for this project, but it needs a little customization for our purpose. Place the following code in your theme’s functions.php, and modify the various labels according to your project.

01	/* Fire our meta box setup function on the post editor screen. */

02	add_action( 'load-post.php', 'post_meta_boxes_setup' );

03	add_action( 'load-post-new.php', 'post_meta_boxes_setup' );

04

05	/* Meta box setup function. */

06	function post_meta_boxes_setup() {

07

08	/* Add meta boxes on the 'add_meta_boxes' hook. */

09	add_action( 'add_meta_boxes', 'add_post_meta_boxes' );

10

11	/* Save post meta on the 'save_post' hook. */

12	add_action( 'save_post', 'flautist_access_save_meta', 10, 2 );

13

}

14

15	/* Create one or more meta boxes to be displayed on the post editor screen. */

16	function add_post_meta_boxes() {

17

18	add_meta_box(

19	'smashing-flautist-access',         // Unique ID

20	esc_html__( 'Post Viewing Permission', 'flautist' ),       // Title

21	'flautist_access_meta_box',        // Callback function

22	'post',                 // Admin page (or post type)

23	'normal',                   // Context

24	'default'                   // Priority

25

);

26

}

27

28	/* Display the post meta box. */

29	function flautist_access_meta_box( $object, $box ) { ?>

30

31	<?php wp_nonce_field( basename( __FILE__ ), 'flautist_access_nonce' ); ?>

32

33

<p>

34	<label for="smashing-flautist-access"><?php _e( "Enter the username of the subscriber that you want to view this content.", 'flautist' ); ?></label>

35

<br />

36	<input class="widefat" type="text" name="smashing-flautist-access" id="smashing-flautist-access" value="<?php echo esc_attr( get_post_meta( $object->ID, 'flautist_access', true ) ); ?>" size="30" />

37

</p>

38

<?php }

With Justin’s code, modified for this project, we should have a custom meta box that looks like this:

A basic meta box positioned below the post editing box.

Adding Ease to the Selection

This box can be used as is, and the author would simply input the members who they want to allow to view a post. This would work well if each author had very few usernames to remember; but if the author has long list of usernames to choose from, then a list of members would have to be displayed, and there would have to be a system that allows the authors to choose members from the list. Add the following code to the area just below the original box, just after the closing paragraph tag, to display a list of users with their names, along with radio buttons to grant one of the users access to the current post.

01	<table class="smashing-flautist-access">

02	<tr align="left">

03	<th>Username</th>

04	<th>    </th>

05	<th>Visiblity</th>

06	<th>    </th>

07	<th>Name</th>

08

</tr>

09

<?php

10	global $post;

11	$users = get_users('role=subscriber');

12	foreach ($users as $user) {

13	$user_info = get_userdata( $user->ID );

14	if(get_post_meta( $object->ID, 'flautist_access', true ) == $user->user_login) $ifchecked = 'checked="checked" ';

15	echo "<tr>";

16	echo "<td>$user->user_login</td><td>    </td>";

17	echo "<td align=\"center\"><input type=\"radio\" name=\"smashing-flautist-access\" id=\"smashing-flautist-access\" value=\"$user->user_login\" " . $ifchecked ."/></td><td>    </td>";

18	echo "<td>$user_info->last_name, $user_info->first_name</td><td>    </td>";

19	echo "</tr>";

20	unset($ifchecked);

21

22	} ?></table>

If everything goes well, you should end up with a box underneath the post editor that looks similar to the image below. The form containing the radio buttons gets a list of users that are listed as subscribers and makes the selection of the student with viewing permissions easy, all without the post’s author having to remember any usernames.

A meta box that contains a method to select the particular name and information of each user.

Saving the List

Now that we have generated a list that makes it easy for the authors to pick which members they want to be able to view particular posts, we have to create a system to add the list to WordPress’ MySQL database so that we can retrieve it later. We also need a way to tell WordPress to update this list of usernames in case the author decides later to add or remove someone from a particular post’s list of authorized viewers. The code provided by Justin does excellent work; place his code below in your theme’s functions.php, just after the function that sets up the custom meta box.

01	/* Save post meta on the 'save_post' hook. */

02	add_action( 'save_post', 'flautist_access_save_meta', 10, 2 );

03

04	/* Save the meta box's post metadata. */

05	function flautist_access_save_meta( $post_id, $post ) {

06

07	/* Make all $wpdb references within this function refer to this variable */

08	global $wpdb;

09

10	/* Verify the nonce before proceeding. */

11	if ( !isset( $_POST['flautist_access_nonce'] ) || !wp_verify_nonce( $_POST['flautist_access_nonce'], basename( __FILE__ ) ) )

12	return $post_id;

13

14	/* Get the post type object. */

15	$post_type = get_post_type_object( $post->post_type );

16

17	/* Check if the current user has permission to edit the post. */

18	if ( !current_user_can( $post_type->cap->edit_post, $post_id ) )

19	return $post_id;

20

21	/* Get the posted data and sanitize it for use as an HTML class. */

22	$new_meta_value = ( isset( $_POST['smashing-flautist-access'] ) ? sanitize_html_class( $_POST['smashing-flautist-access'] ) : '' );

23

24	/* Get the meta key. */

25	$meta_key = 'flautist_access';

26

27	/* Get the meta value of the custom field key. */

28	$meta_value = get_post_meta( $post_id, $meta_key, true );

29

30	/* If a new meta value was added and there was no previous value, add it. */

31	if ( $new_meta_value && '' == $meta_value )

32

{

33	add_post_meta( $post_id, $meta_key, $new_meta_value, true );

34	$wpdb->query($wpdb->prepare("UPDATE $wpdb->posts SET post_status = 'private' WHERE ID = ".$post_id." AND post_type ='post'"));

35

}

36	/* If the new meta value does not match the old value, update it. */

37	elseif ( $new_meta_value && $new_meta_value != $meta_value )

38

{

39	update_post_meta( $post_id, $meta_key, $new_meta_value );

40	$wpdb->query($wpdb->prepare("UPDATE $wpdb->posts SET post_status = 'private' WHERE ID = ".$post_id." AND post_type ='post'"));

41

}

42	/* If there is no new meta value but an old value exists, delete it. */

43	elseif ( '' == $new_meta_value && $meta_value )

44

{

45	delete_post_meta( $post_id, $meta_key, $meta_value );

46	$wpdb->query($wpdb->prepare("UPDATE $wpdb->posts SET post_status = 'public' WHERE ID = ".$post_id." AND post_type ='post'"));

47

}

48

}

The three MySQL queries are in place to prevent unauthorized users from viewing protected posts and to hide the posts from the RSS feeds. The first query runs only when new data populates the previously empty custom field, while the second query runs only when the data in the custom field has changed. The third query runs only if the custom field is emptied, and it sets the post’s visibility back to “Public.” All three are protected from SQL injection attacks by using $wpdb->prepare() to validate the data entered into the username form field.
If you don’t like that WordPress precedes the post’s title with the word “Private,” then add the following code to your theme’s functions.php file. This custom function is called when your theme would display a post’s title; it finds any instance of the words “Protected” or “Private” at the beginning of the title and removes them. In the core of WordPress’ programming, the function get_the_title() adds those words if a post’s visibility is restricted and the person viewing is not an administrator. What the following code does is send a message to the action that get_the_title() hooks into, telling it to remove the terms “Protected: ” and “Private: ” from the title. So, you can set a post’s title to begin with either term, and the title will not be altered; this code only affects WordPress’ ability to add to your title.

1	function title_trim($title) {

2	$title = attribute_escape($title);

3	$needles = array(__('Protected: '),__('Private: '));

4	$title = str_replace($needles,'',$title);

5	return $title;

6

}

7	add_filter('protected_title_format','title_trim');

8	add_filter('private_title_format','title_trim');

To allow users at the subscriber level to see private posts, you have to give them that capability. As it happens, some of the code we’ll be using later frees us from having to worry about users at the subscriber level seeing the posts of others.

1	$subRole = get_role( 'subscriber' );

2	$subRole->add_cap( 'read_private_posts' );

You can also grant users at the subscriber level permission to view private pages, in case you want a dedicated page of information that subscribers should know.

1	$subRole->add_cap( 'read_private_pages' );

Setting Up The Front End

Now that we have a way to add members to the list of people who can view a particular post, we have to modify our theme to use this data, and to actually control the visibility of each post based on this list. First, we need a way to get the username of the person who can view a post. Secondly, we would compare the username of the member with viewing permissions to the user who is currently logged in. Finally, we would make the theme display either the post in the loop or an error message (or perhaps nothing at all).
Place this code just after The Loop starts. It goes in single.php, category.php and index.php if you will be displaying posts on the home page.

1

<?php

2	/* Get the post's acceptable viewer. */

3	$flautist_access = get_post_meta($post->ID, 'flautist_access', true );

4	/* Get the post's current viewer, if he or she is logged in. */

5	if(is_user_logged_in()) {$current_flautist = $current_user->user_login;}

6	/* See if the acceptable viewer and the current viewer are the same */

7	if($flautist_access == $current_flautist || current_user_can('author') || current_user_can('editor') || current_user_can('administrator'))

8	{echo ''; ?>

Place this code just before the loop ends. Here is where you can show an error message telling the user that they may not view this post. Or you could leave this code as is to make it appear as though the current visitor is not missing anything.

1	<?php } else { echo ''; } ?>

This is what a hidden post looks like to the public or to a user who is not logged in. They would see what appears to be an error message and are redirected away from the post.

If a person is not logged in and tries to view a restricted post, they would get an error message.

If a user is logged in but not allowed to view a restricted post, they would see either nothing or an error message specific to members.

If a member is logged in and authorized to view a protected post, then they would see the post itself.

Conclusion

Being able to control who can view individual posts is a useful feature with a wide variety of applications. Third-party software can natively do this, but WordPress is widely supported and documented, which means that any security holes that might allow unauthorized users to view restricted posts would be shut in a future update. Plus, it allows you to run an actual blog next to posts with limited visibility. This system could be used by administrators to distribute personalized content, by professionals to send files to clients, or by bloggers to restrict the visibility of certain posts to certain members.
Enabling an author to control who can view their posts can help them tailor the blog’s content to the needs or tastes of certain users. Ultimately, you will have to factor in the purpose and content of your website when deciding whether to use this method. It’s not for everyone, but it suit the needs of owners of small websites who want to deliver certain content to certain people.

Resources

• “Function Reference/add meta box,” WordPress Codex
• “Function Reference/get users,” WordPress Codex
• “Roles and Capabilities,” WordPress Codex
• “Class Reference/wpdb,” WordPress Codex