|
Chris Stambaugh
|
September 23, 2014 at 2:15 pm
Hi,
I’ve used EE4 since the beginning and there are a couple of things I wish were a bit differently.
1. As the administrator, I should be able to over sell an event if I choose. I can be warned of such, but regardless should be able to proceed. (This is how it works with Eventbrite). Is this possible to add at some point in the future?
2. It seems as if the ticket-end date currently defaults to one week after the date the event was created. Would it be possible to make it so that it defaulted to the event start date or the day before?
Thanks in advance for your consideration.
Paul
|
|
Garth
|
September 23, 2014 at 3:33 pm
Hi Paul,
How are you today?
Thank you for the suggestions. Can you please clarify?
1) How is this any different than not setting limits in EE4?
2) How would you suggest the ticket end date be calculate if the said ticket is associated (or grants access to) multiple datetimes?
Thanks for volunteering your suggestions.
|
|
Chris Stambaugh
|
September 23, 2014 at 3:41 pm
1) Not setting limits allows clients to buy unlimited tickets. I don’t want that. But, in special situations, I want to be able to sell an extra ticket or two (even if it is sold out) for an event.
2) If I were the developer, I’d just leave the field blank but require a date before it could be saved. This one week ahead thing just messes me up time, after time after time.
Paul
|
|
Josh
|
September 25, 2014 at 9:20 am
Hi Paul,
Have you tried increasing the ticket quantity limit? This will let you sell more tickets to an event than you originally planned. You can also create additional ticket types for the same event.
When you wrote Ticket end-date, did you mean ticket sell until date? If so, Event Espresso 4’s plugin API lets you change this. There are filters in place that allow the ticket defaults to be changed. Here’s a link to our developer documentation that explains more on this:
http://developer.eventespresso.com/docs/modifying-the-defaults-on-creating-a-new-event/
So with one of these filters, you can make it so the default ticket sell until date is left blank by adding a little bit of code to your custom functions plugin:
https://gist.github.com/joshfeck/9af6fb1f9a31a0cdde79
|
|
Frank Knippenberg
|
September 25, 2014 at 7:56 pm
I two would like to see what Paul is requesting in terms of overselling an event. Changing the limits opens you up to selling more tickets than you intended if multiple people are trying to register while your doing this. But if from the back end I could override it and sell one or two more without increasing the limits for everyone it would be helpful.
|
|
Josh
|
September 26, 2014 at 7:39 am
Hi Frank,
It turns out you can raise the limits and shut the registration down on the front end. Using the show ticket selector option set to No is one example of how to shut down registration on the front-end at any time.
We’re very cautious about adding a feature that will allow for admin side overselling because of some customer experiences with EE3 where events we had some complaints where oversold unintentionally via the admin.
|
|
Chris Stambaugh
|
September 26, 2014 at 4:22 pm
Josh,
Having to try to manage tickets using the show ticket selector is, in my opinion, wayyyy too complicated a way of doing things.
As the supreme user (admin) on my system, I should have the absolute ability to manually oversell an event if I so choose. From a program point of view, maybe it could be an option, disabled by default so it doesn’t happen by accident, but if I decide to allow it, then I deal with the consequences.
Like I mentioned, the Eventbrite system happily allows the admin to oversell an event. Warns that it is happening and allows you to back out of it, but if you don’t you can oversell at your whim.
Paul
|
|
Chris Stambaugh
|
September 26, 2014 at 4:37 pm
Josh,
Your routine for having the ticket end-date works, but only to a point. If the user misses filling in the field, the system just assumes a date seven days in the future thus allowing the problem to continue.
For me, this unfortunately doesn’t solve anything.
Paul
|
|
Josh
|
September 26, 2014 at 6:04 pm
Thanks for taking the time to leave this valuable feedback. I’ve registered your suggestion and we will keep it in mind for future features and updates!
|
