|
Universal Group
|
April 27, 2017 at 8:54 am
On specifically this event we can not assign ticket for any new events.
Link: https://www.theuniversalgroup.ca/events/traffic-control-person-tcp-flagger-certification/
We have events for May 8, 9, 2017 (sold out), May, 13, 14 2017, May 15, 16 2017 and May 18, 19 2017. There are tickets already created and some sold for May 8, 9 and May 18, 19 but when we try to create and assign tickets for May 13, 14 & May 15, 16, the tickets do not save after clicking update. Also when I look at the May 8,9 or May 18, 19 events, either does not show the ticket assigned and when we try, it does not save either.
|
|
Tony
|
April 27, 2017 at 9:01 am
Hi there,
Generally, if the tickets don’t save when you update the event it is because you have hit your max_input_vars limit on the server.
If you add a ticket and sit on the event editor for a few seconds, do you see a popup stating you have reached the max_input_vars limit?
How many datetimes and tickets do you have on the event in total?
|
|
Universal Group
|
April 28, 2017 at 7:06 am
We can not see any max_input_var error on the site. There are currently 24 tickets which are assigned to 29 eventdatetime. We have tried to create the new ticket through both ways ( under event datatime & under tickets) but we can not create new ticket for any dates. There is no error after saving the ticket & the page loads properly.
This issue is not appearing on any other events.
|
|
Tony
|
April 28, 2017 at 7:44 am
Yeah it’s likely you’re hitting the max_input_vars limit on your server with that number of tickets/datetimes.
You can check the value within Event Espresso -> Maintenance -> System information.
Search for ‘max_input_vars’, what value is set?
You could just try updating the value through your `.htaccess file by adding something like:
php_value max_input_vars 3000
Then check the value updates in the above location and try adding another ticket, does it work then?
(Note some hosts don’t allow you to update max_input_vars through .htaccess, if you are unsure, contact your host and have them update it for you)
This issue is not appearing on any other events.
Do the other events have less datetimes/tickets?
|
|
Universal Group
|
May 1, 2017 at 9:33 am
Hi Tony. my developer is reviewing the information that you provided. I was testing a new event date for June 1, 2017 under the particular course that is giving issues and while I was able to successfully add the event date, I could not add a ticket for that date. I then tried to delete the date and I got a pop up that said “You cannot add this datetime to this ticket because the ticket has a sold amount that is greater than the amount of spots remaining on the datetime.” When I look back at a couple of tickets that the client has sold tickets for, a previous event had a limit of 2 tickets but the client had 9 registrations, another had 6 tickets but 15 registrations, another had 4 tickets and 7 registrations. An upcoming event has a limit of 8 tickets and currently 10 registrations. Is there any way to share my screen with you so you can see what we’re experiencing or upload screen shots? Rob Ancell on behalf of Kobie. You can email me at rob@ancell.ca
|
|
Universal Group
|
May 2, 2017 at 3:43 am
Thanks!
The issue is sorted after increasing max_input_vars limit on server.
|
|
Tony
|
May 2, 2017 at 4:54 am
Great, I’m glad it’s working for you.
To give a little more info on these, max_input_vars is a setting on your server that states how many <inputs> can be on a single page.
Each section that holds a value, something you can change etc on the page is an input. If you go past the number of inputs max_input_vars allows your server will simply ignore the inputs after X amount (X being the amount set, by default it’s 1000) when you save the event.
The value you need depends on the amount of tickets, datetimes and various other options you have on the page (you theme may add a custom section with its own settings for example, that takes inputs) so if you run into this again, you likely need to increase the value again.
|
