|
Tristan Mills
|
November 19, 2014 at 2:15 pm
When I add 20-30 datetimes to an event the database query or update time gets so long that the page times out if I try to make any more changes and hit ‘Update’ again, in fact the admin event page won’t even load now as it takes so long to load. It is going over 120 seconds. In addition the front end event page for that event also starts taking ages to load, e.g. over 30 seconds. Before adding the datetimes the pages were coming up almost immediately [ie normally]. I have lots of wordpress sites running on this platform and havent had problems like this with them.
Has the system been tested with having lots of datetimes for an event like this and is this a problem you are aware of?
message: Fatal error: Maximum execution time of 120 seconds exceeded in D:\html\wp-content\plugins\event-espresso-core-reg\core\db_models\fields\EE_Model_Field_Base.php on line 34
it seems to me that mysql is getting swamped with queries or they are just too complex.
|
|
Tristan Mills
|
November 19, 2014 at 3:10 pm
i have replicated this on test drive by adding about 30 datetimes and tickets and the event admin page will not load now
here
|
|
Lorenzo Orlando Caum
|
November 19, 2014 at 3:26 pm
Hi,
The ticket selector needs to retrieve those from the database. It wasn’t designed to have a large number of ticket options and this will cause registration to run slowly.
First, raise the memory that is available to PHP:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
Then raise max input vars:
http://diywpblog.com/how-to-increase-max-input-vars/
—
Lorenzo
|
|
Tristan Mills
|
November 19, 2014 at 4:38 pm
Hi,
Those changes haven’t really made any difference, I guess the thing to do is abandon the datetimes method as there are so many recurrences of the event and create duplicate events [pages] instead, only using datetimes sparingly e.g. when 2 sessions per day. The event is identical apart from date and time though so it seems long winded to be going through the process of duplicating the event (page) and setting options for each rather than 1 page where you could just enter the dates to run it on, ideally creating a datetime and ticket would be one and the same thing.
That’s just how it would suit us at the moment, you are catering for many different types of usage. Finding v.4 very WP friendly with templating and hooks etc, it’s very easy and logical to work with if you know WP 🙂 Great job!
|
|
Tony
|
November 20, 2014 at 3:28 am
Hi Tristan,
Thank you for the feedback, it is always appreciated 🙂
It sounds like you need functionality similar to the EE3 Recurring Events Manager (REM) for EE4 which is something we have on our roadmap.
Currently it is in very early stages of development so not yet ready to release or test, however once release it should help make EE4 suit your event type a little better.
|
