You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm wondering if you'd be interested in allowing custom order statuses to be canceled? Right now it's not possible as you're checking the status being passed with an array of authorized statutes.
You should be able to use any status, regardless if it's authorized. It just provides more flexibility.
Also, have you considered adding in debugging so that if a mistake occurs, a user can recover all the orders that were canceled? Furthermore, a "Don't do anything" option for testing that doesn't actually cancel the order but prints out debugging information on what orders would have been cancelled.
The text was updated successfully, but these errors were encountered:
Yes it is true that the status check is annoying, but at the origin of the plugin, was normally for pending orders. Then someone asked me to cancel orders in another status.
The concern which could have is to make a request for cancellation on a post which is not an order.
I will think to open this possibility.
When it comes to testing and dry-running, I don't think it's necessary (or else I'm wrong), because in general,
the system is not supposed to crash (the actions it does are low) and the dry-run was not considered, because from the beginning the plugin wanted the simplest and lightest (that's why we use hooks).
I don't know if this function would interest a lot of people
You could check to confirm the post is an order, you could also confirm what statuses are set up in WooCommerce. Some installations do have custom order statuses.
If you do allow statuses outside of the current defined by a default WooCommerce installation, the dry run helps the user confirm what they're doing is correct.
Hello, I'm wondering if you'd be interested in allowing custom order statuses to be canceled? Right now it's not possible as you're checking the status being passed with an array of authorized statutes.
You should be able to use any status, regardless if it's authorized. It just provides more flexibility.
Also, have you considered adding in debugging so that if a mistake occurs, a user can recover all the orders that were canceled? Furthermore, a "Don't do anything" option for testing that doesn't actually cancel the order but prints out debugging information on what orders would have been cancelled.
The text was updated successfully, but these errors were encountered: