|
shooin
|
July 21, 2018 at 10:18 am
Hello,
My client wants to chant the default qty to 1. Apparently some people are trying to register and when they do so they get an error message because they fail to see and change the qty. In an attempt to make it more user friendly can we change the default qty to 1 instead of 0?
Thanks
Jason
|
|
Tony
|
July 23, 2018 at 5:33 am
Hi Jason,
To do that you need to make the ticket required.
Edit the event, click the cog icon for the ticket you want to be required above and save – http://take.ms/AYg4p
We don’t currently have an option to set the default ticket qty to 1 without making that ticket required.
|
|
shooin
|
July 23, 2018 at 8:47 am
Ok. THat worked. However it shows a red letter “This ticket is required” when in reality it is not required. I did a CSS hack to get rid of it but i am afraid it will come back with a update or something. Can you turn off the This ticket is required without the CSS hack. I am not sure how that could be usefull.. if its required, why register? Not sure.. I guess the problem is that people dont see it and 0 registrations will not work.. so that is going to require some thoughts on everybody to achieve a holy grail solution.
THanks
Jason
|
|
Tony
|
July 23, 2018 at 8:57 am
What CSS are you using?
The ticket selector has its own class and the required ticket paragraph has its own class, so something like this:
.tkt-slctr-tbl .ticket-required-pg {
display: none;
}
Is unlikely to change anytime soon and isn’t really a hack.
I am not sure how that could be usefull.. if its required, why register?
I’m not sure I follow, if it’s required, you much register onto that ticket, there is no option to select 0 of that ticket. If you have multiple tickets you can have 1 or more tickets required but generally, users will have an ‘admission’ type ticket as required, then additional options should the user which to select those.
Not sure.. I guess the problem is that people dont see it and 0 registrations will not work.. so that is going to require some thoughts on everybody to achieve a holy grail solution.
I’m not really sure what you are getting at here to be honest, if you select 0 of anything you get 0.
If you have 5 products to select from and you select none of them, you don’t add any to your cart. If you select a qty of 1 for 3 of them, you get 1 of each product, it’s the same here with tickets.
I’m guessing your events only have a single ticket to choose from and you want that ticket to always default to 1 so they don’t have to select it, in which case, whats wrong with making that ticket required? You either want to register onto that event’s ticket (or multiple of the same ticket) or you don’t, so that ticket being required doesn’t make much difference as far as I can tell?
|
|
shooin
|
July 23, 2018 at 11:33 am
Yeah, I see your point.
Unlike products, these are tickets so the zero does not make sense in a sense still to me personally. I guess in my mind no one can register “zero” anything. Programmatically, I guess it does make sense but in the grand scheme of things (user friendliness for the customer) the thought of zero people registering will never exist.
We registered 147 people for an event, and out of those 3 people tried to register 0 people for some strange reason. This was enough for my client to insist that we make the default 1.
Either way, you guys are doing great work making this as flexible as it is. The challenge again is making the client happy.
Thanks again for the quick response.
|
|
Josh
|
July 23, 2018 at 11:45 am
The zero makes sense when there is more than one type of ticket option, and either can be chosen. In that scenario, changing both ticket quantities to 1 would require unsetting one of the tickets back to zero in order to choose just one.
|
