|
jbroner
|
September 25, 2017 at 3:00 pm
Since updating plugin this morning – tickets for various membership levels no longer working. It tells me I have to register to get ticket but I am registered and logged in. I’m using a 3rd-party membership plugin (Paid Membership Pro) but it is no longer working even for default WordPress user levels.
|
|
Josh
|
September 25, 2017 at 3:02 pm
Hi there,
May I ask what’s the capability that’s set in the ticket editor’s Ticket Capability Requirement field?
|
|
jbroner
|
September 26, 2017 at 8:41 am
I have the name of the membership level that I am using in PMPro. It used to work, just stopped after upgrade it seems.
|
|
Josh
|
September 26, 2017 at 10:25 am
If you’re using a membership level role that will not work. You’ll actually need to use a capability for the membership level.
|
|
Tony
|
September 26, 2017 at 10:28 am
If you try setting the capability to read and then view the ticket logged in, does it work then?
|
|
jbroner
|
September 26, 2017 at 12:06 pm
Yes, I am using capability. The membership plugin adds the capability to the interface. I even changed the event ticket to “Subscriber” to test it, and my test user to Subscriber role, and it is still saying event is for members only. It’s just not working anymore like it did.
|
|
Josh
|
September 26, 2017 at 12:27 pm
Hi there,
Subscriber isn’t actually a capability, it’s a role. Like Tony mentioned,
read is a capability. You’ll need to input a valid capability into the Ticket Capability Requirement field.
|
|
jbroner
|
September 26, 2017 at 12:32 pm
OK, so maybe I’m not understanding what a capability is, then. All I know is this worked the other day just fine and now it doesn’t.
So what should I be using if we want only paid members to our site be able to register for an event? Are you saying I need to be able to code in capabilities and it will no longer work with my membership plugin or default WordPress users?
|
|
jbroner
|
September 26, 2017 at 12:42 pm
OK, a little research and now I understand the difference between a role and a capability. But this wasn’t how it worked before upgrade – so why the change?
|
|
Tony
|
September 26, 2017 at 12:49 pm
Can you let us which plugin you updated? Event Espresso core?
If so which version were you running prior to updating this morning?
Did you update PMP at the same time (or any of its add-ons)?
|
|
jbroner
|
September 26, 2017 at 12:53 pm
Hi Tony – yes, I believe it was core. I didn’t update anything in PMPro. I honestly don’t remember what version it was before – but it was installed only recently, so probably the prior version to 4.9.46.p.
Our site is only in development now but it’s crucial I get these events to work with our membership, or the plugin is sadly useless to me. And it was working well at some point.
|
|
Tony
|
September 26, 2017 at 12:58 pm
If I recall correctly, PMP does not create roles for membership levels in the same way something like S2 does.
So are you using the PMP Roles add-on?
https://www.paidmembershipspro.com/add-ons/pmpro-roles/
|
|
Josh
|
September 26, 2017 at 1:02 pm
It may have been a happy accident set in place somewhere that a role could be used instead of a capability for the Ticket Capability Requirement. Which might have been a feature/happy accident in your case, but not intended (and could result in non-members getting access to tickets when they should not).
If Paid Membership Pro does not have a way to assign or check user capabilities, you can find the capabilities for a membership role with the User Role Editor plugin.
|
|
jbroner
|
September 26, 2017 at 1:17 pm
Yes, I am, but I can’t see where to assign a capability to the membership.
OK, so I downloaded a user roles/capability plugin and assigned a capability to the membership level and now I can see the buy ticket, but I’m an administrator. The user level cannot buy a ticket even though I gave that level ee_read_private_events – and changed our ticket option to that capability. So I’m at a loss here.
|
|
jbroner
|
September 26, 2017 at 1:19 pm
Josh – that is the plugin I downloaded, yes. It still doesn’t seem to be working for me.
|
|
Josh
|
September 26, 2017 at 2:00 pm
Can you go in to edit the Ticket Capability Requirement and completely blank out the field, then try setting it to read, then log in with a user account that has the read capability? Usually any WP User account will have read.
Along with that do you have the current version of the WP User Integration add-on activated, and have there been any modifications made to the ticket selector template code?
|
|
jbroner
|
September 26, 2017 at 2:28 pm
No modification to code at all – and yes, using WP User Integration. Setting to “read” does work. Now just have to have a capability that only our paid members will have.
Thank you for being on this and trying to help me.
|
|
Josh
|
September 26, 2017 at 2:36 pm
You can actually create custom capabilities with the User Role Editor plugin. Once you’ve created a new a capability and assigned it to the membership’s user role, you can use that capability in the Ticket Capability field.
|
|
jbroner
|
September 26, 2017 at 3:04 pm
Just tried that and unfortunately that’s not working either. I think I have some major conflict going on.
|
|
jbroner
|
September 26, 2017 at 3:08 pm
OK wait – I might have figured something out. Thanks for your help. Will report back if I continue to have problems.
|
