Hello Craig.

Thank you for your purchase.

There are actually a few things that could go wrong here.

Let's say you created a simple query:

SELECT * FROM `my table`;

1. There may be a security issue with the asterisk ( * ) being in the same row;
2. There may be an issue with a space in the name of the table;
3. Using accent graves ( ` ) can also trigger this behavior;
4. You don't actually need the semi-colon at the end ( ; )

So, your query should look like this:

SELECT
* FROM my_table

If at all possible.

There are a few more things that would render the filters and search not to work, but I'd have to take a look at your query.

Can you share it with me? Also, if it contains any sensitive data, please make sure to enable the PRIVATE reply, so it is visible only to us.

Best regards.

Hi again Craig.

Try this:

SELECT
        ID,
        firstname,
        surname,
        department,
        position,
        location,
        extension,
        mobile,
        ddi
FFROM PL

Please let me know if it works.

Best regards.

Hi again Craig.

In that case, I believe the best way to go about this would be to create a VIEW.

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 (rarely happens, 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 wpDataTables 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.

Best regards.

Hi again Craig.

Well, I must turn back to my first reply again.

I told you about asterisks ( * ), accent graves ( ` ) and semi-colon ( ; ). So, can you try the query like this:

SELECT
* FROM view1

and see if it works then?

If not, 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.

Best regards.

You're welcome Craig.

Glad I could help.

If you have any further questions or issues, please feel free to open a new ticket, and we'll gladly help.

Best regards.

Hello again Craig.

The Ajax call errors are usually linked to security issues, since the call cannot be returned.

Can you share the page with me, so I can inspect it and see what it returns?

Best regards.

Hello Craig.

In that case, it has something to do with your site permissions. Do you have mod_security enabled, or some security plugin that can block the call being made if you are not logged in?

Unfortunately, Skype, Team Viewer, Zoom and similar means of support are not available.

Best regards.

You're welcome Craig.

Anyway, I'd look into permissions on your website. There must be something blocking non-logged-in users from accessing the table.

Best regards.