Josh - Not the OP, but I just built a "Partners" area on a website and we use a similar type conditional based setup. I'm building with Elementor Pro, along with using the Elements Kit add-on, to use "Conditional" based sections on pages. Then using the LoginWP (free) to redirect users after login based on their role.
I use Formidable Registration to register users, add some custom meta, and create a custom role for them. (Level1Partner, Level2Partner, etc) We manually review each Partner and approve them before their account is created.
In the editor, I hide all content except 2 buttons for "Create an account / Login" (Or a logout button if they are logged in). Once they login, the content is shown. Once an active user is on the page it will show/hide specific blocks based on the custom meta and custom user role.
Elements Kit has a nice advanced feature for displaying conditional content, but keep in mind that pages serve two purposes at this point, one for logged out users (prompt to login, register) - and then the second section which is the content when they are logged in, and also has conditionals of it's own for the user-role and access level.
FWIW, the content is not just hidden from the browser with display:none, it's not rendered at all and those specific blocks do not generate any html code.
Thanks Mark! I really appreciate your response. I like your approach.
Please login or Register to submit your answer
This isn't a feature of Formidable Forms. Permissions and role based accessibility is relatively limited.
It's a bit more complicated than can be discussed here, but you could create register user form and then create some user meta for the role type "basic" and "featured" and then use those as filters in your view.
It will take some research and effort. You can use this reference to help you understand how to do such a thing, but it isn't spelled out. You may need a third-party developer to assist you.
https://formidableforms.com/knowledgebase/user-registration/
You might also use stripe or paypal add-ins to collect payments and such.
You can try and do it all manually with some sort of user role plugin that limits visibility of pages based on role as well, but again, research and effort are required, and it isn't always spelled out.