|
Matt
|
October 30, 2015 at 4:55 am
Event Espresso when it is enabled is stopping the checkout functionality of my woocommerce from working? Please advise? I have tested all other plugins but as soon as I enable EE it breaks it?
|
|
Josh
|
October 30, 2015 at 5:51 am
Hi Matt,
Can you describe what exactly is happening? Also, does your site have https and is force https set in the WooCommerce options? If you give us more specific details it will help us investigate.
|
|
Matt
|
October 30, 2015 at 4:24 pm
Hi Josh,
If I enable EE, the checkout page where the payment section is just has a little black circle with white dots that continously spins.
Yes our site is https:// and yes woocommerce is set to force it. We are using the theme BETHEME and everything is error free in woocommerce etc. It is only when we enable EE it breaks things.
|
|
Josh
|
October 31, 2015 at 11:36 am
Can you check the browser console for JavaScript errors on the checkout page?
|
|
Matt
|
November 3, 2015 at 11:39 am
Hi Josh,
Mixed Content: The page at ‘https://www.matthudson.com/checkout/’ was loaded over HTTPS, but requested an insecure image ‘http://www.matthudson.com/wp-content/uploads/2014/03/logo.jpg’. This content should also be served over HTTPS.
Mixed Content: The page at ‘https://www.matthudson.com/checkout/’ was loaded over HTTPS, but requested an insecure image ‘http://www.matthudson.com/wp-content/uploads/2014/10/bannerupdated10.jpg’. This content should also be served over HTTPS.
Mixed Content: The page at ‘https://www.matthudson.com/checkout/’ was loaded over HTTPS, but requested an insecure image ‘http://www.matthudson.com/wp-content/uploads/2014/03/logo.jpg’. This content should also be served over HTTPS.
Mixed Content: The page at ‘https://www.matthudson.com/checkout/’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘http://www.matthudson.com/wp-content/uploads/2014/03/logo@2x.jpg’. This request has been blocked; the content must be served over HTTPS.
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Failed to load resource: the server responded with a status of 404 (Not Found)
Errors that are showing?
|
|
Josh
|
November 3, 2015 at 12:28 pm
Those are mixed content errors and not found errors, which usually is the result of the theme using http instead of allowing WP to set http or https. Most likely unrelated.
One thing to consider is the amount of memory available to WordPress on your site. What can happen is if the server is already close to running low on memory, then you activate a plugin like Event Espresso (or any other plugin) that requires a good chunk of memory, then you can run into Memory Exhausted errors, which may be resulting in that little black circle with the dots that spin.
So to fix, you increase the amount of memory available to WordPress so it has enough memory by following this guide:
http://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory/
|
|
Matt
|
November 3, 2015 at 12:40 pm
Hi Josh.
I have increased the memory to 92mb. It still spins? Are you saying I need to increase the memory even more?
|
|
Matt
|
November 3, 2015 at 12:42 pm
I have just increased to 254mb. Still not working.
|
|
Josh
|
November 3, 2015 at 12:55 pm
Nope, I did not say you’d need to increase it to more. The guide that I shared a link with you says that if the memory bump doesn’t help, you can contact your host to see if they can go into their php.ini file to increase the memory limit for you.
|
|
Matt
|
November 3, 2015 at 12:56 pm
Hi Josh, I have done both. It is my own dedicated server. This error hasn’t occured in the past. Just the latest updates has messed it up.
|
|
Josh
|
November 3, 2015 at 1:11 pm
Have you checked the PHP error logs since the latest update?
|
|
Matt
|
November 4, 2015 at 8:44 am
[04-Nov-2015 16:21:21 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
[04-Nov-2015 16:21:21 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
[04-Nov-2015 16:24:17 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
[04-Nov-2015 16:29:31 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
[04-Nov-2015 16:32:51 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
[04-Nov-2015 16:32:52 Europe/Berlin] PHP Warning: Module ‘zip’ already loaded in Unknown on line 0
Nothing else other than that. Which I don’t think is related as this has been a consistent error since August 2014 lol!
|
|
Josh
|
November 4, 2015 at 12:38 pm
Can you find out which version of PHP you have running on your server? This information will help us investigate.
|
|
Matt
|
November 4, 2015 at 4:15 pm
5.6 is the version.
|
|
Josh
|
November 4, 2015 at 7:05 pm
Can you turn on WP_DEBUG and check for errors? Also, when the WooCommerce checkout fails, is it when the Place Order button is submitted or at another point? Do you have a test site set up so we can investigate? I have a test site set up with Event Espresso 4 and WooCommerce and orders are going through as expected, so if you can clone your live site to a dev site (ideally on the same server) that will help us troubleshoot.
|
|
Matt
|
November 5, 2015 at 2:51 am
Hi Josh,
With WP_DEBUG:
Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/matthud/public_html/wp-includes/functions.php on line 3457
Warning: Cannot modify header information – headers already sent by (output started at /home/matthud/public_html/wp-includes/functions.php:3457) in /home/matthud/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 112
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/matthud/public_html/wp-includes/functions.php:3457) in /home/matthud/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398
I can’t setup a test site. We don’t mind you working on the live site. We just want it up and running. 6 days now.
|
|
Josh
|
November 5, 2015 at 7:29 am
Hi Matt,
The first notice in that list is likely causing those session start warnings. Can you try a theme like twentyfifteen, or fix the theme so its Widget does not use the deprecated constructor method? If the theme’s widget code is up to date, you’ll need to check for plugins that register widgets and update their code.
There’s more information about how to update the theme’s widget code in these articles:
https://make.wordpress.org/core/2015/07/02/deprecating-php4-style-constructors-in-wordpress-4-3/
https://gist.github.com/chriscct7/d7d077afb01011b1839d
|
|
Matt
|
November 6, 2015 at 1:34 pm
Its not that. I have tried it on the default wordpress themes and still doesn’t work.
Please advise. We need this fixed.
|
|
Josh
|
November 6, 2015 at 1:58 pm
Do you get the cannot modify header warnings with the default theme active?
|
|
Matt
|
November 9, 2015 at 5:16 am
otice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /home/matthud/public_html/wp-includes/functions.php on line 3457
Warning: Cannot modify header information – headers already sent by (output started at /home/matthud/public_html/wp-includes/functions.php:3457) in /home/matthud/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 112
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/matthud/public_html/wp-includes/functions.php:3457) in /home/matthud/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 398
What I see on default WP theme install.
|
|
Josh
|
November 9, 2015 at 8:15 am
This means there’s a plugin that’s throwing the deprecated notice when it registers its widget. To fix, you can update that plugin so it’s using the supported Widget constructor.
If you do not update/fix the plugin, it may work to force disable the error display by adding this to the wp-config.php file:
@ini_set( 'display_errors', 0 );
|
|
Matt
|
November 9, 2015 at 10:05 pm
Josh, How does this effect it? I basically need the checkout working and at present it doesn’t work if EE is enabled.
|
|
Josh
|
November 10, 2015 at 8:09 am
Here’s some basic info on the Headers already sent warning problem:
https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
On your site, the “Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0!” is triggering the headers already sent warnings. It’s a domino effect, where Event Espresso is one of the dominos in the middle.
Here’s a quick video that shows a plugin that has the deprecated widget code, its effect on WooCommerce checkout, and how to update the widget plugin code to fix the issue:
http://screencast.com/t/WttlIFWM4u
|
