|
denise
|
July 19, 2017 at 10:55 am
Hi,
I am using ee4 for about 3 years now, and I have events that repeat every week, so I have multiple date times (30-40) on one event. I seems to take a long time (from the users perspective) to load our calendar. Also adding new event dates and updating takes a long time.
I am wondering if I move EE to an new database to remove the older registrations would be helpful? Would it speed things up? And if so… How would I go about doing this?
Thanks
Denise
|
|
Josh
|
July 19, 2017 at 11:07 am
Hi Denise,
Moving the database will likely cause errors if it’s not done correctly. Here’s what I suggest doing first:
1) Contact your host to see if they can run a repair tables script, they may also spot something that’s causing slowness and adjust.
2) Set the calendar shortcode to show_expired=false and if possible adjust these two settings in Event Espresso > Calendar > Advanced under memory management:
Display Attendee Limits > No
Disable Categories > Yes
3) 30-40 datetimes is tremendous amount of data to pull in for a single page request on the admin side and on the front end event page that displays the ticket selector. If those can be broken up into smaller events where there’s less than 12 datetimes per event then you’ll notice a significant speed improvement.
|
|
denise
|
July 19, 2017 at 4:55 pm
HI Josh,
I setup the updates you suggested and will contact my host.
About the Datetimes… I have the 10 different events that repeat every week for the whole year…. Without recurring events on ee4, adding new dates times is easy from the perspective that I just have to duplicate and add a new ticket…. Is there a better way to do this?
Thanks
Denise
|
|
denise
|
July 19, 2017 at 4:59 pm
Josh… I tried Disable Categories > Yes and every time I modify it and save it reverts back to NO?
|
|
Josh
|
July 19, 2017 at 5:13 pm
Without recurring events on ee4, adding new dates times is easy from the perspective that I just have to duplicate and add a new ticket…. Is there a better way to do this?
Instead of duplicating a datetime, you duplicate the event instead.
I tried Disable Categories > Yes and every time I modify it and save it reverts back to NO?
That’s an indication that your _options table needs to be repaired, which would also contribute to the site’s slowness. Do any other calendar setting changes stick when you save? You could try resetting the Calendar settings (if you open the main calendar settings on another window/tab, you can resave the main settings page after doing the reset).
|
|
denise
|
July 20, 2017 at 4:32 pm
For the “Duplicating event vs datetime” It’s painfully slow to do it this way… Remember its 10 events repeated each week… That would be 500 events I have to duplicate, and edit with the correct date time… Let me know if you have a better faster way.
For the “Disable Categories” Looks like none of the other settings take effect. I reset the calendar and I am still not able to make and settings changes.
|
|
denise
|
July 20, 2017 at 4:43 pm
Also for clarification, I also ran the repair on the database. But it did not impact this. When Repairing the database I got this message for any table with esp in it:
wp_esp_answer] note: The storage engine for the table doesn’t support repair
Not sure if these are your tables or not…?
|
|
Josh
|
July 20, 2017 at 5:08 pm
They’re your tables, but yes esp_answer is a table that Event Espresso adds. The table that stores the calendar options is the wp_options table. When you go to save the calendar options page are there any mysql errors logged on the server?
|
