Hello Thomas.

I checked the page a few times today and it loaded every time. This is the only chart that I see:

Is it the only one on the page, and is it correct?

I have refreshed the page at least 20 times, purged cache in my browser, checked multiple times today (as mentioned above), but it loaded every time.

Has the issue been resolved in the meantime or does it still happen from time to time?

Hello again Thomas.

We've just released wpDataTables 5.7, so please try updating the plugin. After you do, purge all the cache from the site and test again.

Let me know if that helped.

Hi again Thomas.

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.

Thank you Thomas.

When I log in and take a look at the table from which this chart is created, it appears blank:

Also, that's a pretty complex query for a 3rd party PHP SQL parser, which is probably why the table returns no rows.

Please try preparing a MySQL view (a stored query), which will return the data that you need, call it e.g. “view1” and then build a wpDataTabled based on a simple query like “SELECT * FROM view1″.

Please note:

• Please do not use “LIMIT” in the SELECT statement. wpDataTables adds it automatically and it will be overridden.
• Please do not use “ORDER BY” in the SELECT statement. wpDataTables has its own sorting engine so it makes no sense to use MySQL’s sorting since it will be overridden. Also, the server-side processing feature adds this part of the statement automatically when users trigger the sorting on the front end, and having it in the initial statement may cause the table to crash.

Let me know if that helps.

Thanks, Thomas.

The page I'm being redirected to (https://www.trachtanalyse.com/?honig=musterhonig-2) is actually post ID #2874, so I confirmed that returns data without issues (in the table).

This may be interfering with HighCharts loaded by wpDataTables:

Can you please create a new blank page and add [wpdatachart id=2] that we created?

Let me know if that's being displayed correctly. If it is, can you clone your website?

If yes - I'll ask you to install the Duplicator plugin. It will generate a couple of files that you can send me (along with the log-in credentials), and then I can create an exact copy of your website, see what the issue is and try to resolve it.

The Duplicator plugin can export only up to 500MB of data, so if your site is bigger than that, please use the All-in-One WP Migration plugin.

Please note that the files will be too large to attach to the ticket, so you can upload them via wetransfer.com and just send me the link.

Also, please note that this is a public ticket, so make sure to enable the PRIVATE response when sending me your data.

Hi again Thomas.

When I log in with the demo user, and check the page I don't see anything but once I refresh the page, the chart shows:

There could be a script that's loading before the chart and is blocking it.

Our developers asked if you can send us the duplicated website as mentioned in my last response, so they can troubleshoot it?

Just remember to send us a PRIVATE response.

Thank you, Thomas.

I forwarded the link to our developers, so they can check it out.

I'll get back to you as soon as I hear from them.

Hi again Thomas.

Sorry for the delay. Our developers found some bugs in the latest version of wpDataTables and they are working on resolving them.

A new update should be released during the week (maybe even today), and I hope this issue will be resolved as well. If not, I'll ask them to check it out again.

I truly apologize for the delay.

Hi again Thomas.

Can you create a Test page without the QR code that's present on https://www.trachtanalyse.com/?honig=musterhonig-2 and see if the behavior remains the same? Those scripts seem to be the only difference between a logged-in and a non-logged-in user, so maybe one of those scripts is overwriting wpDataTables.

I just heard from our developers, and they said that your case is isolated, so they weren't able to replicate it. Thus, there's no fix that will be included in the upcoming update, but they are continuing to troubleshoot the issue.

Thanks for reminding me, Thomas.

I can't replicate the issue anymore, though. See the video attached to my response.

I'm still waiting for our developers to inform me what's going on with the duplicated site.

Understood, Thomas.

I asked our developers to inspect this further and I'll get back to you when I hear from them.

Hi Thomas,

Aleksandar is on a Vacation so i will take over this case.

Firstly we would like to sincerely apologise for all the time that passed since our latest reply.

There was a communication error within our Team,

which is extremely rare to happen,

but still, we don't wish to make any excuses,  we acknowledge the mistake and going to do our best that it doesn't happen again.

In the meantime, our QA Team was able to reproduce this issue.

We can confirm this is a bug from our end.

The issue is that the redirection from one Post to another does not work as expected,

and our Plugin takes the value from the previous Post since that is the current logic when we use custom_post_id placeholder.

Our developers isolated the bug, and they'll add it to their queue for fixing.

 They will do their best to build a fix as soon as possible.

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

It will be stated there during updates which bug fixes have been implemented at each update.

We apologise once again for this internal communication error that caused such a delay between our response times.

Thank you very much for all your patience and cooperation on this issue.

If the developers manage to build a fix in between two Updates, we will make sure to come back to this ticket and send it to you.

Hi Thomas,

Just wanted to follow up on this issue - Our developers created a working fix, our QA Team is just additionally testing it.

It should be released in the following update - so please keep a lookout on our ChangeLog and when you do the next version update, please check if this is fixed for your chart.

If you still see an issue after the next update - please contact us and we can take a closer look.

Thank you.