Develop WooCommerce

The official WooCommerce development blog

Dev Chat Summary: May 9th — May 10, 2017

Dev Chat Summary: May 9th

This post summarizes the dev chat meeting from May 9th. (agenda, Slack archive).

How we deal with “random” products and caching

Currently results from product shortcodes are saved in cache for 30 days, and this is raising issues with “Random” products since some users feel it is too much time.

All results were randomly chosen, even if you refresh five times and see the same products, not to mention that “Random” does not mean “New every page refresh”.

We decided to do a few extra queries, creating a range of random products saved in cache, so every page refresh we can randomly choose a range of products already cached and shuffle them. This will create an impression that have new products for every page refresh without the burden of querying new products each time.

Progress with CRUD search

We decided to split it into every CRUD object, so will be done products by 3.1, and then Coupons and Orders for 3.2.

Claudiu is currently work in a better way to do query search, like doing queries by date using:

>=2017-05-05
>2017-05-05
<2017-05-05
<=2017-05-05 2017-05-05...2017-05-08 >=1493942400
>1493942400
<1493942400
<=1493942400
1493942400...1494201600

Check #14971 for more details.

Progress with importer

Work in progress, but we have a parser ready and by the end of this week we’ll have it working. More news coming soon.

May 9th: Dev chat #3 — May 8, 2017

May 9th: Dev chat #3

It’s time for our third dev chat, if you missed something in the last one, you can recap our summary here.

Our third dev chat will be on May 9th at 16: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:

  • How we deal with “random” products and caching.
  • Progress with CRUD search.
  • Progress with importer.
  • Anything else? Contribution ideas, projects, & thoughts.

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

See you there!

WooCommerce 2.6.13 fix release notes — January 18, 2017

WooCommerce 2.6.13 fix release notes

The WooCommerce 2.6.13 fix release is now available. You can download it from WordPress.org or as an automatic update in your administration panel.

~8 commits made it into this release fixing a few issues.

The full changelog for 2.6.13 is below.

* Fix - Demo store banner styling in 2017.
* Fix - Removed default instructions from COD, BACS and Cheque gateways so displayed messages can be unset.
* Fix - Made variation options update on first load.
* Localisation - Added Romanian locale to the installer.

If you spot any further issues, please report them to us in detail on GitHub so the development team can review – comments on this post are closed.

WooCommerce 2.6.12 fix release notes — January 12, 2017

WooCommerce 2.6.12 fix release notes

The WooCommerce 2.6.12 fix release is now available. You can download it from WordPress.org or as an automatic update in your administration panel.

~12 commits made it into this release fixing a few issues.

The full changelog for 2.6.12 is below.

* Fix - Make images shown up on pageload when using ajax variations.
* Fix - Allow variations options to be deselected in IE11.
* Fix - Disabled-button and pagination styling in 2017.
* Fix - PHP 7.1 compatibility issues with non-numeric math operations.
* Fix - Fix notices in abstract class when price is empty.

If you spot any further issues, please report them to us in detail on GitHub so the development team can review – comments on this post are closed.

New REST API based on the WP REST API in 2.6 — April 22, 2016

New REST API based on the WP REST API in 2.6

During the development of WooCommerce 2.1 (Back in Feb 2014) we knew that one day WordPress would have it’s own REST API, but the demand was so great for such a thing in WooCommerce we had to roll our own.

We’ve learned a lot from this process and our API is now widely used, but given recent developments surrounding the actual WordPress REST API, and since it is now part of WordPress core (since version 4.4) we started work to replace ours with what is available in WordPress.

2.6 will contain this new API, and will require WordPress 4.4 or higher.

Continue reading