Hi carl,

You are right, this is our current default behaviour for any dropdown filtering.

If we choose some value and the table is now filtered by it - when we return to that column's filter, now the dropdown allows that 'empty value' to give the user the ability to reset/clear this filter.

At the moment, it is like that, but I will speak with our developers to see if we currently have any code workaround to completely remove that empty value in that situation, or if not, if we can add a task for them as an improvement for the future.

As soon as we check this, I will report back right away.

Thank you for your patience.

Hi carl,

I have an update about this bug.

This only happens in case if you set "Number of possible values" to any fixed/limited number.

If you change this to "All", then the bug will not happen, this can be a temporary workaround fix.

Can you please try this - if you don't have too many possible unique values for your String columns - such as more than 100 possible values and let me know if that fixes it for you?

If you have a lot of possible values, that could slow down the load, but let me know how it goes.

Thank you.

Hi carl,

Good news, we have an update from our Developer Team. They already made a fix, it just needs to have further testing before it gets implemented in an update.

It should be added in the next update but we can't guarantee it. If not, it will most probably be added in the update after the next one.

You can certainly first try the method i explained, basically just set the "All" for the "Number of possible values" in the Column data settings and if you don't notice any performance issue, that can work as a temporary workaround.

Or if you notice any performance issue, here are the steps to fix it :

Please find this JS file in our Plugin files, in this path :

../wp-content/plugins/wpdatatables/assets/js/wpdatatables/wdt.columnFilter.js

And around line 994, comment or delete this part :

data.unshift({value: ''});

Save the change and now it should be fixed.

If you wish us to do this for you, we would need WP-Administrator user credentials and FTP credentials in order to remotely edit our code and test it for you.

Let me know how it goes and if you have any questions.

Hi carl,

I am glad to see this worked as a temporary workaround.

We should have this bug fixed in one of our upcoming updates. It will be noted on the changeLog. You can certainly keep using this method if you don't see any slow load/performance impact on your table(s), too.

If anything else comes up, please don't hesitate to reach out to us.

Thank you.