|
wkcde
|
January 15, 2021 at 3:33 pm
We have a class that is held weekly but you pay by the week and can come as you please. What I’d LIKE to do is have 1 event, 52 datetimes, and 2 tickets – member & non-member. But if I do that, it signs users up for all the weeks when you pick a ticket instead of using the combination of datetime/ticket as your booking. For 2020, we ended up making 2 tickets for EVERY WEEK even though the tickets were the same 2 for each datetime. What happened was it created so many input vars it exceeded our server setting of 4000 inputs. (Which I still can’t figure out how it got to 4000??) Plus it’s just more unwieldy to make that many tickets.
In a similar example, what if you put on a play every night for a week with tickets like Left Orchestra, Right Orchestra, & Balcony but the balcony was not available for the Tuesday or Thursday shows. It seems like you should just be able to make Left/Right Orchestra tickets and a Balcony ticket but not assign the Balcony ticket to the Tuesday and Thursday datetimes.
I’m sure others have hit this. How did you set it up?? Thanks!
|
|
Tony
|
January 18, 2021 at 11:07 am
Hi there,
The examples you’ve given here would be considered ‘recurring events’ (events that happen on a set pattern, hourly/daily/week/monthly etc) and currently, Event Espresso 4 does not officially support recurring events. For some event types you can create the event and duplicate the datetimes/tickets etc but your right, it does become unwieldy with the current setup when you get to higher numbers of tickets.
So with your current examples above the way you mentioned setting it up with 2 tickets per DateTime is how you would need to set this up within Event Espresso currently.
Tickets grant access to datetimes so its the ticket that determines ‘what’ the attendee can attend, which means any changes to the dates (including 1 date per week) needs an individual ticket for that week.
What happened was it created so many input vars it exceeded our server setting of 4000 inputs.
That’s not uncommon and the max_input_vars limit can be increased on the server to accommodate this. Themes can also add multiple inputs to the page and so also run into the same issue (we’ve seen themes add 14,000 inputs to every page on a site).
Which I still can’t figure out how it got to 4000??
Inputs hold values, every value you see is an input and then there are also hidden inputs, the input count includes them all.
By default you’re looking at 13 inputs on a DateTime and roughly 35 per Ticket (due to the number of options on tickets), then tickets and datetimes allow you to specify the DateTime/Ticket it applies to, each of those is an input meaning as your add more tickets the inputs can increase rapidly.
Now having said that, we are aware that the number of inputs can cause issues for some users and have rewritten the event editor to work around this. The beta version for that re-write will be available on our pre-release channel relatively soon, from there we’ll discuss any feedback given by testers and start working towards including that into Event Espresso core itself which then sets the path for working towards support recurring events.
In short, with the current version of Event Espresso 4, how you had it previously is how you would need to set this up but we are aware that a better solution is needed for recurring events.
|
|
wkcde
|
January 18, 2021 at 5:52 pm
Thanks Tony. Yes – I keep increasing the max_input_vars setting on the server.
|
|
Tony
|
January 20, 2021 at 7:11 am
Yeah I understand, as you add more tickets/datetimes (or anything else to the editor for that matter) you’ll need to increase that value but it is something we are working on fixing.
|
