[webmaster.mid]

Hi,

I have an old MVX install. I updated to last version.

I am still no using HPOS but would be interested in.

I would need to know if there is some kind of documention regarding HPOS migration form old WCMP / MVX /Woo structure to new HPOS structure.

[Sangita Support Squad]

Hello there, You can try a simple approach by creating a staging site (a replica of your live site). On the staging site, enable the HPOS feature and check whether everything works as expected. Once you’ve confirmed that everything is functioning correctly on staging, you can safely enable the feature on your live site as well.

If you need any further assistance, please feel free to let us know – we’ll be happy to help.

[webmaster.mid]

What do you mean by « everything works as expected«  ?

What is expected ?
Migration of all old orders ?
New orders in both good and old way ?

Is there a way to clean all old orders from posts tables ?

Does the migration is only based on woocommerce stras are migration ?

Does mvx make specific changes durinh migration ?

[Sangita Support Squad]

Hi there,

Thank you for getting back to us and for your detailed questions.

When we say that “everything works as expected”, we are referring to the standard WooCommerce HPOS (High-Performance Order Storage) behavior working correctly with MultiVendorX, without any disruption to order management.

To clarify your points in detail:

— Migration of existing orders:
>> When you enable the HPOS option in WooCommerce, WooCommerce itself will prompt you to sync the existing orders. This migration process is fully handled by WooCommerce and ensures that your old orders remain accessible and properly synced with the new order storage system.

— New orders after enabling HPOS:
>> Once HPOS is enabled and the sync is completed, any new orders placed will follow the HPOS structure. For MultiVendorX vendor products, both the main order and the corresponding suborders should continue to be created as usual.

— Testing recommendation:
>> Although no issues are expected, we strongly recommend placing a test order for a vendor product after the migration to confirm that the main order and suborders are being generated correctly. For safety, it’s best to perform this testing on a staging site first, and once confirmed, apply the same steps on your live site.

— Cleaning old orders from posts tables:
>> WooCommerce does not recommend manually removing old orders from the posts tables. These records are kept for backward compatibility and data integrity, and removing them may lead to unexpected issues.

— Migration scope:
>> The migration process is handled smoothly, so no issues are expected after enabling this feature.

If you have any further questions or would like any further assistance, please feel free to let us know—we’ll be happy to help.

[Author]

Posts