Allow access to more than one role

Thank you for your kind words and feedback.

The problem certainly sounds like a bug and I will look into it. It is on the roadmap to be able to create more “hierarchical” restrictions, so that you do not have to create the same conditions twice.

I can confirm this is a bug.

Is it possible for you to open wp-content/plugins/restrict-user-access/restrict-user-access.php and replace function authorize_access with:

public function authorize_access() {

		$posts = WPCACore::get_posts(self::TYPE_RESTRICT);

		if ($posts) {
			$kick = 0;
			$roles = $this->_get_user_roles();
			$this->_init_metadata();
			foreach ($posts as $post) {
				$role = $this->metadata()->get('role')->get_data($post->ID);
				if(!in_array($role, $roles)) {
					$kick = $post->ID;
				} else {
					$kick = 0;
					break;
				}
			}
			if($kick) {
				$action = $this->metadata()->get('handle')->get_data($kick);
				self::$page = $this->metadata()->get('page')->get_data($kick);
				switch($action) {
					case 0:
						if(self::$page != get_the_ID()) {
							wp_safe_redirect(get_permalink(self::$page));
							exit;
						}
						break;
					case 1:
						add_filter( 'the_content', array($this,'content_tease'), 8);
						break;
					default: break;
				}
				return;
			}
		}
	}

Great !

I had the same problem and the new code function seems to fix the problem.

Thanks again for a great plugin !

Also had the same problem. I set some pages’s restrictions to subscribers only but the admin and editors could not view those pages.

Will this change be integrated in the next update?

I tried to use the new code but still not working. I’ve set up both admin and customer to view this page: https://staging2.gypsyorganicfoods.com.au/co-op-order-form/
but its still visible to people that are not-logged in. Not sure whats wrong…

Jeerish,
Make sure your restrictions show Negate group | Target this context. This means that the only the role assigned will have access to the pages specified. It looks like you have Negate group | Target all but this context.

I hope the wording improves in the next version so it is more intuitive.

This has been fixed in version 0.3 along with other improvements!

@eric3d

I am open to suggestions on how to explain the “negate” functionality better.
Negate group | Target this context means that the restriction/Access Level will be applied to the content (context) added to the condition group.
Negate group | Target all but this context means that the restriction will be applied to all other content (contexts) than added to the condition group.

E.g. if you add “All Posts, Category A” to the condition group and choose negate, only users with this Access Level (or higher) will be able to see all other content on the site than posts in Category A.

It’s working perfectly for me now! Thank you so much for your quick response to the issue.