|
sogtalks@gmail.com
|
October 17, 2017 at 3:38 pm
– We have free tickets for members, functions as an RSVP.
– We also have guest tickets which can be purchased by the Member (or logged-in user).
– They should be limited to one RSVP ticket per Member per event.
– We are having an issue when members return to the site after selecting their RSVP ticket and say a few days later they want to buy a couple of Guest tickets. When we select 2 Guest tickets and proceed to registration > Attendees > now Attendee 1 is pre-filled with the logged in member’s info. Looks okay but we really have to input the 2 Guest’s information in Attendee 1 and 2. When we do that the account information for the logged-in Member is updated to the new information in the Attendee 1 fields.
– so the Member has previously selected the Free RSVP ticket
– come back at a later date to purchase two Guest tickets
1) can we limit the sale of a ticket by role?
2) is the updating behaviour expected or is there a setting to manage this.
Thank you.
|
|
Tony
|
October 18, 2017 at 10:45 am
Hi there,
1) can we limit the sale of a ticket by role?
You can set a ticket to have a minimum required capability, so that only users that have that capability can purchase the ticket but we don’t have any feature to limit the purchase of a ticket to once per member.
One solution Josh came up with when working with another user was to use capabilities on the users account and remove the capability when a ticket was purchased:
https://gist.github.com/joshfeck/51c2ef122616b48cc4846b1f44384859
Note that would require you create a unique capability for each ticket you wanted to do the above for and to customize the function to remove the capability currently set on the ticket rather than a hard coded one.
2) is the updating behaviour expected or is there a setting to manage this.
Updating the information is expected, the WP User Integration add-on keeps your user account synced up with the registration details you enter.
You can disable this within:
Event Espresso -> Registration form -> User Integration settings -> Always sync contact information with WP user profile.
Set that to No and save.
Note that registrations made with a users account that do not match the users details will not show up in the ‘My Events’ section of the wp user integration add-on – https://eventespresso.com/product/eea-wp-user-integration/#espresso-my-events-shortcode
|
|
sogtalks@gmail.com
|
October 18, 2017 at 12:49 pm
1) can we limit the sale of a ticket by role?
Required Ticket option
We tried setting the ticket to have a minimum required capability, but we have two ticket options, one for members as an RSVP and guest tickets. On subsequent visits if a member wants to buy guest tickets they are forced to also select the required RSVP again.
Create a unique capability
– created plugin, activated plugin, as suggested
– added a unique capability and granted to role
– added unique capability to ticket under Ticket Capability Requirement
Results
Not logged in – ticket blocked with message “The [our ticket name] is available to members only. On Sale”. No selection available
Logged-in – ticket available, no limits, multiple log-outs an log-ins.
Seems that the capability is not removed. And you’re correct, would have to create a unique capability dynamically for each ticket, if it worked.
2) is the updating behaviour expected or is there a setting to manage this.
Yes this is what I was looking for, couldn’t remember where to find it.
– this solves my problem. Can now have multiple unique attendees and only one member as required. Thank you.
|
