Hello,

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.

We are unable to reproduce any issue with the date editing or date filtering.

Can you please record your screen and send us a short video that demonstrates how the issue happens?

If the video shows any sensitive data, mark the reply as PRIVATE .

If you can then also send us remote access.

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.

And point us to the table id.

Thanks.

Hi Barnabás,

I have good news.

Our developers made the first version of the Fix for the Date Picker bug.

We will most probably add this fix to the next Update - but I can't guarantee it yet, since we need more testing on it.

I am sending you the file here as an attachment and will advise you on how to upload it to your FTP.

So, first update the Plugin again to the latest 6.2.1 Version.

Then, access your FTP/ or Hosting File manager, and inside your WordPress Folder, find this JS file:

..\wp-content\plugins\wpdatatables\assets\js\wpdatatables\wdt.funcs.js

Unzip the file i sent and upload it to overwrite the existing file there.

After that, purge cache of your Site and try - let me know if that fixes the Date Picker on your end.

It works on our Test Sites.

If it does not work, we can try to fix it for you from our end ;

If you need us to do that remotely, please provide me a WP-admin (administrator) user for your website where this happens, 

as well as FTP credentials;

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.

Let me know how it goes and if you need us to remote in.

Thanks.

Hi Barnabás,

I am delighted to hear that this JS fix works now after deactivating the 'minify JS' option.

My apology for missing to tell you that right away - I should have pointed it out with importance as well as clearing cache to avoid having any 'old cached page version' active.

After any major change, it is always best practice to do one 'cache purge'.

 Thank you for letting us know. 

If you notice the issue reoccur at any time, let us know, but I am confident it should stay fixed this time.