As you know each post (property) below the custom post type "eigendommen" includes an address, contact details and different data blocks. We want to protect these blocks individually by only showing them if a user has an apropriate membership plan. If not, a user should first register (so instead of showing the address, contact details and/or data a text/button to register will appear).
Obviously it will be impossible to setup the content protection for each post seperately (as we will have more than 1 million posts in place over time). So, we want to setup the content protection for each block individually once for the custom post type which will then apply to all the posts globally and automatically.
For the membership management we consider using MemberMouse (hidden link). They have two options to protect content. We can set the access rights, or we can use SmartTags, which are like shortcodes to protect the content. These SmartTags sound like what we would need.
This article (hidden link) explains how the MM_Access_Decision SmartTag work, and as you can see, it will hide content from users who are not members and suggest they signup to see the content. Just what we need. The only thing left is that Toolset should GLOBALLY apply these tags to ALL posts worth of blocks.
Thank you for contacting us and I'd be happy to assist.
I noticed that you're using a Toolset content template named "Properties" to show the content of the single "Eigendommen" pages.
The benefit of using a content template for showing the content on single post pages is that you don't have to edit the content and design in each post individually. You just apply the changes to the content template and it reflects on all posts which use it. So you're good there.
If you were using the classic editor for the content template "Properties" where the content is added as a simple text (i.e. without blocks), the use of MemberMouse's SmartTag or shortcodes for content protection would be straightforward.
However, your content template is using the newer Gutenberg (or blocks-based) editor. For this, I'll recommend getting in touch with the "MemberMouse" support team to see if they offer any content protection method for the content created inside the Gutenberg editor/environment. As this is the new direction WordPress itself is heading in, I'm pretty sure they'll have some function for this or will have some suggestions.
How exactly can we use Toolset's access functionality for the members to restrict content "WITHIN" a page? And apply the restrictions "GLOBALLY" to all posts within the custom post type?
See the above use case.
Each post "eigendom" includes an address, contact details and data blocks. We want to protect these blocks individually by only showing them if a registered user has an apropriate membership plan. If not, the user should first pay (so instead of showing the address, contact details and/or data a text/button to pay should appear).
The steps are as follows:
- "visitor" accesses the page "hidden link". Clicking "meer informatie" he is required to login/register first (THAT'S ALREADY IN PLACE).
- "new subscriber" accesses the same page "hidden link" again. Clicking "meer informatie" the property page shows. However, there are 2 options:
- IF the new subscriber has access to one of the membership levels with the apropriate user role > show content
- IF NOT: new subscriber is not part of the right membership level with the apropriate user role > show buy message and button
We have already setup the user registration form.
If we now just setup the WooCommerce membership plans, can we then connect the registered user together using the Toolset Forms Commerce plugin to finish the process? Or are there any other things to do?
In your content template "Properties" you can wrap the member's only content inside the conditional block that shows it only to the users with the right user role.
And likewise, for users without the right role, you can use another conditional block to show the buy now message and button.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
