Hi, Lucas.

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 please send me an URL to see the page with this issue?

And if we can see the back-end setup.

Please provide me a temporary WP-admin (administrator) user 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 parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Hi, Lucas.

Thank you for pointing out to another example.

I will go through them with our QA Team as soon as possible, and we will send all details to our developers to work on building a fix for this bug.

Thanks again for reporting this and for providing examples of the behaviour.

 We still don't have an ETA on when the fix will be available, but please keep a lookout on our wpDataTables changeLog.

Hi, Lucas.

Just wanted to follow up on this.

I checked again on the status, and our developers confirmed that they are actively working on fixing this bug.

We still can't promise an exact ETA when it will be fixed, but i hope they should be able to add a fix to one of the upcoming Updates, as soon as possible.

Thanks again, and of course, please don't hesitate to open other tickets if anything else comes up in the meantime.