]]>mikejolleyFebruary 27th: Dev chat #19https://woocommerce.wordpress.com/2018/02/21/february-27th-dev-chat-19/
https://woocommerce.wordpress.com/2018/02/21/february-27th-dev-chat-19/#respondWed, 21 Feb 2018 16:38:54 +0000http://woocommerce.wordpress.com/?p=5137&ellipsis;Read the full post »]]>The next chat will be on February 27th at 17:00 UTC in the #core channel of the WooCommerce Community Slack. If you don’t already have access to the group, you can request an invite at the bottom of the WooCommerce developers page.

Here is the agenda for the chat:

The Gutenberg Products block feature plugin is now available. Get it here and test it out! We’ll do a quick overview then take feedback and first impressions.

If you have anything to propose for the agenda or related to the above, please leave a comment below.

See you there!

]]>https://woocommerce.wordpress.com/2018/02/21/february-27th-dev-chat-19/feed/0claudiulodroWooCommerce 3.3.2 fix release noteshttps://woocommerce.wordpress.com/2018/02/20/woocommerce-3-3-2-fix-release-notes/
Tue, 20 Feb 2018 17:03:12 +0000http://woocommerce.wordpress.com/?p=5131&ellipsis;Read the full post »]]>WooCommerce 3.3.2 is now available.~85 commits made it into this release. The full changelog is below.

To resolve these issues, we selected a set of the most common themes running on WooCommerce stores and then tested for compatibility with the 3.3.1 release. In addition, some theme authors have tested and released updates to ensure compatibility as well.

This has been a learning experience for us, and has highlighted problems in the extensibility of the template system, and a disconnect between our team and theme authors operating on external marketplaces. We hope to find solutions to these problems in the near future.

We’re hopeful the majority of the problems are now resolved and we can push ahead. ~90 commits made it into this release. The full changelog is below.

]]>https://woocommerce.wordpress.com/2018/02/06/woocommerce-3-3-1-fix-release-notes/feed/29mikejolleyWooCommerce 3.3.1 status updatehttps://woocommerce.wordpress.com/2018/02/01/woocommerce-3-3-1-status-update/
https://woocommerce.wordpress.com/2018/02/01/woocommerce-3-3-1-status-update/#commentsThu, 01 Feb 2018 21:12:43 +0000http://woocommerce.wordpress.com/?p=5122&ellipsis;Read the full post »]]>As you may have seen, 3.3.0 was removed from WordPress.org soon after release on Wednesday; this was to give the team time to look deeper into some theme conflicts being reported and to avoid more users running into the same issues.

The severity of the issue was relatively low, however, the volume of users running the impacted themes was potentially high, so we chose to take this safer approach.

To prevent further users downloading 3.3.0 as an automated update from WordPress admin, we reverted the stable version back to 3.2.6.

When 3.3.1 is released, the auto update will be available again for all users.

What should I do if I updated to 3.3?

If you’re running 3.3 already and your theme is compatible, you don’t need to make any changes.

If you have upgraded and saw issues with your theme, check to see if a compatibility update was released – these updates will likely fix issues on your site. For example, Genesis Connect for WooCommerce was affected and has since released a fix.

If you have upgraded, are seeing issues, and no compatibility updates have been released, you have three options:

Just wait for 3.3.1 to be released officially: This path makes sense if you’re not too concerned about the issues you’re seeing.

Update to our pre-release version of 3.3.1 available here: We only recommend this route if you’re comfortable with pre-release versions. More below on what’s already gone into 3.3.1.

Downgrade to 3.2.6 using the WP Rollback plugin: We only suggest going this route if you’re seeing issues you’re concerned about and don’t want to take the risk of a pre-release version.

Aside from the theme issues mentioned above, 3.3 is looking pretty stable. We are running it ourselves on WooCommerce.com without problems, so please only downgrade if absolutely neccessary.

Using this pre-release or downgrading should not affect your WooCommerce data as long as you never ‘uninstall’ via admin.

What are you doing to resolve this issue?

