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
3rd Party Plugin Compatibility: WooCommerce + Hide Out of Stock Products #674
Comments
@raamdev I'm unable to reproduce this problem with WordPress v4.5.3 + Comet Cache v160709 + WooCommerce v2.6.3 using these steps.
|
The reason for you being unable to reproduce it this way could be because you changed this from the admin, where a change in the stock status is also accompanied by the I suggest fixing this by attaching to this hook in WC.
|
Comet Cache already attaches to |
You'll need the |
@jaswsinc Got it. Thanks for the link to the WooCommerce source! I'll get this fixed for the next release. |
…`woocommerce_product_set_stock_status` hook in addition to the `woocommerce_product_set_stock` hook. See also: [issue #674](wpsharks/comet-cache#674) if you'd like additional details.
Next Release Changelog:
|
Confirmed WorkingSteps taken
Shop Catalog with Product In Stock with 1 item After Purchase of 1 Product (Out of Stock) |
Comet Cache v161119 has been released and includes changes from this GitHub Issue. See the v161119 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#674). |
A user report indicates that when "hide out of stock products from the catalog" is enabled in WooCommerce, and a product goes out of stock, the catalog pages are not updated (i.e., the old cache file is loaded, which shows the now-out-of-stock product that should be hidden).
In #597 we improved compatibility with WooCommerce and stock changes, however it sounds like there's room for more improvement here so I'm opening this GitHub issue so that we can look into this more closely.
The text was updated successfully, but these errors were encountered: