Hello David

Where can I take a look at this behavior? If you're loading all data in the filter (if it's a select-box or a check-box), it can either slow down the page load or break.

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.

Also, please make sure to tell me what the table ID is, so I know where to look.

Hey David

In this case, the issue is probably with the collation of those columns in the database.

Can you please provide me with database access credentials, again in a PRIVATE response? 

Hey David.

Thanks for that, but your security measures are blocking WP phpMyAdmin:

Is there a way you can either lift the block or provide us with a URL and login credentials for the database?

Hi David.

The ticketing system that we use (Ticksy.com) is currently going through some updates and we're facing issues with it as well.

We apologize for the inconvenience, but since this is a 3rd party application, we can't do anything about it. I hope you were able to submit the ticket after all, and if you have - we'll get back to you as soon as we reach it.

If not, please feel free to respond to this ticket with the topic added to the other one, and I'll gladly help you out.

Hi again David.

Can you please record your screen when trying to submit a new ticket, and we'll forward it to Ticksy's support team? Thanks in advance!

If your MySQL-query-based wpDataTable doesn’t work correctly with server-side processing, probably this is happening because the wpDataTables server has problems with parsing the query and building new queries dynamically. 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: 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, the server-side processing feature adds this part of the statement automatically when users trigger the sorting on the front end, and having it in the initial statement may cause the table to crash.

Remember that wpDataTables is a WordPress plugin for managing tables, not a database manager, so it can't perform the same as phpMyAdmin or similar tools.

Our logic is based on a PHP SQL parser which has full support for the SQL dialect for the following statement types

SELECT, INSERT, UPDATE, DELETE, REPLACE, RENAME, SHOW, SET, DROP, CREATE INDEX, CREATE TABLE, EXPLAIN, and DESCRIBE.

Some of them are disabled for security reasons.

Filtering, sorting, and searching may not work properly if you include:

• Accent graves ( ` ) around the table name
• JOIN functions
• UNION functions
• CONCAT functions
• sub-queries

These can also be solved by preparing a MySQL view, as mentioned above.