Fields associated to WooCommerce orders with HPOS

  • WooCommerce is currently introducing High-Performance Order Storage (HPOS), a new database schema that will improve the performance.

    One of the main changes is that orders and refunds are no longer custom post types, but they (and their corresponding metadata) will be kept in different tables, and will use different edition pages.

    Until now, we were using ACF for some fields that were shown in the Order edition pages, by selecting “Show when the post type is Order”. However, we’ve already checked that these fields won’t be shown nor work once we migrate the database to HPOS (as the metadata will be moved).

    Do you plan to add support to fields associated to the new WooCommerce orders, once HPOS is active?

Viewing 15 replies - 1 through 15 (of 24 total)
  • Plugin Contributor Iain Poulson

    (@polevaultweb)

    ?Hi @davefx, Iain here, the product manager for ACF over at WP Engine ??

    Thanks for the heads up, we’ll get this logged on our internal tracker and investigated. I’ll resolve this ticket for now, but will update you when we move forward with it.

    Thread Starter David Marín Carre?o

    (@davefx)

    @polevaultweb I’ve been told by ACF-Pro support that you won’t support fields associated to Orders once orders in the site won’t be custom post types any longer.

    I’d just like to confirm this information, in order to start moving our current Order-associated custom fields into native WooCommerce fields inside their meta-boxes, or we still should wait for a short-term incoming support: these fields currently are one of the few things that are blocking us from moving our system to HPOS.

    @davefx ??

    ilwoody

    (@ilwoody)

    Hi guys! Any news about the implementation with HPOS order? ACF fields still won’t appear. Thanks!

    robertstaddon

    (@robertstaddon)

    I’m also curious if ACF Pro is planning to release an update with HPOS compatibility. I just tried upgrading to HPOS on a site but had to roll it back when I found that none of my ACF fields worked.

    With all due respect but shouldn’t this be a priority for the ACF team right now?

    @fawadinho As much as I want ACF to support WooCommerce orders, they’re no longer posts and ACF is focused on posts. So the “priority” is not so clear.

    We’re looking to migrate to HPOS but we have ACF fields on orders and subscriptions. I guess we have to decide whether to ditch HPOS or ditch ACF?

    • This reply was modified 11 months, 1 week ago by icanoop.

    @icanoop it seems like, yes

    Same problem here. Would have been great if HPOS was supported.

    I think ACF should work as is at the function/API level with HPOS compatibility mode enabled. The only problem I see is that ACF fields don’t show up on the edit order & edit subscription pages with HPOS enabled because ACF only adds meta boxes to posts and orders are no longer posts.

    It seems like minimal effort for ACF to work when HPOS compatibility mode is enabled. Running with compatibility mode still gets you a lot of the benefit of HPOS such fast order searching.

    Is there any chance ACF would consider supporting HPOS with compatibility mode?

    Is there any chance ACF would consider supporting HPOS with compatibility mode?

    I think that if ACF decides to add compatibility, they should do it with or without “compatibility mode”, and use the orders meta table (which WooCommerce will take care of sync in case the compatibility mode is on.

    I agree that would be ideal. But it would also be more work for them. I’m appealing to the minimal effort aspect of compatibility mode.

    Plugin Contributor Iain Poulson

    (@polevaultweb)

    Hey folks, now we have ACF 6.3 out the door we can turn our attention to what’s next. We plan to add support for WooCommerce HPOS – hopefully in ACF 6.4.

    ??

Viewing 15 replies - 1 through 15 (of 24 total)
  • You must be logged in to reply to this topic.

Tags