I also have had problems with the update to 2.4.6 and have consulted with iPage WordPress support who found that the WooCommerce plug-in crashes the site (but no message generated). We rolled it back to yesterday’s version, 2.4.5 which is fine, but reporting here (and see I am not the only one).
Using WP v. 4.3 with a child theme of CustomizrPro (v.1.2.4, I think).
Any help on what might be the cause of the website crashing on this update would be appreciated.
If you need the website URL, contact me at [email protected] and will send it by private message.
I’m also having an error since the update but to be fair my site still in development and I had been unable to test the cart b4 the upgrade. the site is on a subdomain at . this is the error and you can see i’ve enable wp-debug and do have more than $100 (the min order) in the cart
Checkout
Customer matched shipping zone Domestic (#1)
Have a coupon? Click here to enter your code
You must have an order with a minimum of $100.00 to place your order, your current order total is $0.00.
Customer matched shipping zone Domestic (#1)
Billing Details
First Name *
Last Name *
Company Name
Email Address *
Phone *
Country *
Country *
Address *
Town / City *
State *
State *
Zip *
Ship to a different address?
First Name *
Last Name *
Company Name
Country *
Country *
Address *
Town / City *
State *
State *
Zip *
Order Notes
Your order
Product Total
Multi Walled Carbon Nanotubes 8-15nm × 15 $112.50
Subtotal $112.50
Shipping 1-99: $25.00
Total $137.50
Not sure if it help any of you, but the issue I had that crashed my site was the update screwed up my .htaccess file and I had to re-write it. That got rid of the 500 Server Error, but still the MYSQL Error shown above exists and I’m wondering why???
@thefactory updated from which version?
@thefactory About error should not appear, because we use:
https://codex.ww.wp.xz.cn/Class_Reference/wpdb#Show_and_Hide_SQL_Errors
The code in question attempts to update the database if it’s not possible (eg: It has been previously updated) will return an error (which should not appear).
Perhaps you’ve seen this error in the log of your server, but it has no link with error 500 as you yourself said.
🙂
That is correct, but the update did in fact screw up my .htaccess file causing 500 internal server error. I updated from the previous version. I always keep the latest updates on out site. Yes, the error was retrieved from my error_log in apache.
@thefactory This is strange because we don’t try manipulate the .htaccess.
We create .htaccess files in wp-content/uploads/wp-logs and wp-content/uploads/woocommerce_uploads. But never change anything the main site .htaccess.
Hello, I posted earlier in this thread having a 500 internal server error which only went away when we deactivated the WooCommerce v. 2.4.6. that I was in the process of updating. It happened twice. No server errors in the iPage CGI logs at their end. A third person had a problem on a staging server.
I am not hearing that anything is happening to investigate why I and @thefactory had this experience, only that it is not supposed to happen. Can we get an action item here that gets us to a solution, please?
Thank you.
