-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for additional actions for function wc_update_product_stock() #339
Comments
This is a small change to 2 files as outlined here: https://github.com/woocommerce/woocommerce/pull/27558/files It was introduced in WC 4.9.
|
This is a simple change that would be good for CC. Thanks @magenta-cuda @simplycomputing for highlighting this. Would you like to make a PR for this? |
No, my feeling is ClassicCommerce is not a viable product and I am porting my plugin which currently only works with ClassicCommerce to WooCommerce. While porting I am finding fixes that were made to WooCommerce after the fork of ClassicCommerce. As it takes only a small effort to submit these as issues I am willing to do this. However, a pull requests means coding and testing - this would require a significant investment of resources which I am not willing to do for a non-viable product. Anyway, my history with the stakeholders of ClassicPress and ClassicCommerce has not been very good - I have submitted multiple issues and pull requests and all of them have gone nowhere. So, you will understand my reluctance to do more. I feel the stake holders of CP and CC are not willing to further invest the resources to further develop CP and CC into good products. I apologize if this seems harsh but it is honestly the impression I have. If this is not the case then I think you need to do something differently to better reflect the resources you are committing to further develop CP and CC. Is your user base growing or shrinking? If it is not growing them maybe you need to do something different. Having said that, I really would like to see ClassicPress and ClassicCommerce succeed because:
Regards, |
You talk about "the stakeholders of ClassicPress and ClassicCommerce" as if there is a team of developers out there somewhere dedicated to doing the work. This is a community project, so the stakeholders are actually you and me. Anyway, thanks for the input. The issue has been noted. |
WooCommerce has added two more actions - 'woocommerce_variation_before_set_stock' and 'woocommerce_product_before_set_stock' - to function wc_update_product_stock() in file wc-stock-functions.php.
`
function wc_update_product_stock( $product, $stock_quantity = null, $operation = 'set', $updating = false ) {
`
These actions would be extremely useful to my plugin and I think useful to other 3rd party plugins as well.
The text was updated successfully, but these errors were encountered: