I would be grateful to assist where we are facing major problem, where charts are not displaying correctly and when we investigated we receieve an error.
please find attached screenshots and the error for your reference.
note that we tried PHP 7.4, 8.0 and 8.2 and all the same error. we reinstalled 6.7.1 and also the same. please help.
This error is being thrown from the source Table, which the chart is pulling its data from.
JSON errors usually occur if you have a security plugin installed, or there's a security measure blocking admin-ajax calls.
Also, if the pages are cached, it can occur. Try excluding pages where you have our tables loaded from being cached, and try again.
If there's a notice, warning or fatal error WordPress that manifests through responses. Our table requires a valid JSON in the response, so if there are these notices, the JSON is not valid, and the data is not being loaded.
In most cases like this, it turns out that the table uses our server-side processing, if we combine that with any caching on a Page - the issue happens.
So let me know are you maybe using a Manual Table, or an SQL Query table with server-side processing enabled, as the table source of this chart?
And if you have caching active on the Page.
We will advise more on that specific issue and how you can solve it.
We currently have this issue which only happens for server-side processing tables when you have caching active on the page.
Our developers are intensively working to resolve this issue, as soon as possible. I can't say an ETA on it, unfortunately.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
For the time being, the only two possible solutions will be:
1. To disable caching only for pages where you have the tables, or perhaps disable caching entirely, if possible.
Most caching Plugins have the option to add URL's that will be excluded, so if possible, see if you can add the Pages with tables there, and that should solve it for now.
2. Or you can try disabling the server-side processing option in your Table.
but you can make a new SQL Query based table from the same data which is stored in a Manual Table.
This is how that is done.
First, check what is the MySQL Table name inside the Editing settings,
then make an SQL Query like :
SELECT * FROM TableName
For any SQL Query based Table which has less than 2 thousand rows, you can disable the server-side option on SQL tables, and it will work like it does for tables linked from files. ( loads all rows on the browser regardless of table's pagination)
If you need to increase the row count while still having the "toggle" to disable server-side,
Please go to ../wp-content/plugins/wpdatatables/source/class.wpdatatable.php and around line 3188 you'll see this:
if (is_array($res_dataRows) && count($res_dataRows) > 2000) {
The lines of code can change during Updates because our Developers add new lines from time to time, so it is best to search for the line in any Code Editor with CTRL+F to get the right line.
You can change the number 2000 to a value bigger than the number of rows in your table in order to still have that 'toggle option' for server-side processing.
In this file, please search for this, there should be two occurrences, first one around line 82 as :
if (count($wpDataTable->getDataRows()) > 2000) {
And second one around line 143:
if (count($wpDataTable->getDataRows()) > 2000) {
That will increase the server-side processing option automatic limit.
We just advise caution not to increase that number 'too high' to avoid going over the limit what your Hosting Server's PHP Limitations can handle.
Usually, up to around 5 to 6 thousand rows should pose no significant performance issues, but if you go higher than that data size without server-side processing, you could experience slow loading times.
You can certainly test to see how a Table behaves on front-end, and if it loads too slow/or freezes the browser's Page, you can go back in the Table's Back-End and enable server-side processing for that Table.
Let us know how it goes and if you have any questions.
I am delighted to hear that this has been resolved. Thank you for letting us know. Anything else that we could assist with, please don't hesitate to create new tickets.
Hello Support
I would be grateful to assist where we are facing major problem, where charts are not displaying correctly and when we investigated we receieve an error.
please find attached screenshots and the error for your reference.
note that we tried PHP 7.4, 8.0 and 8.2 and all the same error. we reinstalled 6.7.1 and also the same. please help.
Attached files: Screenshot 2024-10-29 181707.png
Screenshot 2024-10-29 181523.png
Screenshot 2024-10-29 181629.png
Good Day
kindly may you assist...
we have an issue and we are stuck. should we go back to previous version ? what should we do?
Regards
Hi Joe,
This error is being thrown from the source Table, which the chart is pulling its data from.
JSON errors usually occur if you have a security plugin installed, or there's a security measure blocking admin-ajax calls.
Also, if the pages are cached, it can occur. Try excluding pages where you have our tables loaded from being cached, and try again.
If there's a notice, warning or fatal error WordPress that manifests through responses. Our table requires a valid JSON in the response, so if there are these notices, the JSON is not valid, and the data is not being loaded.
In most cases like this, it turns out that the table uses our server-side processing, if we combine that with any caching on a Page - the issue happens.
So let me know are you maybe using a Manual Table, or an SQL Query table with server-side processing enabled, as the table source of this chart?
And if you have caching active on the Page.
We will advise more on that specific issue and how you can solve it.
We currently have this issue which only happens for server-side processing tables when you have caching active on the page.
Our developers are intensively working to resolve this issue, as soon as possible. I can't say an ETA on it, unfortunately.
You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;
and our newsletter, so you're informed about new features, bug fixes, freebies, etc.
For the time being, the only two possible solutions will be:
1. To disable caching only for pages where you have the tables, or perhaps disable caching entirely, if possible.
Most caching Plugins have the option to add URL's that will be excluded, so if possible, see if you can add the Pages with tables there, and that should solve it for now.
2. Or you can try disabling the server-side processing option in your Table.
For the Manual Tables, it is not possible to disable server-side processing,
but you can make a new SQL Query based table from the same data which is stored in a Manual Table.
This is how that is done.
First, check what is the MySQL Table name inside the Editing settings,
then make an SQL Query like :
For any SQL Query based Table which has less than 2 thousand rows, you can disable the server-side option on SQL tables, and it will work like it does for tables linked from files. ( loads all rows on the browser regardless of table's pagination)
If you need to increase the row count while still having the "toggle" to disable server-side,
Please go to ../wp-content/plugins/wpdatatables/source/class.wpdatatable.php and around line 3188 you'll see this:
The lines of code can change during Updates because our Developers add new lines from time to time, so it is best to search for the line in any Code Editor with CTRL+F to get the right line.
You can change the number 2000 to a value bigger than the number of rows in your table in order to still have that 'toggle option' for server-side processing.
Another PHP file in this path :
../wp-content/plugins/wpdatatables/source/class.wdtconfigcontroller.php
In this file, please search for this, there should be two occurrences, first one around line 82 as :
And second one around line 143:
That will increase the server-side processing option automatic limit.
We just advise caution not to increase that number 'too high' to avoid going over the limit what your Hosting Server's PHP Limitations can handle.
Usually, up to around 5 to 6 thousand rows should pose no significant performance issues, but if you go higher than that data size without server-side processing, you could experience slow loading times.
You can certainly test to see how a Table behaves on front-end, and if it loads too slow/or freezes the browser's Page, you can go back in the Table's Back-End and enable server-side processing for that Table.
Let us know how it goes and if you have any questions.
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thank you so much for getting back to me. We will go through your feedback and get back to you the soonest.
Hi Joe,
You're welcome, I am happy to help.
Let me know how it goes when you check everything as advised, we will be here if further assistance is needed.
Thank you.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Thank you so much, we followed your advise and we successfully fixed the issue. :)
Hi Joe,
I am delighted to hear that this has been resolved. Thank you for letting us know.
Anything else that we could assist with, please don't hesitate to create new tickets.
Have a great day! :)
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables