[Emily Tarrant]

Thanks Cliff. I’ll do the updating and then see what it tells me. I’ll let you know what I find out!
Cheers, Emily

[Emily Tarrant]

Hi Chris

Thanks for your continued help with this. I’m having a go with the debug options.

With the query monitor plugin disabled I get just one error:
[10-Jul-2018 07:35:07 UTC] PHP Notice: automatic_feed_links is deprecated since version 3.0.0! Use add_theme_support( ‘automatic-feed-links’ ) instead. in /home/sites/lrmdev.co.uk/public_html/lrm1806/lrm/wp-includes/functions.php on line 3840

I’m due to do a round of updating (including to WP 4.9.7) so I’ll do that and see if that solves that particular error.

But when I turn on query monitor and go to the events admin page I start getting a bunch of memory errors. Here are the last few lines:
[10-Jul-2018 07:36:22 UTC] PHP Fatal error: Out of memory (allocated 163577856) (tried to allocate 2097152 bytes) in /home/sites/lrmdev.co.uk/public_html/lrm1806/lrm/wp-content/plugins/query-monitor/output/html/db_queries.php on line 377
[10-Jul-2018 07:36:29 UTC] PHP Notice: automatic_feed_links is deprecated since version 3.0.0! Use add_theme_support( ‘automatic-feed-links’ ) instead. in /home/sites/lrmdev.co.uk/public_html/lrm1806/lrm/wp-includes/functions.php on line 3840
[10-Jul-2018 07:36:40 UTC] PHP Fatal error: Out of memory (allocated 163577856) (tried to allocate 671744 bytes) in /home/sites/lrmdev.co.uk/public_html/lrm1806/lrm/wp-content/plugins/query-monitor/output/html/db_queries.php on line 386
[10-Jul-2018 07:36:40 UTC] PHP Fatal error: Out of memory (allocated 163577856) (tried to allocate 655360 bytes) in Unknown on line 0

I’ve already got the memory limit quite high, should I increase it more or is there something else I should be looking at?

Cheers, Emily

[Emily Tarrant]

Hi Cliff

I’ve checked the memory settings on the site and have already got it set to 512 – that sounds like it should be plenty doesn’t it?

I’ve installed Query Monitor on a dev copy of the site and if I go to the wp-admin Events page I just get a blank page. That doesn’t seem good does it? Do you know why that might happen?

Cheers, Emily

[Emily Tarrant]

Thanks Cliff, I’ll have a go with the query monitor and review the memory settings.

Can I leave this ticket open for the moment and come back to you when I’ve done some testing?

Cheers, Emily

[Emily Tarrant]

Thanks Cliff

Yes, we’re on PHP 7 at the moment – this is the highest that our web hosts (Heart Internet) are currently offering.

Do you have a recommendation as to what the best memory setting is? And any tips on cleaning up the database? I’m not expecting you to do the work for me (I’m not that cheeky!), but if you’re able to point me in the direction of some info I can work through that would be brilliant.

The site has currently got:
Posts: 110
Pages: 36
Collections (custom post type): 24
Articles (custom post type): 50

These all load without a problem, it’s the events that are particularly slow loading.

Cheers, Emily

[Emily Tarrant]

Thanks Cliff, the events go from June 2017 to December 2018. I’ve been clearing past events manually, but I see from the link you’ve given that there are some settings to automate that. I’ve set it to:
move to trash after 3 months
permanently delete after 1 yr

This has reduced the number of published events quite a bit (it’s now showing as 298 published). But loading events in the backend is still really slow.

The advice about how many events to display I’ve already applied (no more than 3 events showing per day etc), but this is really about speeding up the front end isn’t it? What we’re really struggling with is how long it’s taking to load in the back end.

Can you suggest anything else I can look at?

Thanks for your help with this, I really appreciate it!
Best wishes, Emily

[Emily Tarrant]

Hi Victor

Thanks for your advice, that’s really helpful. I’ve started by asking here as you may have said ‘use this plugin’ or ‘try this setting’. I’ll now do some digging to see what I can do. Deleting old events might be a good start, but maybe with leaving the tickets in place as you suggest. And I know there are some actions I can take to help optimise the WooCommerce tables. Hopefully with a combination of things I can get the database a bit tidier!

Thanks again, Emily

[Emily Tarrant]

Thanks for your reply Victor. And thanks for suggesting the Force Sells plugin, that’s really useful. I’ll have a look and see if it will work for us.

Cheers, Emily

[Emily Tarrant]

Thanks Cliff, much appreciated.

[Emily Tarrant]

Thanks Cliff, is there a particular server limitation that I should enquire about?

[Emily Tarrant]

Hi Cliff

That’s worked! What a relief!!

Is there anything that I should be aware of with using this fix?

Cheers, Emily

[Emily Tarrant]

Hi Cliff

I can confirm that I have installed and activated the cleanup tool and it didn’t display any recurring events.

So, from what I can see there is nothing for me to clean up using the tool. I’ve attached a screenshot of the tools so that you can check I’ve understood this correctly.

Many thanks, Emily

[Emily Tarrant]

Hi Cliff

I’ve made sure that the site is completely up-to-date – WordPress core and all plugins.

I’ve also had a look at the Recurring Event Cleanup Tool but I’m not using any recurring events – all events are entered individually as one-offs.

So, unfortunately that’s not my issue. Can you suggest anything else for me to look at?

Cheers, Emily

[Emily Tarrant]

Hi Cliff

I’ve tried resetting the debug file and this is what I’m finding:
Theme: Twenty Sixteen
Plugins Activated: The Events Calendar and The Events Calendar PRO – all other plugins deactivated

When I go to the widgets page I get the following error in the log:
[06-Jan-2017 14:12:47 UTC] PHP Fatal error: Out of memory (allocated 182452224) (tried to allocate 32 bytes) in [REMOVED]/wp-includes/wp-db.php on line 2416

I only get this memory error if these two plugins are enabled. If I disable them and enable everything else it’s fine.

Cheers, Emily

[Emily Tarrant]

Hi Cliff. Happy New Year! Thanks for your advice. I will do what you say and see what the debug says. I’ll let you know what I find out.
Cheers, Emily

[Author]

Posts