HI spounch,
Thank you for your purchase.

This is a small bug on our side which is fixed for the upcoming update of the plugin.

Can you please go in file wpdatatables/controllers/wdt_ajax_actions.php and on the last line below 

add_action('wp_ajax_wpdatatables_get_column_possible_values', 'wdtGetColumnPossibleValues');

add this line of code

add_action('wp_ajax_nopriv_wpdatatables_get_column_possible_values', 'wdtGetColumnPossibleValues');

Also you can set the Number of possible values to load of the select box ( attachment) 

If the cascade filtering is turned on then option All will be set as a default and it can not be changed.

Let me know the result.

Best regards.

HI spounch,
 

Can you please tell me which version of our main plugin and version of Powerful filters Add-on do you use.

The version of main plugin should be 2.2.2 and the version of Powerful filters should be 1.0.1

Best regards.

HI spounch,

To download the 2.2.2 version you can follow this guide

Please take a look at our documentation where you can see how you can successfully update the plugin.

You can follow this guide :

1.) Download zip from this link

2.) Use FTP to open /yourwordpressfolder/wp-content/plugins

3.) Delete existing wpdatatables folder.

4.) Upload previously downloaded wpdatatables folder through FTP to plugins folder (unzip it)

5.)  Go to WP-admin panel, open Plugins section.

6.) Deactivate wpDataTables, and then activate it again.

As for the Powerful filters the steps are the same except for the first step.

You will need to login to your Envato account and there you will have the link for downloading the latest Powerful filter Add-on file.

Best regards.

HI spounch,

Bogdan is on vacation so I will help you.

Please provide me a temporary WP-admin login 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 party. You can write credentials here just check Private Reply so nobody can see them except us.

Also point me on table id where you have this issue so can take a look

HI spounch,

Sorry for late response. 

We are located in Serbia and our working time is from 10:00 to 17:00 CET. business days.

I am glad that you found what cause the issue. Thank you for sharing you experience.

Best regards.

Hi spounch,

Yes the problem is when you use database name as prefix in query. All server side features like search, sort or filtering will not work properly if you use queries like this.

Hi spounch,

If your MySQL-query based wpDataTable doesn’t work correctly with server-side processing, probably this is happening because wpDataTables server has problems with parsing of the query and building new queries dynamically (happens rarely, but does sometimes). To avoid this please prepare a MySQL view (a stored query), which will return the data that you need, call it e.g. “view1” and then build a wpDataTabled based on a simple query like “SELECT * FROM view1″.

Please note some this when working with the server-side processing feature:

• Please do not use “LIMIT” in the SELECT statement. wpDataTables adds it automatically and it will be overridden.
• Please do not use “ORDER BY” in the SELECT statement. wpDataTables has its own sorting engine so it makes no sense to use MySQL’s sorting, since it will be overridden. Also server-side processing feature adds this part of statement automatically when users triggers the sorting on the front-end, and having it in initial statement may cause the table to crash.

Best regards.