Posted: October 9, 2024 at 1:33 pm
Our website uses Paid Membership Pro and Event Espresso and we are currently trying to limit inactive/expired members from purchasing an event at member prices. Only active members should get the reduced rate for an event. Any other users should get the regular rate unless they purchase a membership for the current year. In the ticket we are creating, under the WP Users section, it offers the ability to set a custom capability and limit to those users. We would like guidance on the best solution here. Can we, at the end of the year, dynamically update expired users to remove a capability? If so, what capability should we use to limit the users (active vs inactive/expired)? Or is there an existing capability we can use for active users under PMP that we can use? Then, on expiration, we could remove that capability. Any guidance is appreciated. |
|
Hi there, So in short, you need to base the ability to purchase a ticket based on a user PMP Subscription status, right? How many different PMP Subscription types do you have? |
|
Yes. Right now we have two primary ones – active and non-active. Active accounts may also include sub-accounts (corporate memberships – each person needs to set up a sub account to have access to the resources and discounted registrations). |
|
Ok, so in terms of PMP, how is that set up? 2 Memberships called ‘Active’ and ‘non-active’? Or am I misunderstand how that is set up. I’m asking because what you can do here is hook into when EE checks for a valid capability on the ticket and then check to see if the user has a valid pmp subscription. However, as far as I can tell they don’t have any kind of ‘any’ valid subscription check, you need to be explicit with which subscriptions you check:
But for that to work I need details of the setup. |
|
I am using a web designer to help with more difficult issues – is there a way to get him in contact with you? |
|
They can email support[at]eventespresso.com and I’ll reply there, ask them to include a link to this thread within the email so I know what it relates to. Just to note, we don’t provide custom development (custom code) under general support. I’m more than happy to help point them in the right direction and answer any questions they have (if I can) but if custom code is need we would require a support token (You don’t need one right now, we just prefer to be transparent and let you know ahead of time when they may be required). |
|
The support post ‘Limiting Registration Discounts to Members’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.