WOOF filter slow and not correct
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 anne on June 25, 2021, 15:18Currently we are using WOOF to filter on our website. This was pretty fast until we noticed that some attributes were out of stock and still showing.
To fix this we enabled the “in_stock” filter by default. This fixed the issue but made the website really slow. We then tried to enable the WOOF turbo mode. But this caused the filter to be still a bit slow and also caused products variations to be shown when they were out of stock.
We have around 3000 products and each product has around 9 variations and this makes in total about 27000 variations. How could we implement WOOF to be fast and have it also show us the correct, in stock, products (by counting the in stock variations)?
Currently we are using WOOF to filter on our website. This was pretty fast until we noticed that some attributes were out of stock and still showing.
To fix this we enabled the “in_stock” filter by default. This fixed the issue but made the website really slow. We then tried to enable the WOOF turbo mode. But this caused the filter to be still a bit slow and also caused products variations to be shown when they were out of stock.
We have around 3000 products and each product has around 9 variations and this makes in total about 27000 variations. How could we implement WOOF to be fast and have it also show us the correct, in stock, products (by counting the in stock variations)?
Quote from Pablo Borysenco on June 28, 2021, 12:32Hello
Unfortunately, "in stock" to work correctly, the filter must check each variation that causes a high load on server resources
Please try to use these options - https://share.pluginus.net/image/i20210628133227.png
Hello
Unfortunately, "in stock" to work correctly, the filter must check each variation that causes a high load on server resources
Please try to use these options - https://share.pluginus.net/image/i20210628133227.png
Quote from anne on July 27, 2021, 14:17Hello Pablo,
Thanks for you reply. We've tried a few things, also enabling cache.
Enabling cache means that when a product is sold, the filtermenu will still show the product as available, meaning that customers get to see products that aren't on stock anymore.
Is there a solution to make the filters work with the "in stock" but without cache while maintaining an acceptable loadtime of < 2 seconds?
Greetings,
Hello Pablo,
Thanks for you reply. We've tried a few things, also enabling cache.
Enabling cache means that when a product is sold, the filtermenu will still show the product as available, meaning that customers get to see products that aren't on stock anymore.
Is there a solution to make the filters work with the"in stock" but without cache while maintaining an acceptable loadtime of < 2 seconds?
Greetings,
Quote from Pablo Borysenco on July 28, 2021, 10:50Hello
Read this please - https://products-filter.com/searching-is-slow/
It also depends on your server
Hello
Read this please - https://products-filter.com/searching-is-slow/
It also depends on your server
Quote from anne on July 28, 2021, 17:35Hi!
The suggestions are helpful. One of the fixes is to turn off 'dynamic recount' and 'hide empty terms' options. The filter is indeed fast when those options are disabled, but the website is also not working properly anymore.
Disable those options results in the filter returning many empty responses.We want the filter to adapt to the previous selected filters (and stock). So when the color 'red' is selected, all other options, like a 'brand' that doesn't contain any product with the color red, needs to disappear.
Explaining the issue isn't easy. We've tried many different settings to make this work, but all out comes are either slow or not working as needed.
Is it possible to share our screen and explain the issue in more detail? We can show you the filters when they are fast and with one extra setting that they become really slow. Maybe we overlook something and the changes are that you will see this right away.
Thanks!
Hi!
The suggestions are helpful. One of the fixes is to turn off 'dynamic recount' and 'hide empty terms' options. The filter is indeed fast when those options are disabled, but the website is also not working properly anymore.
Disable those options results in the filter returning many empty responses.
We want the filter to adapt to the previous selected filters (and stock). So when the color 'red' is selected, all other options, like a 'brand' that doesn't contain any product with the color red, needs to disappear.
Explaining the issue isn't easy. We've tried many different settings to make this work, but all out comes are either slow or not working as needed.
Is it possible to share our screen and explain the issue in more detail? We can show you the filters when they are fast and with one extra setting that they become really slow. Maybe we overlook something and the changes are that you will see this right away.
Thanks!
Quote from Pablo Borysenco on July 29, 2021, 12:48Hello
As I wrote to you above - https://share.pluginus.net/image/i20210729133754.png - if you use a weak server it is impossible to make the filter faster
If you want to hide empty terms, the filter must make a separate request for each filter element to get the actual quantity. If you have 1000 attributes, the filter will make an additional 1000 requests. You have 27000 variations - The filter must check each variation to check the stock status. And this is a heavy load on the server, and the only way not to make so many requests is to use caching.But that doesn't suit you. So you need to use a more powerful server
Hello
As I wrote to you above - https://share.pluginus.net/image/i20210729133754.png - if you use a weak server it is impossible to make the filter faster
If you want to hide empty terms, the filter must make a separate request for each filter element to get the actual quantity. If you have 1000 attributes, the filter will make an additional 1000 requests. You have 27000 variations - The filter must check each variation to check the stock status. And this is a heavy load on the server, and the only way not to make so many requests is to use caching.But that doesn't suit you. So you need to use a more powerful server