The Legacy REST API is not compatible with HPOS, and never has been. It’s important for merchants to be aware of that. If they need both, then enabling Compatibility Mode as you seem to have already done is a sensible precaution.
Does that answer your question?
Correct me if I’m wrong (honestly), but using “Compatibility mode” is even worst than just sticking to the old posts table, because now everything (read/write) is done twice: on the new orders/ordermeta table and on the WordPress native posts/postmeta tables.
Hi @webdados,
You’re correct about the added work: instead of just writing order data to one store, we have to write to two different stores. How much of an impact this will have, though, will obviously vary greatly.
It’s also worth remembering that, going forward, our own maintenance and development efforts will tend to be concentrated on HPOS, rather than the classic CPT-based order store. Additionally, there is a small amount of divergence between the two implementations when it comes to things like the range of hooks that are available for customization.
I’m flagging those things because, for many merchants, the (hopefully temporary) performance impact of Compatibility Mode will be negligible, and there will be more value in using the new default store (actively supported and developed, with third party extensions increasingly developed and tested only against HPOS).
So, it’s worth weighing the trade-offs here. There could certainly be cases where it is preferable to just turn off HPOS and utilize the legacy order store, but that will not always be true.
I’m flagging those things because, for many merchants, the (hopefully temporary) performance impact of Compatibility Mode will be negligible, and there will be more value in using the new default store (actively supported and developed, with third party extensions increasingly developed and tested only against HPOS).
Definitely. My comment was just to alert anyone reaching here that the “compatibility mode” should be a temporary thing, while migrating for example, and not to be seen as something you can stay with forever.
For sure, thank you.
In fact, the WooCommerce Legacy REST API plugin itself should be seen as a temporary measure, rather than something to depend on for years to come (as it is legacy functionality that we do not intend to maintain indefinitely).
