HI Maxim,
Thank you for your purchase.

There are the options to choose the look of the table by using limit table width or Scrollable option, more information on this link from our documentation.

As for the common filter for both , unfortunately something like this is not possible with the plugin built in features at the moment.

Each table will have their own filters.

Best regards.

Hi Maxim,

You can only choose between Limit table width or Scrollable option at the same time, both features can not work at the same time.

The charts have the option Follow table filtering which allows the use case that you mentioned below which is a built in function in our plugin.

But 2 separate tables can not use one same filtering on the same page.

I will add your suggestion on our TODO list and we will discuss within our team and hopefully add it for some future releases of the plugin, but at the moment this is not possible.

Best regards.

Hi Maxim,

You are welcome.

Best regards.

HI Maxim,

To transpose the table our suggestion is to use PIVOT in the MySQL query.

But please keep in mind that if the query is to complicated our suggestion is to make 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 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.

Best regards.