Why no HPOS compatibility?

  • titsmaker

    (@titsmaker)


    3 months ago

    Hi, guys. Why this plugin has no HPOS compatibility? It seems you made it intentionally but it won’t make 3rd party companies to upgrade their code faster. E.g. Integromat (now “Make”) still uses legacy API and has no plans to upgrade it. Declaring HPOS compatibility is just a few lines of code . AFAIU no changes needed except declaring compatibility for this plugin.

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

    (@dabesa)

    2 months ago

    +1

    Barry

    (@barryhughes-1)

    2 months ago

    Why this plugin has no HPOS compatibility?

    At this point, the Legacy REST API has been deprecated for many years. It was never compatible with HPOS (High-Performance Order Storage).

    The key difference is that, if you install this plugin, it actively warns of this risk. However, you can still use them together so long as you enable HPOS’s compatibility mode. To do this, visit the appropriate setting found at:

    WooCommerce ▸ Settings ▸ Advanced ▸ Features

    In the end, though, this should be considered a temporary solution. It is best to migrate to an actively supported version of the REST API.

    Barry

    (@barryhughes-1)

    2 months ago

    Declaring HPOS compatibility is just a few lines of code . AFAIU no changes needed except declaring compatibility for this plugin.

    To pick up on this point in a little more detail: yes, in theory we could do that, but doing so would be wrong since the Legacy REST API is not compatible with HPOS.

    In other words, if you use HPOS without enabling compatibility mode, the Legacy REST API is not guaranteed to return accurate information about orders. That’s the reason for the warning.

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