|
The Loved Child
|
October 24, 2017 at 1:19 pm
I discovered a configuration error in one of my events today. While I know how to fix the specific issue, I’m wondering if there’s a way to avoid/detect it in the future.
I have an event posted that has two different tickets available – for one person, or for two people with a $10 discount/person. The min/max number of tickets is set to ‘1’ for the one-person ticket, and ‘2’ for the two-person ticket. But I noticed this morning that the maximum ticket per order field was set to ‘1’. The result was that even if someone selected the couples ticket, even though the correct price (2 tickets) was listed on the event page, the registration only processed a form for one person, and they were only charged for one ticket.
Thanks!
Adrienne
|
|
Tony
|
October 25, 2017 at 8:39 am
Hi Adrienne,
I’ve created a ticket for this, however as your basically telling EE you want a single ticket per transaction its technically function as it should.
The ticket selector switches to radio buttons for single ticket events and all of those radio buttons use a qty of 1 (as that’s all the event allows) and which then means it’s skipping the check for min qty on the event as you can only have 1 regardless.
I do think there’s some user proofing we can add the help with this (possibly removing the tickets from the ticket selector with a min qty less than the total allow tickets) in a future version but for the time being the admin would need to select the correct min qty they want to allow on the event.
|
|
The Loved Child
|
October 25, 2017 at 11:25 am
Thanks! I’ll go through and make sure our other events are set correctly. I also updated the default setting for max tickets per order to 3, so hopefully we can just ignore that field in most cases for now.
I know it was our configuration error, but some user proofing in a future release would be super – removing events that don’t match the criteria, or a warning of some sort.
Thanks again!
|
|
Tony
|
October 25, 2017 at 12:36 pm
I also updated the default setting for max tickets per order to 3, so hopefully we can just ignore that field in most cases for now.
Just to confirm, you want users to be able to purchase 3 of any combination of ticket available on your event?
If you want either a single or couple ticket, you can set that option to 2. If you want the option of a Single AND Couple ticket, you need the option to use 3.
I know it was our configuration error, but some user proofing in a future release would be super – removing events that don’t match the criteria, or a warning of some sort.
I’ve added this thread to the ticket and we will be looking at adding some additional user proofing for this eventually, however, just to note, we are currently working on other areas of the plugin so this is unlikely to be fixed ‘soon’.
|
