aimeewarnock
Forum Replies Created
-
Thanks Harish, sorry I ended up using a different plugin as I’m on a tight timeframe with getting the page finished for my client.
Forum: Fixing WordPress
In reply to: High CPU Load After Update to v4.3I am so thankful I came across this thread, I just had a white screen after updating the Woocommerce plugin on the latest version of WP (V4.3) (on the latest version of the Divi by Elegant Themes theme).
I’ve just tried this fix and I can confirm it worked a treat for me – I’ve reactivated the updated Woocommerce plugin and everything is working all A ok now.
Thank you so much to the person that came up with this fix, I can’t thank you enough!!!!
Forum: Plugins
In reply to: [WooCommerce] Dashboard broken after updating Woocommerce plugin – help!Hey Stephan & Mike, back again!
SOLVED (by me!) – there is actually a bug in the WordPress V4.3 update that is causing high CPU load. I just tried the bug fix that is given in a wordpress.org support forum thread and it worked – I’ve reactivated Woocommerce plugin (latest version) and everything is working A ok again! Sheesh, WordPress, what are you doing to me!!
I can confirm that the fix in this wordpress .org support forum thread works (while we are waiting for the next WordPress update which will include the bug fix): https://wordpress.org/support/topic/high-cpu-load-after-update-to-v43?replies=17#post-7330770
Forum: Plugins
In reply to: [WooCommerce] Dashboard broken after updating Woocommerce plugin – help!Thanks Mike and Stephan – after enabling WP_DEBUG I discovered it was the PHP memory limit exceeded (as I’m on shared hosting with Hostgator and they limit PHP memory to max 256M):
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 4751196 bytes) in /home3/laiyee/public_html/wp-includes/functions.php on line 384
However, increasing PHP memory to 256M in the wp_config file doesn’t help.
I believe I had heard there is a bug in the latest version of WP that causes unnecessary strain on the server, so I’m not sure if that’s my problem. I might try to roll back to an older version of WP.