Hello Nasser.

Thank you for your purchase.

Can you, please show me that query?

Just make sure you enable the Private reply, so nobody can see it except for us.

Also, if at all possible, could 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.

Best regards.

Hello nasser.

I am sorry to disappoint you, but unfortunately something like this is not possible with the plugin's built in feature. One workaround would be to create a new column, where it would say "Group" or "Single" and use it in our tables.

Or, if only one timestamp is occupied at one time, you can enable row grouping for non-server-side tables and show the appointments for that time only.

I am sorry for the inconvenience.

Best regards.

HI nasser,

Aleksandar is currently on vacation so I will help you out.

The issue with the sorting is because of the query.

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.

HI nasser,

You are welcome.

Best regards.