Hi Daniel,

Can you tell me what is the Table type, is it an SQL Query based table as from the other ticket;

if so - are you calling that table from the local WordPress Database - or is it being called from an external DB?

This error text seems to be pointing to a filter type on some column, so can you try to recall more details, was this table originally working when you first created it?

Is it possible you changed a filter type for a specific column, then hit "Save Changes" on the table when this error started coming up, or something similar like that?

If so, try to retrace the steps - what was the original filter type, the column type - and what change you made when the error happened, if you can retrace it?

Would it be possible if you can make the same table again from same data source, then try to redo the same steps, to isolate it?

It will help us to know as many details as possible to try to isolate the issue.

Can you also check do you have the latest Plugin version 6.5.3 installed or an older one?

If you have the latest one, are you using any add-on on this table?

If so, can you check what are the add-on versions installed - for example the Powerful Filters latest one is 1.4.5.

You can check all the latest versions for wpDataTables on the ChangeLog Page.

For the add-ons, just click in each respective tab above and you can check them, too.

The ideal approach would be if you can recreate the same table and try to re-do the steps when the error happens while catching it on Video and send it to us, then our developers can isolate it quicker.

If you can't isolate the issue on your end - our developers can try to take a remote look;

For that, we will need full access as advised on the other ticket :

Please provide me a temporary WP-admin (administrator) user for your website where this happens, 

as well as FTP credentials and access to the database ( either link with credentials for PHPmyAdmin, or access to Hosting Panel),

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.

And confirm the Table ID, please.

Thank you.

Hi Daniel,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

No problem about merging between tickets, as long as we determine them and focus on one in the end when they have the same subject.

In regards to the debug output, thank you for this update and clarifying more details what might have happened before these errors started happening.

1. You mentioned the error might have happened after you dropped a column from an SQL Query based Table - and the data is called from an external PostgreSQL DB, right?

That is not the expected behaviour - you can call any columns you wish from the source Table.

For example, if I have a table in my Database which has 10 columns, but I only want to call 3 columns, we can do :

SELECT ColumnA,
ColumnB,
ColumnC
FROM TableName

Or, if we first called 4 columns like :

SELECT Column1,

Column2,

Column3,

Column4

And we decide to drop one from the Query, like change the Query now to :

SELECT Column 1,

Column 2,

Column 3

Then hit "save Changes" on the Table, there should not be any errors.

Only, for example, if you had Editing enabled, and if you choose an ID /integer Column for Editing;

and then you drop it from the Query - that could cause an issue, because if you allow editing in a Table and remove the editing ID column from this Query then "save changes", that could break the editing logic;

but here the error is pointing to 'setting a specific filter type' - so maybe you set some specific filter on that column which got removed from the Query and that caused this;

but we are still unable to reproduce it - So we will need your help to continue isolating it on your Site.

Would it be possible if you can try to re-create the same SQL Query as before;

then record your Screen and try to do the same steps as before, see if you can 'catch the issue' happening?

If so, that can help us determine exactly which steps you did/ if you set some specific filter on that column, and then how the Query looks in the step when you remove it and hit "Save Changes" - i presume that is the moment when the issue starts happening.

If the Video shows any sensitive data, please flag the reply as a PRIVATE message, then only we can see it, for safety.

Or if it gets too large as the attachment, upload to weTransfer and send me a download link.

Thank you.