Latest WooCommerce update (3.0.2) gives problems on checkout and cart pages

Hey Support, I am having the same issues as everyone else. In my case the product will add to the cart. However, users cannot properly remove items from the cart. Please help asap. I am in the final stages of my website completion and this is my biggest hurdle. Thank you for your assistance.

Hi,

We are sorry for the issue. Our developers are investigating it now, hope that it will be fixed soon.

Sincerely,
Hella

I also have this issue and now I have upset clients that are losing money. I can confirm that it is not working on the product page but I can add items to the basket from the main shop page on simple items.

Just to add I've found a work around in that turning off "Enable AJAX add to basket buttons on archives" in the Woocommerce settings allows products to be added to the basket from within the product page again.

Change the settings here: https://YOURWEBSITE.COM/wp-admin/admin.php?page=wc-settings&tab=products&section=display

Just to add I've found a work around in that turning off "Enable AJAX add to basket buttons on archives" in the Woocommerce settings allows products to be added to the basket from within the product page again.

Change the settings here: https://YOURWEBSITE.COM/wp-admin/admin.php?page=wc-settings&tab=products&section=display

Thanks Bijoubyte! This is a nice work around. Still we look forward in a permanent fix. :)

Sorry scrap that idea, it worked for a few items before posting about it here but then I went back to test other stuff and it is no longer working, I have no odea whatsoever why and as this is on a work in progress website there isn't any caching plugins at the minute either.

Sorry scrap that idea, it worked for a few items before posting about it here but then I went back to test other stuff and it is no longer working, I have no odea whatsoever why and as this is on a work in progress website there isn't any caching plugins at the minute either.

Okay, too bad.

I think the devs from Themler just need to update the outdated template files for WooCommerce. The 3.0.2 update has some serious changes.

I installed the Wp Rollback plugin on my WIP website and it rolledback Woocommerce to v2.16.14 however it did give several warnings about possible database errors and I'm reluctant to use that on clients live sites.

I enabled debugging previous to this step and all I can say is what a mess! Here are some of the debug errors from WC 3.0.1:

Header:
Notice: get_product is deprecated since version 3.0! Use wc_get_product instead. in /home/yummybubbles/public_html/wp-includes/functions.php on line 3829

Notice: post was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/yummybubbles/public_html/wp-includes/functions.php on line 4137

Notice: post was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/yummybubbles/public_html/wp-includes/functions.php on line 4137

Notice: WC_Product::get_gallery_attachment_ids is deprecated since version 3.0! Use WC_Product::get_gallery_image_ids instead. in /home/yummybubbles/public_html/wp-includes/functions.php on line 3829

Sidebar:
Notice: get_product is deprecated since version 3.0! Use wc_get_product instead. in /home/yummybubbles/public_html/wp-includes/functions.php on line 3829

Notice: WC_Product::get_related is deprecated since version 3.0! Use wc_get_related_products instead. in /home/yummybubbles/public_html/wp-includes/functions.php on line 3829

Notice: id was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/yummybubbles/public_html/wp-includes/functions.php on line 4137

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 137

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 141

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 145

Product thumbnail gallery:
Notice: WC_Product::get_gallery_attachment_ids is deprecated since version 3.0! Use WC_Product::get_gallery_image_ids instead. in /home/yummybubbles/public_html/wp-includes/functions.php on line 3829

Between short description and add to basket:
Notice: product_type was called incorrectly. Product properties should not be accessed directly. Please see Debugging in WordPress for more information. (This message was added in version 3.0.) in /home/yummybubbles/public_html/wp-includes/functions.php on line 4137

Recently Viewed Widget:
Notice: Undefined variable: _SESSION in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 439

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 137

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 141

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 145

Featured Products sidebar:

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 137

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 141

Warning: A non-numeric value encountered in /home/yummybubbles/public_html/wp-content/themes/Soapaddict_01/includes/products_slider_widgets_1.php on line 145

The widget debug errors persist even after downgrading Woocommerce so I decided to do a theme check and got this long line:

