23a605c14c
This includes the following: - Fix the "upshifting" that was implemented in 36218 so that it only applies when the post type of the order being deleted is hierarchical (this conforms to the WordPress behavior when deleting a post). - Now when an order is deleted while sync is off a record will be created in wp_wc_orders_meta (regardless of which table is the authoritative one) with 'deleted_from' as the key and the authoritative table name (from where the order has been deleted) as the value... - ...then DataSynchronizer will detect the presence of these 'deleted_from' records and delete them from the backup table as part of the batch processing procedure. - Exception to the above: when an order is deleted from the orders table and the corresponding records in the posts table are placeholders, these are deleted immediately too, even if sync is off. - Add an "order_exists" method in both order data stores (Abstract_WC_Order_Data_Store_CPT and OrdersTableDataStore). - Add a pair of get/set_verify_parent_id methods in WC_Abstract_Order (turning off the check in set_parent_id is necessary when deleting an order using the backup data store during synchronization). - Placeholder records are now created with the appropriate parent id for child orders (e.g. refund), this is necessary in order to properly find which records need to be deleted. |
||
|---|---|---|
| .. | ||
| woocommerce | ||
| woocommerce-admin | ||
| woocommerce-beta-tester | ||