Not hiding products without stock
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from juanpa91 on March 4, 2026, 07:00Hello, I have download your plugin in my 2 sites, one used in Brasil and the other in Uruguay.
In brazilian site, the plugin hide products atributes that are zero (for example, I have 36 products that size goes from 4 to 11, but now I have only 17 of them size 8 in stock available and is exactly what it shows, "17") but in Uruguay site, that doesn't happened.
Instead of that, the plugin show all the products that size 8 is a possible option, although in some of them I am out of stock.
I will appreciate any help with this in Uruguay site.
Regards
Hello, I have download your plugin in my 2 sites, one used in Brasil and the other in Uruguay.
In brazilian site, the plugin hide products atributes that are zero (for example, I have 36 products that size goes from 4 to 11, but now I have only 17 of them size 8 in stock available and is exactly what it shows,"17") but in Uruguay site, that doesn't happened.
Instead of that, the plugin show all the products that size 8 is a possible option, although in some of them I am out of stock.
I will appreciate any help with this in Uruguay site.
Regards
Quote from Alex Dovlatov on March 4, 2026, 12:31Hello Juan
Thanks for the detailed description — this makes it easy to diagnose!
The difference in behavior between your two sites is almost certainly caused by a WooCommerce setting, not WOOF itself. WOOF respects WooCommerce's own stock visibility rules.
Please check this setting on the Uruguay site:
WooCommerce → Settings → Products → Inventory → "Out of stock visibility"
☑ Enable "Hide out of stock items from the catalog"
On your Brazil site this option is likely enabled, which is why WOOF correctly shows only the sizes that have available stock. On the Uruguay site it's probably disabled, so WooCommerce treats out-of-stock variations as still "visible" — and WOOF reflects that.
Once you enable that option on the Uruguay site, WOOF will automatically show only the attribute values (sizes) that have products actually in stock, matching the behavior you see in Brazil.
Note: After changing this setting, you may need to clear any caching (site cache, object cache) for the change to take effect on the frontend immediately.
Let me know if that resolves it!
Hello Juan
Thanks for the detailed description — this makes it easy to diagnose!
The difference in behavior between your two sites is almost certainly caused by a WooCommerce setting, not WOOF itself. WOOF respects WooCommerce's own stock visibility rules.
Please check this setting on the Uruguay site:
WooCommerce → Settings → Products → Inventory →"Out of stock visibility"
☑ Enable "Hide out of stock items from the catalog"
On your Brazil site this option is likely enabled, which is why WOOF correctly shows only the sizes that have available stock. On the Uruguay site it's probably disabled, so WooCommerce treats out-of-stock variations as still"visible" — and WOOF reflects that.
Once you enable that option on the Uruguay site, WOOF will automatically show only the attribute values (sizes) that have products actually in stock, matching the behavior you see in Brazil.
Note: After changing this setting, you may need to clear any caching (site cache, object cache) for the change to take effect on the frontend immediately.
Let me know if that resolves it!
Quote from juanpa91 on March 4, 2026, 15:02Hi Alex, thank you for your reply.
The "Out of stock" checkbox was enable, so It isn't that.
Any other recomendation?
Regards
Hi Alex, thank you for your reply.
The"Out of stock" checkbox was enable, so It isn't that.
Any other recomendation?
Regards
Quote from Alex Dovlatov on March 5, 2026, 12:48Hi Juan
Since your Brazil site works correctly, the answer lies in the differences between the two setups. Let's compare them directly.
Could you please provide the following in the private section of this ticket:
- Admin access to both sites (URL, login, password) so I can compare the WOOF settings and WooCommerce configuration side by side
- Both purchase codes (the active ones from your CodeCanyon account) — one for each site if you have installed premium versions
https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png
https://share.pluginus.net/image/i20230222134511.pngAlso, a few quick questions to narrow it down faster:
- Are both sites running the same version of WOOF?
- Are both sites running the same version of WooCommerce and PHP?
- Are both sites using the same theme and the same set of plugins?
The root cause is definitely a configuration difference between the two — once I can compare them directly I should be able to pinpoint it.
Thanks!
Hi Juan
Since your Brazil site works correctly, the answer lies in the differences between the two setups. Let's compare them directly.
Could you please provide the following in the private section of this ticket:
- Admin access to both sites (URL, login, password) so I can compare the WOOF settings and WooCommerce configuration side by side
- Both purchase codes (the active ones from your CodeCanyon account) — one for each site if you have installed premium versions
https://share.pluginus.net/image/i20230222134241.png
https://share.pluginus.net/image/i20230222134615.png
https://share.pluginus.net/image/i20230222134511.png
Also, a few quick questions to narrow it down faster:
- Are both sites running the same version of WOOF?
- Are both sites running the same version of WooCommerce and PHP?
- Are both sites using the same theme and the same set of plugins?
The root cause is definitely a configuration difference between the two — once I can compare them directly I should be able to pinpoint it.
Thanks!
