|
Somatic Practice
|
December 3, 2019 at 3:57 pm
Hi, I’m looking for a solution that would allow a person who has attended an event to get a repeat discount if they attend another of the same event (we do classes that some students repeat). We were planning on using a members-only ticket, but we want to make sure that it’s only available to students who have already taken that class (attended all three date-times of an event). I searched the forums, but couldn’t find this use case. Really, what I need to know is what Member plugin would be able to accomplish this- essentially, giving a user membership status after they attend all three date-times for a single event.
Or, is this approach the wrong way, and the best way would be to send a discount code? We would still like to have a way of validating that they’ve taken the classes without having to check manually, so we’re wary of just giving out a code that would apply a discount. Perhaps a one-time use code?
Open to other suggestions as well. Thanks!
|
|
Tony
|
December 4, 2019 at 4:37 am
Hi there,
Really, what I need to know is what Member plugin would be able to accomplish this- essentially, giving a user membership status after they attend all three date-times for a single event.
Out of the box, none of them will without some custom development. Almost any membership plugin will be able to do what you are looking for as you could do it with a custom capability and the member-only ticket as mentioned, but none of them will do it out of the box as your use case is specific to Event Espresso.
Or, is this approach the wrong way, and the best way would be to send a discount code?
Either of the two methods mentioned can work but if you want this to be automated so you don’t need to confirm the user has taken the ‘full class’ manually you’ll need custom development however you do it as EE doesn’t have this functionality built-in.
So you can either monitor registrations and add a custom capability to the user, or monitor registrations and add a custom promotion code, both require similar code.
Adding a capability (if your users are required to log in) is the most seamless for the user but may require more work on your part if you then want to hide that option from others if they don’t have the capability.
How comfortable are you with PHP?
|
