Since WooCommerce released 2.3.x there is a huge conflict with the Blanco theme (all products and product categories disappear), so I had to revert to WooCommerce 2.2.11. I have manually reverted twice via FTP to replace the plugins/woocommerce folder. However, I discover that WooCommerce has mysteriously upgraded itself to 2.3.x without anyone choosing to upgrade the plugin. I have not been able to find any setting in WooCommerce (or WooDojo) that would disable the auto upgrade.
At this point I suspect the Envato Toolkit. I’m trying to remember if I visited that page in my WP admin before each time I discovered that WC was updated. The Envato Toolkit mentions something about auto updating my theme and will make auto backup before performing upgrade. It didn’t mention anything about WC or other plugins, but perhaps it does try to be overly efficient (my theme is made for WC). I’m hesitant to browse to it now to verify specific verbiage because I don’t want to trigger an update.
Is there a solution to the fatal error?
I am running a heavily modified version of Blanco 2.9.4 and cannot simply replace it with a new release. Is there a new “content-product.php” I can install to fix the problem?
I have reverted to woocommerce 2.2.11 several times but when I log off it keeps updating automatically to 2.3.3
I discovered that WordPress is doing the WooCommerce auto update. The plugin Simple History showed me. Here’s a snippet of the details:
I never set it up to auto update WC. Quite odd…
Had to come up with quick fix, so I went with a plugin (rather than figuring out how to block WC update in wp-config). Installed “Disable Updates Manager” to block any updates to WooCommerce. It worked well and blocked the mysterious auto update to WC 2.3.x until I explicitly unblocked it and upgraded. I am able to run Blanco 3.0 with WC 2.3.3.
Regarding the heavily modified Blanco, I also have custom code and have noted which source files have modified PHP. When there’s a Blanco update, I use BeyondCompare to diff my customized PHP files against the PHP files in the new Blanco version. After I merge code where necessary, I overwrite files via FTP. Hope this tip will help you!
Hi Eva, thank you for the help. At this point you may not need to FTP and log into the site with WooCommerce issues because I have been able to upgrade to Blanco 3.0 and run WC 2.3.3. Instead, would you be able to send a link to the changes in Blanco 3.0?
You can find the information on our site: http://themeforest.net/item/blanco-responsive-wordpress-wooecommerce-theme/2755246
@roxiebaby thank you so much! That was very helpful. Hopefully things will remain stable with WC 2.2.11
Since this site was setup by a previous developer, I’m not sure there’s any way for me to update to Blanco 3.0 but hopefully that won’t be a problem.
Anyway, things seem to be working for now except for bizarre formatting of featured and recent products. Example
What page do you see that error on?
I’ve checked your site and haven’t found any issues:
Try to clear your browser cache and check again.
@eva – Thanks for the reply
I had to remove the shortcode because of the formatting but I have added a test page so you can see the issue.
The formatting problem arises with both [featured_products] and [recent_products]
I would like these pages to display just like the content on the home page.
You must be logged in to reply to this topic.Log in/Sign up
One standard license is valid only for 1 project. Running multiple projects on a single license is a copyright violation.
The message was successfully sent
Your shopping cart is empty