To resolve the issues, we selected a set of the most common themes running on WooCommerce stores and then tested for compatibility with the 3.3.1 release. We’ve already tested with more than 40 themes, and we believe 3.3.1 is relatively stable, but are taking the extra time to test more thoroughly.

When will 3.3.1 be out?

Subject to our continued testing, we’re aiming to have 3.3.1 out early next week (the week of the 5th Feb, 2018). Any further updates or deviations from this will be added to this post as needed.

Thanks for your support.

]]>https://woocommerce.wordpress.com/2018/02/01/woocommerce-3-3-1-status-update/feed/37mikejolleyWooCommerce 3.3 has been releasedhttps://woocommerce.wordpress.com/2018/01/30/woocommerce-3-3-has-been-released/
https://woocommerce.wordpress.com/2018/01/30/woocommerce-3-3-has-been-released/#commentsTue, 30 Jan 2018 16:39:50 +0000http://woocommerce.wordpress.com/?p=5090&ellipsis;Read the full post »]]>Today we’re excited to release WooCommerce 3.3 into the wild! 3.3 has been in development since October, and has had over 1581 commits from 80 contributors.

3.3 is a minor update. All changes should be backwards compatible with sites running any version of WooCommerce since 3.0, but we do still recommend ensuring extensions and themes are compatible before upgrading by testing on a staging site, and making backups for peace of mind.

Orders screen redesign

WooCommerce 3.3 features a revamp of the Orders screen. It has been redesigned to be simpler and clearer while at the same time being more useful. This has been developed with backwards compatibility in mind, so extensions that add features to the Orders screen should continue working normally. You can read more about these changes here.

On Backorder stock status and stock management improvements

There’s a new stock status in town! Products can now have the “On Backorder” stock status. We’ve combined this with some improvements and automation to make the product stock management experience more intuitive. You can read more about these changes here.

Greater theme support and customization

We’ve improved the way WooCommerce stores look on themes that don’t declare WooCommerce support. This was done by rendering the store content inside of the theme’s post content area. This way the layout of the store will fit neatly with any sort of theme layout and the store will look great. This change only affects themes that don’t formally declare WooCommerce support. You should now be able to use WooCommerce with almost any theme from WordPress.org!

All themes get to take advantage of this next feature: You can now use the Customizer to set the number of rows and columns in the shop. Theme developers can set minimum, maximum, and default row/column settings when declaring theme support. Read more about these features here.

Image size improvements

You can choose and change the aspect ratio of the images in your shop using the Customizer. Themes can also set the image sizes when declaring WooCommerce support.

In addition, product thumbnails are now automatically regenerated. No need for a special plugin to regenerate images! This feature uses a new event queue that processes in the background. We will be able to use this sort of queue in the future for eliminating race-conditions caused by concurrent requests and for improved performance through background processing. Read more about these changes here.

myaccount/payment-methods.php – Removed a message about new payment methods.

notices/error.php – Added role=alert for improved accessibility.

notices/success.php – Added role=alert for improved accessibility.

order/form-tracking.php – Converted submit inputs to buttons.

order/order-details-customer.php – Cleaned up and updated as part of Orders UI revamp.

order/order-details.php – New actions and a little refactoring.

order/order-downloads.php – Made the downloads table responsive.

single-product/add-to-cart/grouped.php – New hooks and added form action.

archive-product.php – Use new loop functions.

content-widget-product.php – Better action names.

product-searchform.php – Converted submit inputs to buttons.

Deprecated functions and methods in 3.3

wc_get_core_supported_themes has been deprecated since core now supports all themes.

WC_Product_Download::set_previous_hash has been deprecated since core is no longer using filename-based hashing to keep track of files.

WC_Product_Download::get_previous_hash has been deprecated since core is no longer using filename-based hashing to keep track of files.

WC_Admin_Webhooks::logs_output has been deprecated since logging is no longer done on the Edit Webhook screen.

WC_Admin_Webhooks::get_logs_navigation has been deprecated since logging is no longer done on the Edit Webhook screen.

WC_Customer_Download_Data_Store::update_download_id has been deprecated because download_id is now a static UUID and should not be changed based on file hash.

