WooCommerce 2.7 beta 1 has been released on December 15, 2016. The first release candidate is expected to land in February 2017. If you’d like to help test, you should download the release from Github.
In the meantime here are the latest release notes from 2.6.8 through 2.6.10.
WooCommerce 2.6.8
On November 10 WooCommerce 2.6.8 was released to fix a few issues.
This release had ~14 commits.
- Fixed an issue where REQUEST_URI was missing a trailing slash during comparison in our page caching functions.
- Fixed an issue where empty prices were sent to PayPal.
- Fixed email validation on the account page.
The extensions screen was also updated so it’s a bit more modern.
WooCommerce 2.6.9
WooCommerce 2.6.9 security/fix release was released on December 7. ~44 commits made it into this release fixing several minor issues and taking care of some security hardening.
The main change was compatibility with WordPress 4.7 and the new Twenty Seventeen theme!
The full changelog for 2.6.9 is below.
- Theme – Added support for Twenty Seventeen Theme.
- Fix – Excluded webhook delivery logs from comments count.
- Fix – Included password strength meter in «Lost Password» page.
- Fix – Order fee currency in admin screen.
- Fix – Variation selection on Firefox 40.
- Fix – Don’t prevent submission when table is not found on cart.
- Fix – Improved layered nav counts on attribute archives.
- Fix – Fixed pagination when removing layered nav items via widget.
- Fix – Default BE tax rate.
- Fix – Downloads should store variation ID rather than product if set. Also fixes link on account page.
- Fix – Use wp_list_sort instead of _usort_terms_by_ID to be compatible with 4.7.
- Fix – Only return empty string if empty for weight and dimension functions.
- Security – Wrapped admin tax rate table values in _escape to thwart evil CSVs an admin user could upload. Vulnerability was discovered by Fortinet’s FortiGuard Labs.
- Dev – API – Only update categories menu order and display if defined.
- Dev – Fixed when should deliver wp_trash_post webhooks.
WooCommerce 2.6.10
WooCommerce 2.6.10 fix release landed on December 22. ~30 commits made it into this release fixing several issues.
The main change to be aware of surrounds the variation add to cart form script. A few versions back we spotted an incompatibility with the latest version of Firefox which would deselect an attribute on click. This was “fixed” in 2.6.9, however this inadvertently prevented the ‘default selected’ attributes from working correctly in other browsers.
It was narrowed down to the way WooCommerce would filter out non-relevent attributes on select box focus. Some browsers did not like the DOM being changed during the focus event. To resolve this, the DOM needed to be kept up to date and left alone during focus.
The PR which fixed this can be found here. You’ll notice it’s a fairly substantial refactor, and one we wouldn’t usually feel comfortable including in a fix release, but it was necessary to resolve the browser compatibility issues and makes the script more easily understandable. The WooCommerce core devs have been testing this internally since merging.
The full changelog for 2.6.10 is below.
- Fix flat rate no class costs when no shipping classes exist.
- Fix returned REST API coupon expiry date.
- Fix reviews_allowed being set to false in Rest API.
- Fix sales date series for some custom ranges.
- Fix missing attributes when an option is chosen by default on variations. This was the result of a Firefox 50 compatibility fix. In order to support both Firefox, Chrome, IE, and Edge we’ve done some refactoring of the variation add to cart scripts.
- Updated Geo IP API services.
- Added support for WP VIP/VIP GO GEO IP headers.
- Dev – API – Throw error messages when product image ID is not a valid WordPress attachment ID.
If you spot any further issues, please report them on GitHub so the development team can review.
Remember to backup before updating. Good luck and happy ecommerce!
