|
Gene Rowe
|
February 6, 2025 at 1:05 pm
I have had the S2Member Pro add on for some time. Right now, my ticket setting will only let me set access levels to WP default roles. I need to be able to select S2Member access levels so unpaid members (Subscribers) can’t access member pricing for tickets. Right now, if they log in to their subscriber accounts, they’re viewed as ‘Members’ by WP since they have an account. I used to have this drop down capability on each ticket but it’s no longer there, just the WP roles. I’m running EE4+ 5.0.34.p, EE Calendar 3.2.16.p, S2Member Pro v.241216 & S2Member v.241216. I’ve run this by S2Member support, but they’re unfamiliar with EE & don’t understand my problem. I’ve also scoured the support forums. Thanks for any help you can provide.
|
|
Tony
|
February 7, 2025 at 6:15 am
Hi there,
I used to have this drop down capability on each ticket but it’s no longer there, just the WP roles.
This isn’t something EE has had within EE4 core, are you sure this wasn’t something custom? Can you post a screenshot of where this loaded previously so I can check into it?
We did/do have a section where you can add a custom capability (which would also allow for this) in the WP user integration add-on, here is how that look in the ‘legacy editor’:
https://monosnap.com/file/sbOGBbWaMn2PTPIGcDZy6q7UMyFgZn
Now in the advanced editor:
https://monosnap.com/file/ogczuGA4DeeE72KcCiQ2FkC4JLO6Tx
Neither of those will list S2 member roles/capabilities by default, but you can manually add S2 capabilities within the field to limit them. For example you could set access_s2member_level2 as a custom capability on the ticket to give your S2 members access to that ticket.
Is that how you did it previously?
|
|
Gene Rowe
|
February 7, 2025 at 8:51 am
You’re absolutely right, of course. My tickets only had the visibility drop down, so per your reply, I looked for the WP user integration add-on in WordPress & found it had been deactivated! I reactivated it and that did the trick. Thanks for your concise & accurate reply!
|
