Setting a page restriction to a single level

Hey guys,

I’ve left you alone for a while. Please repay that favor with a good answer for a novice to the following question (-:

I want to set page restrictions to either a single member level, or a custom set of member levels (i.e. Level 2 only, OR say Levels 1,4 only). Right now I can only see how to set page restrictions to a level including that member level and all levels above that level (a fully inclusive linear hierarchy such as “Level #2 and higher”).

Is there an EASY way for a novice (non-coder) to configure those types of custom restrictions? Thank you.

Hello Charles,

This is easily achievable using custom capabilities instead of levels, also known as ccaps. You can find a video about them here: Video » s2Member (Custom Capabilities)

Hope this helps. :)

Eduan,

Thanks. I watched the videos on Custom Capabilities and it leads me to another question. Right now, S2MemberPro’s (out of the box) functionality limits the site’s main menu items only to pages that the user has the correct member-level permissions to view. If they don’t have the correct member level to access a page, the menu deletes that page link automatically. That is VERY cool. Will the same dynamic menu configuration occur when I limit user access to specific pages using custom capabilities? or will the user see pages listed on the menu, even though custom capabilities will restrict them from navigating to those pages?

Thank you.

Will the same dynamic menu configuration occur when I limit user access to specific pages using custom capabilities?

Yes. I just tested this and that’s how it behaved. :)

• This reply was modified 4 years, 2 months ago by  Cristián Lávaque.

Thank you.

No problem. :)

The next logical question would be . . . . .

The registration forms that S2MemberPro allows us to create, utilize “Custom Registration/Profile Fields” that can be set to appear only on forms for specific membership levels. That is a great function.

How do we get the same “member-level specific” form field inclusions/exclusions when using the custom capability functionality to delineate different membership types?

Thank you.

You can use the Pro-Form template=”” attribute to specify a custom Pro-Form template that you’ve created for a specific scenario.

So, if you’re selling different memberships on the same membership level and using Custom Capabilities to differentiate between those users, you could create a Pro-Form template for each custom capability, e.g., template-ccap1.php, and then dynamically specify that template file in the Pro-Form shortcode depending on what Custom Capabilities the user selected to sign up with.

This is getting to the advanced level of s2Member customization, but it’s certainly doable. This method would allow you to have a different Pro-Forms for each Custom Capability that you “sell” with your membership, along with a custom set of Custom Registration Fields on each Pro-Form. The registration fields themselves would all be created and set to be applicable to the same membership level, but your Pro-Form template file would only show the ones you want to appear.

Please see this thread for more info on how to create and use custom Pro-Form templates.