WARNING: file_get_contents was found in the file export.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 518: $content = file_get_contents($path);
Line 737: $content = file_get_contents($file);
Line 1056: $files[$name] = file_get_contents($path);
Line 1153: $result = array('result' => 'done', 'data' => base64_encode(file_get_contents($zip_file)));
Line 1312: fwrite($file, file_get_contents($_FILES['chunk']['tmp_name']));
WARNING: file_get_contents was found in the file editorHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 186: $hashes_content = file_exists($hashesfile) ? file_get_contents($hashesfile) : '';
Line 217: $cache = file_exists($cachefile) ? file_get_contents($cachefile) : '';
Line 256: $content = file_get_contents($projectfile);
Line 344: $version = file_get_contents($theme->get_template_directory() . '/export/manifest.vers
Line 381: $manifest = file_get_contents('$manifests_dir/$version.manifest');
Line 432: $changed_files_file_content = file_get_contents($changed_files_file);
Line 554: if (file_exists($lock_file) && ($instanceId = file_get_contents($lock_file)) !== $_REQUEST['instanceId']) {
WARNING: file_get_contents was found in the file content-importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 65: $data = file_get_contents($json_path);
WARNING: file_get_contents was found in the file archive.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 9: 'content' => base64_encode(file_get_contents($archive_file))
WARNING: file_get_contents was found in the file PreviewHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 16: $data_attributes_diff_content = file_exists($data_attributes_diff_file) ? file_get_contents($data_attributes_diff_file) : '{}';
Line 31: $content = file_get_contents($path);
Line 70: $content = file_get_contents($path);
WARNING: file_get_contents was found in the file Chunk.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 70: $chunk = file_get_contents($this->_chunkFolder . '/$i');
Line 105: $result = @file_get_contents($result_path . '/data');
Line 199: fwrite($file, file_get_contents($_FILES['chunk']['tmp_name']));
WARNING: fclose was found in the file importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 170: fclose($f);
WARNING: fclose was found in the file export.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 1315: fclose($file);
Line 1480: fclose($file);
WARNING: fclose was found in the file editorHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 293: fclose($handle);
Line 325: fclose($handle);
WARNING: fclose was found in the file Chunk.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 201: fclose($file);
REQUIRED: You are not allowed to hide the admin bar.
REQUIRED: The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output
REQUIRED: importer.php. Themes should use add_theme_page() for adding admin pages.
Line 26: add_submenu_page($menu_slug, ('Settings', 'default'), __('Settings', 'def
Line 27: add_submenu_page($menu_slug, __('Import', 'default'), __('Import', 'default
Line 28: add_submenu_page($menu_slug, __('Export', 'default'), __('Export', 'default
REQUIRED: importer.php. Themes should use add_theme_page() for adding admin pages.
Line 24: add_menu_page(('Themler tools', 'default'), __('Themler tools', 'default'
REQUIRED: bloginfo("template_url") was found in the file export.php. Use echo esc_url( get_template_directory_uri() ) instead.
Line 740: $old_path = '<?php bloginfo('template_url')?>/images/' . theme_get_image_name($key);
REQUIRED: Zip file found. Plugins are not allowed in themes. The zip file found was themler-core.zip.
RECOMMENDED: Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.
RECOMMENDED: No reference to add_theme_support( "custom-header", $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: No reference to add_theme_support( "custom-background", $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality.
RECOMMENDED: No reference to add_editor_style() was found in the theme. It is recommended that the theme implement editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience.
RECOMMENDED: preview_theme_ob_filter() found in the file functions.php. Deprecated since version 4.3.
Line 1155: if (!function_exists('preview_theme_ob_filter'))
Line 1158: return preview_theme_ob_filter($test_data) === $test_data;
Line 1163: function theme_preview_theme_ob_filter($content) {
Line 1164: return preg_replace_callback('|(<a.?href)(=[\''])(.?)([\''].*?>)|', 'theme_preview_theme_ob_filter_callback', $content);
Line 1166: function theme_preview_theme_ob_filter_callback($matches) {
Line 1169: ob_start('theme_preview_theme_ob_filter');

Part 2 as list was too long:

WARNING: file_get_contents was found in the file export.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 518: $content = file_get_contents($path);
Line 737: $content = file_get_contents($file);
Line 1056: $files[$name] = file_get_contents($path);
Line 1153: $result = array('result' => 'done', 'data' => base64_encode(file_get_contents($zip_file)));
Line 1312: fwrite($file, file_get_contents($_FILES['chunk']['tmp_name']));
WARNING: file_get_contents was found in the file editorHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 186: $hashes_content = file_exists($hashesfile) ? file_get_contents($hashesfile) : '';
Line 217: $cache = file_exists($cachefile) ? file_get_contents($cachefile) : '';
Line 256: $content = file_get_contents($projectfile);
Line 344: $version = file_get_contents($theme->get_template_directory() . '/export/manifest.vers
Line 381: $manifest = file_get_contents('$manifests_dir/$version.manifest');
Line 432: $changed_files_file_content = file_get_contents($changed_files_file);
Line 554: if (file_exists($lock_file) && ($instanceId = file_get_contents($lock_file)) !== $_REQUEST['instanceId']) {
WARNING: file_get_contents was found in the file content-importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 65: $data = file_get_contents($json_path);
WARNING: file_get_contents was found in the file archive.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 9: 'content' => base64_encode(file_get_contents($archive_file))
WARNING: file_get_contents was found in the file PreviewHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 16: $data_attributes_diff_content = file_exists($data_attributes_diff_file) ? file_get_contents($data_attributes_diff_file) : '{}';
Line 31: $content = file_get_contents($path);
Line 70: $content = file_get_contents($path);
WARNING: file_get_contents was found in the file Chunk.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 70: $chunk = file_get_contents($this->_chunkFolder . '/$i');
Line 105: $result = @file_get_contents($result_path . '/data');
Line 199: fwrite($file, file_get_contents($_FILES['chunk']['tmp_name']));
WARNING: fclose was found in the file importer.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 170: fclose($f);
WARNING: fclose was found in the file export.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 1315: fclose($file);
Line 1480: fclose($file);
WARNING: fclose was found in the file editorHelper.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 293: fclose($handle);
Line 325: fclose($handle);
WARNING: fclose was found in the file Chunk.php File operations should use the WP_Filesystem methods instead of direct PHP filesystem calls.
Line 201: fclose($file);
REQUIRED: You are not allowed to hide the admin bar.
REQUIRED: The <title> tags can only contain a call to wp_title(). Use the wp_title filter to modify the output
REQUIRED: importer.php. Themes should use add_theme_page() for adding admin pages.
Line 26: add_submenu_page($menu_slug, ('Settings', 'default'), __('Settings', 'def
Line 27: add_submenu_page($menu_slug, __('Import', 'default'), __('Import', 'default
Line 28: add_submenu_page($menu_slug, __('Export', 'default'), __('Export', 'default
REQUIRED: importer.php. Themes should use add_theme_page() for adding admin pages.
Line 24: add_menu_page(('Themler tools', 'default'), __('Themler tools', 'default'
REQUIRED: bloginfo("template_url") was found in the file export.php. Use echo esc_url( get_template_directory_uri() ) instead.
Line 740: $old_path = '<?php bloginfo('template_url')?>/images/' . theme_get_image_name($key);
REQUIRED: Zip file found. Plugins are not allowed in themes. The zip file found was themler-core.zip.
RECOMMENDED: Screenshot size should be 1200x900, to account for HiDPI displays. Any 4:3 image size is acceptable, but 1200x900 is preferred.
RECOMMENDED: No reference to add_theme_support( "custom-header", $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: No reference to add_theme_support( "custom-background", $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality.
RECOMMENDED: No reference to add_editor_style() was found in the theme. It is recommended that the theme implement editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience.
RECOMMENDED: preview_theme_ob_filter() found in the file functions.php. Deprecated since version 4.3.
Line 1155: if (!function_exists('preview_theme_ob_filter'))
Line 1158: return preview_theme_ob_filter($test_data) === $test_data;
Line 1163: function theme_preview_theme_ob_filter($content) {
Line 1164: return preg_replace_callback('|(<a.?href)(=[\''])(.?)([\''].*?>)|', 'theme_preview_theme_ob_filter_callback', $content);
Line 1166: function theme_preview_theme_ob_filter_callback($matches) {
Line 1169: ob_start('theme_preview_theme_ob_filter');

Also I've checked the existing Artisteer with Tuxedo Woocommerce sites and they are fine with the WC update.

Also I've checked the existing Artisteer with Tuxedo Woocommerce sites and they are fine with the WC update.

Yes, it's really the old template files which I pointed out in my first post.

Same here.
I am using the Woocommerce Product Add-ons plugin, this is a genuine Woocommerce plugin.
Wordpress 4.7.3, Woocommerce 3.0.1

For a simple product with no add-ons, it will add to the cart.
For a product with add-ons, it does not add to the cart.

I have warnings that the following theme files are out of date:

SDA21/woocommerce/archive-product.php,
SDA21/woocommerce/cart/cart.php version 2.3.8 is out of date. The core version is 3.0.0,
SDA21/woocommerce/loop/result-count.php version 2.0.0 is out of date. The core version is 3.0.0,
SDA21/woocommerce/loop/sale-flash.php,
SDA21/woocommerce/notices/error.php,
SDA21/woocommerce/notices/notice.php,
SDA21/woocommerce/notices/success.php,
SDA21/product-searchform.php version - is out of date. The core version is 2.5.0,
SDA21/woocommerce/single-product.php

My customer is loosing money on a daily basis

This is urgent, can a fix be delivered urgently please, hours not days please.

Thanks

Agreed. This is really bad. I reverted back to 2.6.14 of WooCormmerce for now.

My customer is loosing money on a daily basis

This is urgent, can a fix be delivered urgently please, hours not days please.

I strongly agree, I too have now used the rollback plugin (fingers crossed everything looks ok at the mo) BUT this cannot carry on for long because as plugins for Woocommerce get updated that may break functionality with the older version of WC as well as security implications if there are any updates needed to plug security holes and this on platforms that handle customers money on a daily basis is a must!

The beta for Wordpress and Woocommerce is open to all so surely a company that is selling software that creates templates and themes for said platform should be proactively keeping up with the development and making sure that their software still functions for paying customers without breaking their clients websites!

We need to know that they are actively working on a fix and treating it as a priority or else I will be forced to start migrating clients away from Themeler themes and instead look into a subscription to one of the theme websites.

6 days for a button so far...

Looks like a hug amount of stuff was changed Developer Migration Notes

ok, i also understand that this is urgent, but as a customer i would ask you, why the hell did you upgrade without a backup or a plan b aka a fallback scenario?

also 3.0 seems to be a major release which has released 7 days ago! so i really have to ask

this seems to be a bit crazy, going live which a 7 days old release? see https://github.com/woocommerce/woocommerce/releases for my information.

for major releases woocommerce clearly states that it is possible to break "old" themes: https://docs.woocommerce.com/document/fix-outdated-templates-woocommerce/

so it is mainly your problem and not themlers! of course a software usually does/cannot yet support a 7 days ago updated major release.

imagine, if there is a new major Windows release, is every vendor supporting the new major release after 7 days???

regards

Mike

My customer is loosing money on a daily basis

This is urgent, can a fix be delivered urgently please, hours not days please.

I strongly agree, I too have now used the rollback plugin (fingers crossed everything looks ok at the mo) BUT this cannot carry on for long because as plugins for Woocommerce get updated that may break functionality with the older version of WC as well as security implications if there are any updates needed to plug security holes and this on platforms that handle customers money on a daily basis is a must!

The beta for Wordpress and Woocommerce is open to all so surely a company that is selling software that creates templates and themes for said platform should be proactively keeping up with the development and making sure that their software still functions for paying customers without breaking their clients websites!

We need to know that they are actively working on a fix and treating it as a priority or else I will be forced to start migrating clients away from Themeler themes and instead look into a subscription to one of the theme websites.

I have the very bad feeling that Themler is definitely going the way of Artisteer not matter what they say, after all the Artisteer team kept declaring that they would continue support and development whilst they were beginning Themeler until at least a year in.

Now with their new toy in development I'm sure that all we will receive from now on are minor bug fixes and nothing from their much proclaimed wishlist.

If I sound angry that is because I am furious, I have bought a piece of software (the top level version) which cost me just a bit less for my upgrade than I pay for my yearly subscription to Adobe CC for Photoshop + Lightroom + Bridge all of which are professional level programs at the top of their game and are actively developed with top notch support. For a freelancer like myself that is a considerable chunk of change.

As for people making comments about people complaining and only being amateurs, well I suppose I could be considered one by some standards, I have serious health issues and go for very long periods of time unable to leave my house. I freelance because it is the only paying work that I can undertake. It is my only income and things like this have a massive impact on my income. I work with clients remotely, creating their websites from start to finish, every aspect of it, a lengthy time consuming job, yet I charge less than most because of my inability to network and mix with potential clients in the real world and my working at sometimes strange hours around my illness. Does this make my input any less valuable?

ok, i also understand that this is urgent, but as a customer i would ask you, why the hell did you upgrade without a backup or a plan b aka a fallback scenario?

also 3.0 seems to be a major release which has released 7 days ago! so i really have to ask

this seems to be a bit crazy, going live which a 7 days old release? see https://github.com/woocommerce/woocommerce/releases for my information.

for major releases woocommerce clearly states that it is possible to break "old" themes: https://docs.woocommerce.com/document/fix-outdated-templates-woocommerce/

so it is mainly your problem and not themlers! of course a software usually does/cannot yet support a 7 days ago updated major release.

imagine, if there is a new major Windows release, is every vendor supporting the new major release after 7 days???

regards

Mike

My customer is loosing money on a daily basis

This is urgent, can a fix be delivered urgently please, hours not days please.

I strongly agree, I too have now used the rollback plugin (fingers crossed everything looks ok at the mo) BUT this cannot carry on for long because as plugins for Woocommerce get updated that may break functionality with the older version of WC as well as security implications if there are any updates needed to plug security holes and this on platforms that handle customers money on a daily basis is a must!

The beta for Wordpress and Woocommerce is open to all so surely a company that is selling software that creates templates and themes for said platform should be proactively keeping up with the development and making sure that their software still functions for paying customers without breaking their clients websites!

We need to know that they are actively working on a fix and treating it as a priority or else I will be forced to start migrating clients away from Themeler themes and instead look into a subscription to one of the theme websites.

I have daily backups thank god of all my clients websites but chose to use the roll back plugin to prevent loss of any sales in the previous hours between backups.

In the past (many years ago) whilst just starting out I had several personal websites on various cms hacked due to not applying updates, hence I now usually keep all of my websites fully up to date. I tested the updated first on a local site but missed the add to cart button as every product on that website is a variable and that IS working.

This is down to the Themler developers not keeping abreast of Woocommerce development.