|
Michael King
|
November 23, 2014 at 9:32 am
Maybe there is something I’m missing – is there any value in having the default quantity of tickets be 0? Does anyone ever want to buy 0 tickets? I regularly get people who say “registration didn’t work” and my default answer is “Did you pick a quantity?” and so far the answer is always “oops – no.”
Is there some reason the default value can’t be 1?
Yes, somewhere I read a process to change the default with HTML hacking, and while I have the knowledge to do that, for several reasons I don’t want to do that.
|
|
Lorenzo Orlando Caum
|
November 23, 2014 at 3:53 pm
Hi,
The software has to be able to handle are variety of use cases.
You can set the minimum to 1 via the advanced options for a ticket.
—
Lorenzo
|
|
Michael King
|
November 23, 2014 at 11:26 pm
I set the minimum to 1 in advance options, but that had no effect I can see. On the event page, still starts with a “Qty” of 0; and the REGISTER NOW button throws up an error rather than substituting 1. Maybe I misunderstood what you’re telling me?
|
|
Tony
|
November 24, 2014 at 5:57 am
One of the reasons the ticket selector defaults to 0 is as you add more ticket’s to an event your attendee would need to remove a qty from each of the tickets they did not want to register onto.
Currently they simply add a the qty of tickets they do want to register for.
Adding a minimum qty within the advanced settings will set the ticket selector to start at 0 and then the minimum qty (for the reason above). So here is an example with a min qty set to 3 – http://take.ms/ZItfM
However we do have a tutorial on how to modify this behaviour and start the ticket selector with a value of 1 which should work as you require. This is available here:
How to Setup a Default Value of 1 for the Ticket Selector
Does that help?
|
|
Dean
|
November 24, 2014 at 6:06 am
Hi,
Sorry about that, the above does work, but what will happen is it will still show 0 and then the minimum required. E.g. if you entered 10 as a minimum required the dropdown would go: 0, 10, 11, 12 etc.
Looking at the code, it is not currently possible to swap the 0 to a 1. It could probably be achieved via JavaScript.
I’ll certainly add a feature request for this as it was a popular request in EE3.
|
|
Dean
|
November 24, 2014 at 6:12 am
There’s a jQuery example here if that is helpful – https://eventespresso.com/wiki/setup-default-value-1-ticket-selector/
|
|
Josh
|
November 25, 2014 at 8:31 am
Hi Michael,
I want to figure out the intent of your question because I’m not 100% clear on how your events are set up. Am I assuming that all your events have only one ticket option? If so, that would make sense why you think it wouldn’t make sense to have a zero option.
In which case, what we could do is ask the developers to change things so if there is only available ticket for an event then the default quantity automatically changes to 1 instead of zero. The zero quantity option would still be there if there was more than one ticket option available.
Anyway, please let me know if that’s how your events are set up.
|
|
Michael King
|
November 25, 2014 at 10:00 am
Josh – happy to share. Not quite as simple as you are thinking but almost – I often have more than one ticket but they will be an “early bird” and a regular price that are available for purchase on different days, ie only one available at a given time. I will probably have one and only one event in the spring with multiple on sale at the same time, and in that circumstance I can now see how the zero default makes sense, but it’s a minority of my use cases. I wonder how that stacks up with your other users?
For my purposes, this would not have to be automated – I’d be happy if the min-max quantity in the advanced options would set the default. Or a separate selector would also be fine.
Thanks for asking! I always tell people you are great to work with.
|
|
Josh
|
November 26, 2014 at 10:17 am
Hi Michael,
I’m not sure how the use case you describe is different than: “if there is only available ticket for an event then the default quantity automatically changes to 1 instead of zero. The zero quantity option would still be there if there was more than one ticket option available.”
Can you explain how it’s not quite as simple as the solution I describe?
|
|
Michael King
|
November 26, 2014 at 10:40 am
Ok, let me try this again – my last event had two tickets, one for early registration price, and one for late price, with available dates such that only one is buyable at a given point in time – eg Sept 1 to 30 for one, and Oct 1 to 14 for the other. That means that while there are two tickets, but a minimum quantity of 1 is the logical choice.
Would be ok with me if EE4 was smart enough to sense that situation and substitute a min qty of 1, but that sounds more difficult for ee4 to figure out:
IF <only one ticket created> THEN set min qty to 1
ELSE <IF more than one ticket created AND available dates overlap> THEN set min qty to 0
ELSE set min qty to 1
Maybe we are saying the same thing, as I’m not entirely sure what you mean by “if there is only [one?] available ticket for an event” – available by dates, or only one created? [BTW, I think there’s a word missing in your first response]
And again, I don’t know if my case works for a lot of other users, maybe everyone else has much more complicated events. I’d be quite content with a manual selection, like that MIN/MAX quantity selector in the ADVANCED OPTIONS.
|
|
Josh
|
November 26, 2014 at 1:52 pm
Yeah the missing word is one, sorry about that.
I’ve made a ticket that’s requesting a change to the ticket selector. The request is for dynamically remove the “0” option when it doesn’t make sense to have a “0” option.
|
