Access is a WordPress plugin that lets you add custom roles and control their privileges.
Access User Guides include detailed documentation for controlling what actions different roles and users can do on content and what WordPress admin screens users can access.
When you ask for help or report issues, make sure to tell us the versions of the Toolset plugins that you have installed and activated.
Viewing 15 topics - 1,801 through 1,815 (of 2,212 total)
Problem:
The customer wanted to a way to approve new user registration using our access plugin. Unfortunately this is not possible with our access plugin.
Problem:
How to prevent guests (anyone not registered) from accessing/seeign the content either as a post or in a view
Solution:
Then you need 2 steps:
1. Access:
You can hide with access single posts, forms, fields and taxonomies, or just part of Post Contents
2. Views
Views can't be controlled by Access.
That means, a View's list would still be visible to any user, only once the user clicks on the SINGLE post title he would trigger the Access Settings.
In Views, you can use conditional HTML where you check the current User's status, name or role.
In this case you can just check if the user is logged in, if not, hide the content
What you can also do, is to wrap your View (when you insert it into a page/post) into a Access Group Rule, so you can hide the entire View with a certain group.
This Custom Access group has permission settings for every role, so you would set the "Guest" no not being able to read this, and they should therefore not see the page you set under Access Group control.
You can also just wrap the Views ShortCode in a Access Condition, thats also done with the Access Button in the editors of posts / pages.
You can there as well tell WordPress to hide certain content from certain roles.
Problem:
Q1) Users can subscribe to different roles.
- Subscriber to get newsletters
- paid subscribers
Q2) Front end user page
After the user has subscribed they should be redirected to an user page. This should be a front end page that is only available after they log in. This page should list all content created by this user and link to pages where they can edit their content. Typically they should be able to do:
- Create a single post for custom post type 1, after they created this they should be able to edit this but not be able to create additional posts.
- Create posts and delete post for custom post type 2.
- Only see and use the media files uploaded by the current user
Q3) dditionally these users should then not be able to enter the WordPress backend
A2) a) To redirect user to a specific page, in above CRED form, section "Basic Settings", there is an option "Choose what to do after visitors submit this form:", you can set it as the specific page you want.
b) In above page, you can create a view to list posts which author is same as current user:
Filtering Views Query by Author https://toolset.com/documentation/user-guides/filtering-views-query-by-author/
c) for the "post type 1"
Same as above step b), you can create a view to list posts of "post type 1", which author is same as current user, if there is a result, display the post and the edit form link, if there isn't any result, display a CRED form to create new post of "post type 1"
d) for the "post type 2"
You can display the view and CRED form directly.
e) I suggest you with Access plugin, to limit the access of user to the media files:
Access Control for Standard and Custom Content Types https://toolset.com/documentation/user-guides/setting-access-control/
