Why enabling HPOS affect some hooks?

  • Resolved titsmaker

    (@titsmaker)


    3 months, 3 weeks ago

    Hi, after enabling HPOS I noticed that some my customizations of orders table no longer work. Why this happens if I have “Enable compatibility mode (synchronizes orders to the posts table)” feature enabled? AFAIU the posts table is still populated with all the data so old hooks should work as before.
    Are hooks like ‘manage_shop_order_posts_custom_column’ and ‘manage_edit-shop_order_columns’ completely useless now?
    Also the plugin I used for tracking (in 2024 you need a plugin to have tracking numbers in your shop…) stopped working and this time I have no idea what caused this. It used to render extra metabox with tracking number input field but now it’s not present. Any ideas what kind of hook can be responsible for this? I tried checking plugin code but it is rather lengthy and complicated so I was not able to locate the issue.

Viewing 3 replies - 1 through 3 (of 3 total)

  • Custom fields are stored in the ‘postmeta’ field, if for example, you made them using ACF/SCF – and they haven’t yet added compatibility with HPOS, as this doesn’t use the postmeta table.

    I believe they are already trialing this in beta for ACF, no idea about SCF

    Plugin Contributor Barry

    (@barryhughes-1)

    There are some alternative hooks you might be interested in. For instance:

    manage_woocommerce_page_wc-orders_custom_column

    The reason we’ve had to replace various core WP hooks with alternatives (at least in some cases) is that the originals are documented as supplying WP_Post objects to callbacks. With HPOS, that is no longer the case.

    Plugin Contributor Barry

    (@barryhughes-1)

    It used to render extra metabox with tracking number input field but now it’s not present.

    It’s difficult to say, as there are lots of reasons this might not be working. Either of these hooks can be used to add meta boxes to the (HPOS) order editor:

    • add_meta_boxes
    • add_meta_boxes_woocommerce_page_wc-orders

    The first of those supplies the screen ID (woocommerce_page_wc-orders) so it’s possible the problem is that the plugin in question expects the previous screen ID.

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