Hi, Corey.

Our developers have identified the root of this bug,

that does not correctly render special characters such as the percentage sign for filtering in multiselectbox filters.

They are working on building a permanent fix for this,

but it is a very difficult bug,  so it will take some time until they test everything to ensure that the new fix does not negatively affect any other plugin functionalities before they add it to the plugin's core.

They will do their best to make it as soon as possible, but i can't promise a realistic ETA on it.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

We will make a patch Note about that fix there, when it is finished/added to the plugin core.

-

In the meantime, here is a temporary JS fix that you can copy to overwrite the file on your FTP in the plugin files.

( You can either use FTP or your Hosting's File Manager)

The path to overwrite the file should be :

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

and please make sure to disable 'Use minified wpDataTables Javascript' in the main plugin settings/Custom JS and CSS:

Until our developers implement a fix to the plugin's core,

you would have to repeat this "overwrite" step each time you update the plugin.

Let me know when you apply this fix does it work correctly for you, please?

It is working on our testing environment, we tried a lot of different scenarios, so it should work for your installation as well - but we can't guarantee that it will be perfect until you try it to be sure.

Thank you.

Hi, Corey.

Yes, unfortunately, this is a difficult bug,  so it will not be fixed in the next update i would say.

Most probably it will take some time before it is completely fixed.

The JS fix file has solved most of the special characters for some users - it does not work perfectly for everyone;

that is one of the reasons why our devs and QA Team are working to test everything to make sure it works correctly for everyone before they add it to the plugin's core;

and additionally some special characters are not resolved yet, we wish to solve all of them to have a proper fix, etc.

-

If you wish, i can overwrite this file for you, it is not a problem at all,

i just need the credentials to access the FTP of the hosting server.

I use the FileZilla FTP client, so i would need Host ,  Username,  Password and the Port Number,

and i can overwrite this for you.

It will be good if i have Wp-Admin access as well , so that i can check the changes made by the file;

and to make sure everything is safely working.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

And if you can point me to this table ID from the screenshots,please.

Thank you.