|
Universal Group
|
December 6, 2017 at 1:30 pm
One of our event espresso classes is super slow to load in the admin dashboard. It takes forever to load when you open initially or after editing and clicking update. What makes it different from other classes in our system is that it has numerous future dated events and tickets. We would ideally like to schedule our tickets a year in advance but this sluggishness is really getting in the way.
We are also seeing that on this same event, we cannot update the venue. When we add a venue and update, it does not save it.
We tried deleting old classes and tickets to see if this helps but it has not.
WordPress 4.8.4 running EE 4.9.49.p
Checked with the host to see if it was something to do with low server resources but it is not. The site is well under the server resource threshold.
Not really sure what to look for and help is needed.
|
|
Tony
|
December 6, 2017 at 1:44 pm
Hi there,
Roughly, how many datetimes and tickets do you have in this single event?
We are also seeing that on this same event, we cannot update the venue. When we add a venue and update, it does not save it.
If you have a lot of datetimes and tickets your likely hitting the servers max_input_vars value.
If you go to Event Espresso -> Maintenance -> System information.
Search for max_input_vars and what value does it show?
|
|
Universal Group
|
December 6, 2017 at 2:10 pm
Hi Tony
There are 110 event dates for this one course. 1/2 for 2017 and 1/2 for 2018.
Here is what I found about Max Input Vars
max_input_vars 4000
version 5.6.1
|
|
Universal Group
|
December 6, 2017 at 2:11 pm
I should include this too:
global_value 1000
local_value 4000
access 6
|
|
Tony
|
December 6, 2017 at 4:51 pm
It will be the number of datetimes on your event that is causing the slow loading times, that’s a lot of data that needs to be pulled in for the event.
I’d recommend breaking the event dates out into smaller events, maybe a single eent that holds 1 months woth of datetimes/tickets.
I should include this too:
global_value 1000
local_value 4000
access 6
The default is 1000, the local_value means your sites has been updated to use a different value from the default (4000).
With the number of datetimes/tickets on that event, it’s likely your hitting 4000 inputs and that’s why the venues doesn’t save (inputs over 4000 will be ignored by your server on save/update) if you add an additional datetime or ticket and save, does that datetime/ticket then disappear again?
|
