Top

Version 1.7 Released

Version 1.7 of the WooCommerce Zapier plugin has just been released.

This release includes the following:

  • Compatibility with WooCommerce 3.3 and 3.2 (and backwards compatible with WooCommerce v3.1.x and 3.0.x).
  • Send data to Zapier synchronously, instead of relying on WordPress Cron. This should prevent scenarios where data is sent to Zapier multiple times or not at all.
  • New: Line Item Unit Price field for orders and subscriptions.
  • Fix: Avoid intermittent PHP fatal error that occurred with some variable products.
  • “New Order Status Change” trigger: Include previous and new order statuses in the order’s notes.
  • “New Subscription Status Change” trigger: Include previous and new subscription statuses in the subscription’s notes.
  • Improved logging of Zapier’s response after sending data to Zapier.
  • Sending data asynchronously via WordPress cron is now deprecated and will be removed in a future version.
  • Change: Minimum required version is now WooCommerce 3.0.0.

See the full changelog for details of the other changes in this release.

Update today!

The latest plugin version can be downloaded via your WordPress dashboard, or via the WooCommerce.com my account page.

Questions?

If you are looking for technical support, try the Documentation, Zapier Help Desk or the WooCommerce Help Desk.

2 Responses to Version 1.7 Released

  1. Avatar for Jon
    Jon February 3, 2018 at 9:20 pm #

    Hi there! With this new release changing to synchronous sending of data, how will that affect performance? One of the reasons I am using this and Zapier is because it offloads tasks to be completed separate from the final order processing.

    Bottom line is, will this slow down checkout for customers? Is this adding processes to the checkout? The last thing I need is a slower checkout. Thank you!

    • Avatar for James
      James February 5, 2018 at 3:52 pm #

      Hi Jon, great question!

      This change was implemented because there was a growing portion of our user base that was having relabiality issues with WordPress’ cron facility, causing them to either not receive data at all, or for data to be sent multiple times.

      Depending on the payment gateway used, it does mean that additional processes could be added to the checkout submission process.

      Advanced users who want to continue sending data asynchronously can do so by using the wc_zapier_send_asynchronously filter if they wish. See example code here.

      James