Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is Ticket Type capacity needed now? #168

Open
mihob opened this issue Nov 20, 2024 · 6 comments
Open

Why is Ticket Type capacity needed now? #168

mihob opened this issue Nov 20, 2024 · 6 comments
Labels

Comments

@mihob
Copy link

mihob commented Nov 20, 2024

Question

Why is Ticket Type capacity needed now? In version 2, if a ticket did not have its own capacity, the capacity of the event was used. Which makes much more sense.

For example, we have two ticket types, normal and student, which differ in price. Our event has a capacity of 100 seats, and we don't care which type of ticket is sold as long as these 100 seats are not exceeded.

Why do we have to define another capacity for the types? How is this intended? Or what should you do if an event has no limit on the number of participants?

Additional context

No response

@mihob mihob added the question label Nov 20, 2024
@engram-design
Copy link
Member

So the concept is flipped, the event capacity is the optional thing now, as an overriding constraint. Ticket Types define how many tickets of that type can be purchased.

While it might've made more sense for your events, it was confusing for other types of events where if you wanted to limit tickets for different types. It also decremented these values, which added to confusion.

Happy to entertain an "Unlimited Capacity" setting for ticket types, you'd just need to set the capacity on the event. In your scenario, you'd have 100 capacity set on the ticket types, but would require 100 set on the event capacity as well, to prevent 200 tickets (x100 normal, x100 student) being sold.

@mihob
Copy link
Author

mihob commented Nov 21, 2024

Okay, that would work. And I agree that it was confusing that the capacity value of the tickets was reduced, that's better now.

However, I still don't understand why the capacity is not optional for event and/or ticket type.

@engram-design
Copy link
Member

The capacity is optional for the event!

image

By default, it's set to be the sum of whatever ticket types capacities you have set.

@mihob
Copy link
Author

mihob commented Nov 21, 2024

Yes I know, I mean for both.

  • No event capacity / No type capacity => Unlimited tickets
  • Event capacity / No type capacity => Event capacity is used, no restriction for types
  • Event Capacity / Type Capacity => Both are respected, Event Capacity wins
  • No Event Capacity / Type Capacity => Type Capacity is used

@engram-design
Copy link
Member

Ah, I see what you mean. Yep, more than happy to adjust things to match that.

@mihob
Copy link
Author

mihob commented Nov 21, 2024

Would be nice if the option existed, but I think we can live with your solution for now. So don't stress about it :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants