mintynz

Excellent – thanks @pebblo ! Hopefully this makes things better for everyone ??

Hey @pebblo , quick update in case it’s useful:

• Used the excellent “Better Search Replace” plugin to replace all database instances of the subdirectory.
• Moved the files to hosting root with Siteground’s file manager
• EE 5.0.24 now works fine… no graphql error

Hope that helps with sorting other people dealing with similar issues!

Really appreciate the response, Tony. I am going to try and move it to the root folder (I didn’t do the original site setup, which was many many years ago) and will report back on that.

The result of the support request was that gMail does indeed ignore the “Force Email/Name” checkboxes in the Yay SMTP settings.

I have suggested a small note is added to those settings so users are aware that they won’t work with gMail.

Marking as ‘resolved’.

Hi Mia, thanks for the quick reply. I’ve asked my question there. If I get an answer, I’ll post it here for others to see.

Followup: Cron jobs in Diagnostics all show fine and the wfTrafficRates entry is now tiny.

Success!

Hey @wfphil , thanks for the comprehensive answer. The clarification on what ” Delete all Live Traffic Data” actually does is very useful.

I do indeed have define(‘DISABLE_WP_CRON’, true) to improve WP performance, with a cron job set via Cpanel to run every minute instead.

But checking the Diagnostics tab (thanks for pointing me to that!) I can see the jobs are all overdue.

I’ve set define(‘DISABLE_WP_CRON’, false) and will see what happens, and will do further investigating as to why the Cpanel Cron job was not firing properly.

Many thanks.

Hey @sachser19640628 that certainly looks like an error in the Enfold theme:

“wp-content/themes/enfold/config-woocommerce/config.php”

I can’t see any mention of the WooCommerce Sequential Order Numbers theme in your error log. And I can’t see it in your plugin list. Are you sure you’re in the right place?

Ps. You may want to trim the error listings to start at /wp-content … it may expose too much info about your website setup to have the full path as you have.

@tamarazuk I’ve logged back in and updated Woo again from 4.3 to 4.3.1… and now I’m not getting any errors.

I have not changed anything else at all.

I’m wondering if it was a flawed Woocommerce update… that perhaps one or two files didn’t write out properly, which ended up presenting as “undefined is_ajax() in woocommerce-sequential-order-numbers”.

@sachser19640628 does rolling back to WC4.3 and then reinstalling 4.3.1 solve things for you?

@tamarazuk Apologies for the mislead on this, but again, I do appreciate the prompt and thoughtful responses.

Hey @tamarazuk – thanks for the quick response. It’s encouraging.

I need to find some space to do those steps.

In the meantime: @sachser19640628 I’m using the Divi theme, and the following plugins. Does any of it look similar to your setup?

—–
InfiniteWP – Client
BackupBuddy
iThemes Security
Classic Editor
Format Media Titles
Forminator Pro
Really Simple SSL pro
WooCommerce Payment Express Gateway
WooCommerce Sequential Order Numbers
WooCommerce TM Extra Product Options
Wordfence Security
Yoast SEO
WP Mail Logging
WP Rocket
Smush Pro
WPMU DEV Dashboard

So the mistake is all my fault.

Haha… easy tiger! I did actually look at that exact thing and thought “Oh, maybe filter hooks work differently to action hooks”, so it was easily my fault for not backing myself!

Really appreciate the quick response, and I’m just happy to help with tweaking things that will make it better for everyone in the future ??

That seems to have sorted it!

You might need to update the code here that I based it on – I think both examples under FILTER HOOKS need tweaking ??

https://github.com/methnen/m-chart/wiki/Action-and-filter-hooks#m_chart_chart_args

@methnen Currently using Highcharts.

I wish more developers would apologise for taking a whole 5 hours to update a plugin to fix a bug!

All sorted- it’s working well now.
Many thanks!

@bykastar this was precisely my issue. I’ve just checked though and it does, appeared to be fixed with the recent 1.9.2 update (even though it’s not mentioned in the changelog).

Have you updated to that version? (I’m using the pro version, but hopefully the free one has the same code patch…)