Hello Thomas

The plugin has been tested with WP 5.6, and everything is working fine. All tables on our documentation are live tables, and our website has been updated to 5.6 last week. It's all working fine.

Can you try deleting all cache from your website, and also deactivate and activate wpDataTables?

If that doesn't work, please provide me a temporary wp-admin user (administrator), and tell me which tables are affected, and I'll see if there's anything I can do.

Please note that this is a public ticket, so make sure you enable the PRIVATE response when you leave us credentials.

Hey Thomas

I logged in, but I couldn't replicate the issue on your website. I checked the home page (where you have 3 wpDataTables) while logged in, and from Incognito mode, but the errors never appeared.

The page was refreshed around 20 times, but the errors never appeared. Can you tell me on which page I can replicate this?

Thanks for the instructions, Thomas, I was able to replicate the issue this time.

However, I can't determine what's causing this, so I forwarded the ticket to one of our developers for testing.

As soon as I hear back from him I will let you know.

Hi again Thomas

Our developer couldn't be sure about this, but he believes that because of a lot of requests on the page (in some cases there are over 1.000) tables with these IDs are not removed.

As far as we can see, you're using an SQL query based table with placeholders. Depending on what's clicked on, those parameters are being forwarded to VAR and new tables are being rendered.

He tried adding datatables full, for debugging, but couldn't save the settings because of an error on one of your separate DB connections. Can you please fix the separate DB connections, and turn off the minify option in wpDataTables settings/Custom JS and CSS tab, so we can continue debugging?

I'm not sure about that, Thomas, so I forwarded the ticket to one of our developers.

As for remote connections - there's a bug with Chrome (possibly with other browsers as well), that the data of the currently logged-in user (username) is being automatically added to the credentials for the separate connection. If that happens, the error will occur. 

It's strange because you don't see any errors when you test the connection, so it could be an issue on our end. We'll try again, and let you know.

Hello again Thomas.

We were able to verify that wdt.frontend.min is being loaded after every click; after every page reload, but we're not sure why it's doing that. The warning has been excluded from the script, so it did not appear after that, but your website is really slow. Are you maybe on a shared hosting?

If you plan on having a lot of traffic (users) on this website, it will most likely break frequently, so our advice is to look for a better hosting plan.

Hi again Thomas

It's good to know that you're moving to a new server.

I checked your website yesterday and today, but I couldn't replicate the issue. It could be that the cache is stored on your browser, and it needs to be cleared, but this is probably related to server's performance.

I strongly believe that you won't be facing these issues once you move to a new hosting.