|
rcfc
|
November 6, 2014 at 2:00 pm
I don’t know all of your many use cases, but the default ticket / price setup seems really obtuse to me. Is there something I’m missing? You have ticket info in three places…
- Event Espresso > Pricing > Default Pricing (rigidly editable, info flows in one direction only from here to tickets)
- Event Espresso > Events > Default Tickets (not directly editable, info seems to flow from tickets to here)
- And within events themselves, you can also just create whatever you need….(Partial two-directional information sharing with the above lists….)
It seems that this organizational system is presented as though it would give you lots of options & save time, but the actual UX ends up seeming really stiff, and the features irrelevant. The defaults are continuously in my way, and then I can’t change them because tickets are locked or whatever…. Forgive my crabbiness, I think I just don’t really understand what you guys are going for here. Is there somewhere that makes this coherent? Some video or text explanation of how you expect me to be using this?
|
|
Josh
|
November 6, 2014 at 2:45 pm
Hi there,
I can try to explain the idea behind making an editable default ticket.
In Event Espresso 4, the “factory” default is a ticket labeled or named “Free Admission” with a price of 0. This default makes sense for a common use case: Those who host a lot of free events. Public Libraries and community-based organizations typically run a lot of free events.
For everyone else, it doesn’t make sense to have the default ticket be named “Free Admission” with a price of zero.
So we made it so the default ticket can be changed to fit their needs.
The Default Ticket Name
Many use cases have the same name for all their tickets (for example their ticket name might be General Admission, Access Pass, or Entry Fee). By allowing the default to be modified, it saves people time when setting up events.
The Default Ticket Price
Along with that, your pricing may be the same for a lot of events. With Event Espresso 4 you can set the name and price and every new event will use the default, but you can still change it if need be. The intent here again is to save time.
I can also explain why the tickets get locked. They get locked after tickets are bought. If no one has bought a specific ticket type, then it will not be locked. The locking prevents ticket relationships from being broken. For example, if someone buys a ticket for $20, but the price were allowed to be modified to $18, the price relationship between the ticket they bought and its current price is broken. Which leads to other things breaking.
If you have some ideas or feedback on how we can make the default ticket name and price better, we’d love to hear them.
|
|
rcfc
|
November 6, 2014 at 11:50 pm
Thanks for the big explanation. It sounds like you’re basically saying that this is all an attempt to save time in a well automated system. I get that, but I also think that in the wild it ends up being pretty awkward — not a time saver. I’ll work on articulating my issues with the work flow & post any ideas I have.
In the mean time, I’ll keep plugging away on it of course. There’s one problem that I encountered tonight, with the Default Tickets. Since all my events are not the same shape, this feature isn’t really useful (one comment here: For those events that are the same shape, it seems much easier to simply duplicate an existing event. This has the same functionality of pre-populating tickets. So I believe it makes Default Tickets sort of redundant.). Anyhow, I went to delete all the test Default Tickets, and there’s one (very random, non-useful) ticket that is locked. How do I get rid of this?
|
|
Josh
|
November 7, 2014 at 6:07 am
Default tickets are only redundant if the entire event is the same. Wouldn’t it be awkward if you had to copy an entire event to get a starting point for the tickets?
There is one default ticket that cannot be deleted, and that’s the base price. However, it can be edited in the pricing admin.
|
|
rcfc
|
November 21, 2014 at 8:51 pm
Just want to follow up with this & say that it makes sense. Somehow, however, for the particulars of my setup, it’s still better to copy an event to get a starting point for my tickets. …But that’s just about the complexities & particulars.
I also see what you mean about the default ticket. I could swear that when I went to delete tickets that last one (the one I couldn’t delete) was not one that made sense. But there are a couple other folks who use EE. It’s possible that they were just editing tickets at that same time.
Anyway thanks, a lot, for all your clarifications.
|
|
Dean
|
November 24, 2014 at 3:02 am
Please let us know if you need further assistance with this topic.
|
