Cant figure out the excluded terms id
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 dimitrisv on January 14, 2022, 06:24Do you have any suggestion to make to the tagdiv team regarding their incompatibility? I will be glad to pass it over so that you become compatible.
Do you have any suggestion to make to the tagdiv team regarding their incompatibility? I will be glad to pass it over so that you become compatible.
Quote from Pablo Borysenco on January 14, 2022, 13:43Hello
Unfortunately I have no ideas and don't understand why this plugin affects search queries.
You'd better write in support of a third-party plugin and ask to disable this functionality
Hello
Unfortunately I have no ideas and don't understand why this plugin affects search queries.
You'd better write in support of a third-party plugin and ask to disable this functionality
Quote from dimitrisv on January 15, 2022, 23:00OK. I wrote to them and will have a good look into it in order to make it fully compatible with yours.
I would be extremely obliged to you if you can check on the performance. We have to hide the irrelevant items choices, and in spite of all the caching etc. its performance is nowhere near your performance for related number of products as demonstrated here: https://demo10k.products-filter.com/
Hosting is Cloud Siteground with 10 CPUs and 10GB RAM... (than never reached this so obviously the bottleneck is somewhere else... ). WP Memory limit is set to 4GB
OK. I wrote to them and will have a good look into it in order to make it fully compatible with yours.
I would be extremely obliged to you if you can check on the performance. We have to hide the irrelevant items choices, and in spite of all the caching etc. its performance is nowhere near your performance for related number of products as demonstrated here: https://demo10k.products-filter.com/
Hosting is Cloud Siteground with 10 CPUs and 10GB RAM... (than never reached this so obviously the bottleneck is somewhere else... ). WP Memory limit is set to 4GB
Quote from Pablo Borysenco on January 17, 2022, 12:57Hello
Pay attention to the number of taxonomies! This is the main reason for increasing the load.
For dynamic recalculation, the filter must make a request for each taxonomy term.
it is not possible to extend the filter indefinitely without increasing requests, and each request takes some time
Hello
Pay attention to the number of taxonomies! This is the main reason for increasing the load.
For dynamic recalculation, the filter must make a request for each taxonomy term.
it is not possible to extend the filter indefinitely without increasing requests, and each request takes some time
Quote from dimitrisv on January 17, 2022, 13:16Pavlo one thing.
I thought that my adding the addon of restricting by categories - https://wordpress.org/plugins/woof-by-category/ -, the queries will be limited too for those attributes that are only valid for the particular category. But this is not the case.
The only thing that improves is the removal of the transient display of the irrelevant attributes (that are still computed). But the query executes for all say 70 attributes instead of the five attributes that are relevant to the category. I think it will be great if you can make your plugin to take into account the restrictions by the addon so that we can limit the requests.Another thing that may come to play is the "Regenerate the product attributes lookup table" that may needs to be taken into account.
Pavlo one thing.
I thought that my adding the addon of restricting by categories - https://wordpress.org/plugins/woof-by-category/ -, the queries will be limited too for those attributes that are only valid for the particular category. But this is not the case.
The only thing that improves is the removal of the transient display of the irrelevant attributes (that are still computed). But the query executes for all say 70 attributes instead of the five attributes that are relevant to the category. I think it will be great if you can make your plugin to take into account the restrictions by the addon so that we can limit the requests.
Another thing that may come to play is the"Regenerate the product attributes lookup table" that may needs to be taken into account.
Quote from Pablo Borysenco on January 18, 2022, 12:10Hello
But this is not the case. - it is better to contact the support of this third-party plugin
"Regenerate the product attributes lookup table" - Unfortunately I don't understand what you mean
Hello
But this is not the case. - it is better to contact the support of this third-party plugin
"Regenerate the product attributes lookup table" - Unfortunately I don't understand what you mean
Quote from dimitrisv on January 18, 2022, 13:06I will talk with the guy who did the add on for the WOOF for categories.
As for the Regenerate the product attributes lookup table I mean this setting:
https://1drv.ms/u/s!Akul2ygARwfdh5Vk5qD9fo2dUTWIRQ?e=6ooAIc
And its impact on performance
I will talk with the guy who did the add on for the WOOF for categories.
As for the Regenerate the product attributes lookup table I mean this setting:
https://1drv.ms/u/s!Akul2ygARwfdh5Vk5qD9fo2dUTWIRQ?e=6ooAIc
And its impact on performance
Quote from Pablo Borysenco on January 19, 2022, 12:44Hello
Regenerate the product attributes lookup table - It looks like a function of a third party plugin. I will pass this to the developers, but the problem is that we cannot bind to the functionality of third-party plugins
Hello
Regenerate the product attributes lookup table - It looks like a function of a third party plugin. I will pass this to the developers, but the problem is that we cannot bind to the functionality of third-party plugins