Hello Shay

Thank you for your feedback, we'll forward it to our developers.

You cannot add a predefined filtering value because of cascade filtering being turned on. The logic of the plugin doesn't allow predefined filtering values while this is enabled since the filters follow the previous filter and the plugin can't anticipate if the predefined filtering value will appear after another filtering value has been selected.

Our developers will work on this in the future, but I can't say for sure when it is planned to include predefined filtering for cascade filtering.

The "Free" logic works exactly as it's supposed to work, and you can test it on our Powerful Filters sandbox site. For example, on this table, you can change the logic from "Left to Right" to "Free" and select "Barcelona". The previous (country) filter won't allow you to select any other country except for Spain:

Hi again Shay

As you can see in my previous response, I was not able to replicate this issue.

Can you please record your screen, showing us this behavior on your end?

Hi again Samuel.

I just responded to the other ticket: https://tmsplugins.ticksy.com/ticket/3022245

We'll forward this issue to our developers, and I'll get back to you on that other ticket as soon as I hear from them.

Sorry for the delay.

Samuel, I just want to let you know that our developers have this logged as a bug, and they are working on a fix. It should be included in the next update.

I sincerely apologize for this - I haven't tested the Multi Select-box while testing the Free cascade filtering. A human error on my end.

You're welcome again, Sam.

Thank you!

Hello again Samuel.

The bugfix will be included in our changelog once it's live, so you can keep an eye on it. Also, you can subscribe to our newsletter, so you're informed about new features, bug fixes, freebies, etc.

Hello Samuel

This has been working normally before, and it does still work for other filter types, just not multi-select. So, it's a bug with multi-select, not a missing functionality (since it does function with other filter types).

Our developers are working on a fix, and it should be included in the next update.

Until then, you can fix the issue on your site, so it works normally with multi-select also:

Go to wp-content/plugins/wdt-powerful-filters/assets/js/wdt.pf.frontend.js and on line 581 replace this line:

return $filter.find('select.wdt-multiselect-filter').selectpicker('val') !== null;

With this:

var multiSelectSelected = $filter.find('select.wdt-multiselect-filter').selectpicker('val');
if (Array.isArray(multiSelectSelected)) {
    return multiSelectSelected.length;
}
return multiSelectSelected != null;

After you save the file, make sure to purge all cache on your server, and test the behavior again.

Please note that this is still in the testing phase, so there's a possibility it still doesn't work for all possible use cases. It should, but we can't guarantee that yet.