WooCommerce 4.3.3 fix release

This release fixes a regression with REST API that was inadvertently introduced in 4.3.2. Here is the changelog for the release:

**WooCommerce REST API 1.0.10-pl-2**
* Fix - Fix regression and restore backward compatibility for date-time and mixed datatypes. #239

Download the latest release of WooCommerce here or visit Dashboard → Updates to update the plugin from your WordPress admin screen.

As usual, if you spot any other issues in the WooCommerce core, please log them in detail on GitHub. Found a security issue? Please submit a report via HackerOne.

4 responses to “WooCommerce 4.3.3 fix release”

  1. Lagaao Store Avatar
    Lagaao Store

    I’m unable to edit Product details in my store.
    Please help me

    it must me some kind of technical issue it’s showing (#) before ( inventory_product_data)


    1. Peter Fabian Avatar
      Peter Fabian

      Hi Lagaao!

      Sorry to hear you’re having problems. Please try to follow the troubleshooting steps to rule out plugin or theme conflict and if you still experience the problem, please let submit your system status report to our GitHub repository along with steps to reproduce the problem.


  2. I have this particular code to remove structured data before update to woocommerce 4.3.3 in my theme functions.php

    function remove_output_structured_data() {
    remove_action( ‘wp_footer’, array( WC()->structured_data, ‘output_structured_data’ ), 10 ); // Frontend pages
    remove_action( ‘woocommerce_email_order_details’, array( WC()->structured_data, ‘output_email_structured_data’ ), 30 ); // Emails
    add_action( ‘init’, ‘remove_output_structured_data’ );

    After the update to woocommerce 4.3.3 site went onto recovery mode. After removing the above function, it is now working as usual. If there is any changes that affect this code

    1. Peter Fabian Avatar
      Peter Fabian

      Hi Gopi,

      The only changes in WC 4.3.3 were related to REST API schema. I tried adding your code to my test site and the test site seemed to work fine, so maybe another plugin you have installed is causing issues? Hope you’d be able to identify the problem.

Leave a Reply

Your email address will not be published. Required fields are marked *