Access provides a set of hooks that allows integration with third-party plugins, in order to use its role management interface and functions.
Access also offers built-in integration with CRED and WooCommerce plugins.
When you ask for help or report issues, make sure to tell us which plugin you are trying to integrate.
Problem:
Relevanssi has some problems when it comes to checking if it can show private posts to a user, if the post is in a custom post type.
Relevanssi doesn’t actually check the what the capability to read private posts is called, but instead assumes it’s read_private_slugs, where slug is the name of the post type.
Solution:
You can use the Beaver Builder with Views to create Content Templates for single custom posts in Views and design the output with Beaver Builder and later on with Layouts you can use the content template cell to add such designed content template to your layout. You will not be allowed to use Beaver Builder page builder with Layouts and its expected.
1) Edit the page "Registrazione NCC", section "Post Group", choose option as :
No Post Group selected.
2) Dashboard-> Toolset-> Access Control-> CRED form
in section "CRED Users Frontend Access",
find "Create Custom User with CRED Form "Registrazione NCC"", enable option for guest user.
Problem:
What are the options for displaying different content to different users on the front-end?
Solution:
To display different content on the front-end according to some criteria you essentially have two options.
If the thing being tested relates to the person doing the looking (the user browsing the website is registered and has a certain role because they have paid for a particular membership, for example) then you can use Access to restrict the visibility of whole pages, or to selectively show certain content on a page (as described here: https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/).
If the thing being tested relates to the thing being looked at then you would need to add custom fields to the content being viewed and then use the wpv-conditional shortcodes to test the content of those custom fields and selectively display what is wrapped in the shortcode, as described here: https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
