Hello ashman

How is the table created? Is it maybe an SQL query based table?

If it is, please make sure that, in the editing tab above the table, the ID column for editing is set properly. It needs to be an integer, auto-increment column in the database.

Hi again ashman.

That also depends on the query you're using.

If you're pulling columns from a single table, you shouldn't use accent graves.

From version 2.3 we've implemented a feature that you can use multiple separate DB connections for MySQL, MSSQL and PostgreSQL. For MySQL engine we are dynamically adding the accent grave ( ` ), so there's no need to use it around the table name in the query. If you were to delete them, searching and filtering should work just fine.

Also, if you have a semi-colon ( ; ) at the end of your query, that could cause the issue as well.

If you have a more complicated query, 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 trigger the sorting on the front-end, and having it in initial statement may cause the table to crash.