Home›Topic Tag: Controlling access to front-end content
Topic Tag: Controlling access to front-end content
Access plugin allows you to limit front-end read access to specific pages, posts or custom types and define who will be able to access that content. It also provides the functionality to set access control for specific blocks inside page content, in order to place texts that are visible to or hidden from certain user types.
When you ask for help or report issues, make sure to tell us on which content and user types you are trying to apply access control.
Viewing 15 topics - 556 through 570 (of 587 total)
Problem:
How can I show certain content only to logged in users?
Solution:
This is possible with Access Plugin and also with HTML Conditionals.
In Access you can set entire Types (posts, fields, etc) to not be readable by guests, which then will hide those posts or fields from not-logged in users.
With HTML conditional you can haide single Content or Code in your Views, Content templates and Posts, by wrapping those Contents in HTML conditions.
As example you can check if the current user is logged in and if not, you do not display the content.
Problem:
I only want my CRED form to be available to Registered Users (i.e. logged in). How can I do that?
Solution:
1. You can do that with the
wpv-conditional
so you can hide the link and the form completely from given Roles, logged in status or even single users.
2. Or, you can do it with Access Plugin.
There, what you can do is not allow to edit, submit, and create things with the Form.
If you do it with Access, what happens when a Guest (not logged in user) visits the page and has no rights to submit the form, he / she will find an empty page (by default).
If you use the LINK to the CRED form, that Link will also not show up (by default).
Solution:
You can display role baseed output two ways:
1)
Using [toolset_access] shortcode you can display role based content:
2)
You can also display content to logged in user only using [wpv-conditional] shortcode:
Problem:
Compatibility issue with "WPC-Client" and Toolset access plugin.
Solution:
There is the compatibility issue with "WPC-Client" and Toolset access plugin while editing user profile once you change the custom role from one level to another.
