Hi Craig,

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.

-

Can you first please check which Version of wpDataTables you got installed?

If it is older than 6.1,   please update to the latest 6.1 version, then create a new Manual Table from the same Data ( Perhaps try to export this Table as Excel or CSV, if it has less than several thousand rows - you will just have to set "Show All Rows", because Server-Side Tables need that in order to pull all rows for export/then import this in a new Manual Table);

and check if the new Table now behaves OK for deleting and editing.

There was an issue in one of the older versions which was very rare, it only happened to couple of Users.

Can you please check it with these steps :

Log in your Database directly via PHPMyAdmin or any other DB Management Tool.

First check what is this Table's SQL Name, under Editing/MySQL Table Name.

Then, in your Database, find it under this TableName.

Now, check how the wdt_ID Column is configured.

It has to be "auto increment" , "not null", and the "default" set as "None".

For those Users, it somehow disabled the "auto increment' and it disrupted our Plugin's editing features on that specific Table, but when we changed that/it got fixed after that;

So let me know if that might be the case on your end?

And if you have the latest 6.1 version now, so in the future it should not happen again.

Thank you.

Hi Craig,

My apologies for replying so late again, I will raise the priority on this Ticket since you waited so long already and it is a serious issue.

At this point, I would like to take a closer look and inspect the Back-End Admin configuration as well as the SQL Database, in order to help you isolate the issue most effectively.

If you can, 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.