WC_Cart::get_item_data has been deprecated in favor of wc_get_formatted_cart_item_data.

WC_Cart::get_remove_url has been deprecated in favor of wc_get_cart_remove_url.

WC_Cart::get_undo_url has been deprecated in favor of wc_get_cart_undo_url.

WC_Post_Data::process_product_file_download_paths has been deprecated because no action is necessary on changes to download paths since download_id is no longer based on file hash.

WC_Webhook::get_delivery_log has been deprecated since webhook logs are stored using the logger.

How we tested 3.3

3.3 beta was released on December 12th 2017 and remained in beta until the RC on January 11th 2018. During this time we tested internally, tested our own extensions and themes, did some managed updates for actual customers on staging sites to pick up on any conflicts or bugs before the public release, and tested the update on WooCommerce.com.

Things look stable but if you spot anything, please let us know on GitHub. Thanks to everyone who helped test 3.3!

We contributors!

A massive thanks to everyone in the community who have contributed, be that via issue reports, fixes, translation, testing, supporting other users or simply spreading the word.

]]>https://woocommerce.wordpress.com/2018/01/30/woocommerce-3-3-has-been-released/feed/24blog-header-v33xclaudiulodrobionic-butterflymikejolleyclaudiulodroclaudiosancheskloonrodrigoprimodechovbelcherjWPprodigyshivapoudelbor0marcinbotstevegrunwelldavefxAdamQuadmonElectricFeetrnabyughimireragulkajames-allanalexminzav18JPrykraftbjunfulviojohndcoyvyskoczilovabsessions85axelmmfranticpsyxJeroenSormaniglagonikasMannyCseostudioMounirHamanikovsheninyratofMillerMediaryelleramiytiagohillebrandtmikalai-okunmacbookandrewbekaricemensmaximusgedextiagonoronhaMechielCouvarasbobbingwideminiMAClipemattomedmeibndawoodSiR-DanieLpathursryanr14zachddougaitkenjimjassonahmedofaligarethallisontyrann0usjamesckempChoubyshoheitanakawillgorhamn-dawsondaigo75kellychoffmanparkinepsoft79jobthomaswestiChaseWisemanjameskosterpmgarmanjdmadisoniamchetanpjpkleemanspmaioranaurosmilWooCommerce 3.3 RC2https://woocommerce.wordpress.com/2018/01/26/woocommerce-3-3-rc2/
https://woocommerce.wordpress.com/2018/01/26/woocommerce-3-3-rc2/#commentsFri, 26 Jan 2018 18:00:23 +0000http://woocommerce.wordpress.com/?p=5106&ellipsis;Read the full post »]]>WooCommerce 3.3.0 RC2 is available for testing. This includes some fixes for issues identified during RC1.

The final version of 3.3 is due for release January 30 2018. Huge props to everyone who has sent feedback about this release so far or found bugs.

]]>https://woocommerce.wordpress.com/2018/01/26/woocommerce-3-3-rc2/feed/5claudiulodroFebruary 6th: Dev chat #18https://woocommerce.wordpress.com/2018/01/23/february-6th-dev-chat-18/
https://woocommerce.wordpress.com/2018/01/23/february-6th-dev-chat-18/#commentsTue, 23 Jan 2018 17:31:54 +0000http://woocommerce.wordpress.com/?p=5085&ellipsis;Read the full post »]]>The next chat will be on February 6th at 17:00 UTC in the #core channel of the WooCommerce Community Slack. If you don’t already have access to the group, you can request an invite at the bottom of the WooCommerce developers page.

Here is the agenda for the chat:

Open forum for 3.3 post-launch feedback, including the development and release process as well as the 3.3 release itself.

Present and discuss our progress integrating WooCommerce with the new Gutenberg editor along with our plans for Gutenberg.

Present and discuss our progress on the custom product tables feature plugin, and outline our plan and timeline for integrating the feature plugin into the WooCommerce core plugin.

If you have anything to propose for the agenda or related to the above, please leave a comment below.