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 - 196 through 210 (of 213 total)
Problem:
Toolset doesn's seem to apply any rule (wether post type, post group or WPML group) to the as "shop" designated page used with WooCommerce.
How can we control who can see the ship with Toolset Access?
Solution:
Toolset Access allows the control over Post Types - hence if you control products (the post type "products") with Toolset Access and remove reading rights from a role as an example, that role still can see the shop "page" itself but no products listed in it.
Hiding the single Shop "page" by controlling the post Type "Page" or with a Post Group or even WPML group doesn't work.
This is because the Shop "page" becomes an archive as soon you designate it for WooCommerce's shop "page".
Archives cannot be controlled directly by Access but only it's contents (the products, in this case).
This is the same on any other archive (taxonomy, post, etc).
This page is set to show a different layout for "guests" - showing the login screen.
it works only in english (the default language). when you switch to french or german, you can actually see the content of the page and the access control for the post group doesn't work anymore.
Solution:
I suggest you setup one same layout for all user role, in this layout display a visual editor cell, and use Access shortcode [types_access] to display different contents for different user role.
