|
Jim Meyer
|
April 11, 2016 at 5:33 am
I use EE and s2member. I know the specific add-on for EE3 is not out for EE4, but what I would like to achieve is if I enter “access_s2member_level3” at the Ticket Capability Requirement the ticket is available to membership levels 3, 4 and 5. It occurs to me that this would be possible if the field accepted multiple values, for example “access_s2member_level3,access_s2member_level4,access_s2member_level5”) and this would would be useful in general application, not just for s2member. Would you consider implementing this as an enhancement and if not and in the meantime if there any way I can achieve this functionality through a custom hook / filter?
|
|
Josh
|
April 11, 2016 at 12:24 pm
Hi Jim,
You already have this functionality. It turns out that when you input the
access_s2member_level3 capability
for the ticket capability requirement, the membership levels for 4 and 5 can also access it. The reason is because:
1) A Member with Level 4 access will also be able to access Level 3.
2) A Member with Level 5 access will also be able to access Level 3 & 4.
For further information, you can refer to the S2 Member documentation:
https://s2member.com/kb-article/s2member-rolescapabilities/
|
|
Jim Meyer
|
April 15, 2016 at 2:53 am
Thanks. I realised why it wasn’t working. I was using “s2member_level1” instead of “access_s2member_level1”.
|
