Strange meta data fields in Rest API export

  • Hello,

    We use the WooCommerce Rest API to sync product with channable .com (and from there to Amazon).

    Since a few days, we receive this error from Channable:

    We ran into the following problem: Can’t import values for field “meta_et_builder_module_features_cache.et_pb_text_91d1d1d829a0d5a7269bbd45f1632150.foop”. The values for field “meta_et_builder_module_features_cache.et_pb_text_91d1d1d829a0d5a7269bbd45f1632150.foop” are in a different format. Please use one specific format for this field or set it to “do not import” in mapping.

    (same for many more similar fields)

    These meta fiels are not included in a regular CSV export with meta from the Woo products page.

    The “et_builder_module” part in the fields name indicates that this field originates from the Divi theme builder.

    But, the theme builder is not being used for Woo products, so I don’t understand why et_builder fields popup in the Woo Rest API export.

    We did not install any updates around that date, with the exception of ‘Mollie Payments for WooCommerce’.

    Do you have any idea why builder fields are being added to the Woo Rest Api export.
    And more important, how to get rid of them?

    Thanks
    JP

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Senff

    (@senff)

    Hey @jpnl

    Although the Divi theme builder may not be specifically used for WooCommerce products, their data is likely being included in the API export for any/every post types (WooCommerce products are essentially a custom post type).

    Since the Divi plugin was not created by us at WooCommerce.com, I’d recommend reaching out to the plugin’s own support team first, to see if they can give you more information about this, and if it’s possible to not include that data in the export of the product type.

    While we’re experts on our own products, third party plugins are best supported by their own resp. developers (and more importantly, I’d rather not give you any incorrect information).

    Thank you for your reply. I don’t fully understand though.

    If I do an export from the Woo products list, this meta data is not included. But it is included if I use the Woo API keys to do an export. It’s both provided by and coming from Woo, so why is there a difference between the two exports?

    Thanks
    JP

    Plugin Support Senff

    (@senff)

    Hey @jpnl

    This is the part where I’m not sure if I understand how or when Divi exports its data. ?? I’m not an expert on that, so if you want to know more about why Divi data is included in the Rest API export, but not in the standard WooCommerce export, Divi’s support team can probably help you with that.

    But its the other way around. We use WooCommerce for the export. Not Divi.

    Regular WooCommerce export
    I use the Woo export button shows above the product list.
    In the export screen I enable the option to export custom meta data.
    It only exports the meta data that belongs to the product.
    There is no “meta_et_builder_module” Divi data included.

    WooCommerce Rest API
    We use the WooCommerce Rest API keys as created in the Woo settings.
    The integration partner pulls the product list including the mete data.
    Now the “meta_et_builder_module” Divi data is included.

    So why does WooCommerce send additional meta data, that doesn’t belong to products, with the Rest API. It knows it doesn’t belong to products because it’s not included in the regular export either.

    fyi, I also have a ticket about this with Divi support and for now it looks like Woo and Divi are pointing to each other.

    dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hi @jpnl

    How frustrating this must be for you!

    As this is specific to your site, we won’t be immediately able to replicate this.

    Can I ask for you to gather either a screenshot or to copy the exact response the partner is seeing from the WooCommerce REST API.

    Being able to see this meta_et_builder_module in context will help us possibly provide a solution or understand why this is happening.

    Thanks,

    Thanks Doug, I try to get my hands on it.

    Mirko P.

    (@rainfallnixfig)

    Great! We look forward to hearing back from you on this!

    Thanks.

    Mirko P.

    (@rainfallnixfig)

    Hi there,

    We haven’t heard back from you in a while, so I’m going to close the thread for now – we’ll be here if and/or when you are ready to continue.

    That’s ok. I haven’t heard back from the webshop owner and integrator either, so I guess it’s not as big of a problem as they first claimed it to be.

    Thanks.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Strange meta data fields in Rest API export’ is closed to new replies.