With the new version any report with a calculated formula produce a critical error in the front end. In the wpdatatables-constructor the report shows fine and the calculated formulas are populated with no issues.
You can always go to the admin side where you edit the reports in the wpdatatables-constructor, scroll down and the report should work even with the calculated formula. You can export from this page normally.
I can confirm we are able to reproduce this bug, it only happens for version 6.5 - if we reroll to 6.4, the error goes away.
It is related to our Formula columns - they render on the back-end correctly, while the front-end tables throw that critical error.
For now, we will send the previous installation version to David here on a private message;
and as another temporary measure, you can try removing any formula Columns for now until we fix it.
@primalforce, as mentioned on your other ticket, if you need us to also send you the previous premium installation, you need to open a new private ticket and confirm your licence details there.
-
I will keep you posted on both tickets on updates from our end - our developers are looking into this right now.
// Include Hidden Column
if (is_file(WDT_INTEGRATIONS_PATH . 'hidden-column/wdt-hidden-column-integration.php')) {
require_once(WDT_INTEGRATIONS_PATH . 'hidden-column/wdt-hidden-column-integration.php');
}
Beneath that, add this :
// Include Formula Column
if (is_file(WDT_INTEGRATIONS_PATH . 'formula-column/wdt-formula-column-integration.php')) {
require_once(WDT_INTEGRATIONS_PATH . 'formula-column/wdt-formula-column-integration.php');
}
So in the end, that part of the code in its entirety should look like this :
Save the changes of the file, then purge cache on your site and refresh the Page with the table, it should be fixed.
Let us know how it goes.
If you need us to edit this code for you, we would need a WP Administrator user credentials along with FTP credentials.
And please send me an URL of a Page with the table so that we can test if it is solved.
If you send us access, please make sure it is in a PRIVATE Reply for security reasons, then only we can see the details.
Same goes for anyone else who comes across this ticket, if you apply this and it does not solve it for you, please open a separate PRIVATE ticket where you will send us the required access so we can try to apply this fix for you.
No problem at all, I am glad to see our developers managed to build this fix fairly quickly and it seems to be completely resolved for all the users who reported it.
If anyone notices any other/unrelated issue, please don't hesitate to open new/separate tickets, we will do our best to help.
Since updating to v6.5 this morning my tables are no longer being displayed on the front end of the website.
I simply get an error instead saying:-
There has been a critical error on this website.
I updated to the newer version 6.5 after there was a vulnerability on version 6.3.1 https://patchstack.com/database/vulnerability/wpdatatables/wordpress-wpdatatables-tables-table-charts-premium-plugin-6-3-1-unauthenticated-sql-injection-vulnerability
With the new version any report with a calculated formula produce a critical error in the front end. In the wpdatatables-constructor the report shows fine and the calculated formulas are populated with no issues.
Here is the error log:
2024-06-04T13:20:06+00:00 Critical Uncaught Error: Failed opening required 'class.formula.wpdatacolumn.php' (include_path='.:/usr/local/lib/php') in /dom14130/wp-content/plugins/wpdatatables/source/class.wpdatacolumn.php:874
Additional context
{ "error": { "type": 1, "file": "\/dom14130\/wp-content\/plugins\/wpdatatables\/source\/class.wpdatacolumn.php", "line": 874 }, "backtrace": [ "", "#0 \/dom14130\/wp-content\/plugins\/wpdatatables\/source\/class.wpdatatable.php(1663): WDTColumn::generateColumn('formula', Array)", "#1 \/dom14130\/wp-content\/plugins\/wpdatatables\/source\/class.wpdatatable.php(1832): WPDataTable->createColumnsFromArr(Array, Array, Array)", "#2 \/dom14130\/wp-content\/plugins\/wpdatatables\/source\/class.wpdatatable.php(3229): WPDataTable->arrayBasedConstruct(Array, Array)", "#3 \/dom14130\/wp-content\/plugins\/wpdatatables\/source\/class.wpdatatable.php(4373): WPDataTable->queryBasedConstruct('SELECT date, ut...', Array, Array, false)", "#4 \/dom14130\/wp-content\/plugins\/wpdatatables\/controllers\/wdt_functions.php(1400): WPDataTable->fillFromData(Object(stdClass), Array)", "#5 \/wordpress-versions\/6.5.3\/wp-includes\/shortcodes.php(433): wdtWpDataTableShortcodeHandler(Array, '', 'wpdatatable')", "#6 [internal function]: do_shortcode_tag(Array)", "#7 \/wordpress-versions\/6.5.3\/wp-includes\/shortcodes.php(273): preg_replace_callback('\/\\[(\\[?)(wpdata...', 'do_shortcode_ta...', '[wpdatatable id...')", "#8 \/wordpress-versions\/6.5.3\/wp-includes\/class-wp-hook.php(324): do_shortcode('[wpdatatable id...')", "#9 \/wordpress-versions\/6.5.3\/wp-includes\/plugin.php(205): WP_Hook->apply_filters('[wpdatatable id...', Array)", "#10 \/wordpress-versions\/6.5.3\/wp-includes\/post-template.php(256): apply_filters('the_content', '[wpdatatable id...')", "#11 \/dom14130\/wp-content\/themes\/storefront\/inc\/storefront-template-functions.php(352): the_content()", "#12 \/wordpress-versions\/6.5.3\/wp-includes\/class-wp-hook.php(324): storefront_page_content('')", "#13 \/wordpress-versions\/6.5.3\/wp-includes\/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)", "#14 \/wordpress-versions\/6.5.3\/wp-includes\/plugin.php(517): WP_Hook->do_action(Array)", "#15 \/dom14130\/wp-content\/themes\/storefront\/content-page.php(18): do_action('storefront_page')", "#16 \/wordpress-versions\/6.5.3\/wp-includes\/template.php(812): require('\/dom14130\/wp-co...')", "#17 \/wordpress-versions\/6.5.3\/wp-includes\/template.php(745): load_template('\/dom14130\/wp-co...', false, Array)", "#18 \/wordpress-versions\/6.5.3\/wp-includes\/general-template.php(206): locate_template(Array, true, false, Array)", "#19 \/dom14130\/wp-content\/themes\/storefront-wellness\/content-reports.php(20): get_template_part('content', 'page')", "#20 \/wordpress-versions\/6.5.3\/wp-includes\/template.php(812): require('\/dom14130\/wp-co...')", "#21 \/wordpress-versions\/6.5.3\/wp-includes\/template.php(745): load_template('\/dom14130\/wp-co...', false, Array)", "#22 \/wordpress-versions\/6.5.3\/wp-includes\/general-template.php(206): locate_template(Array, true, false, Array)", "#23 \/dom14130\/wp-content\/themes\/storefront-wellness\/template-reports.php(22): get_template_part('content', 'reports')", "#24 \/wordpress-versions\/6.5.3\/wp-includes\/template-loader.php(106): include('\/dom14130\/wp-co...')", "#25 \/wordpress-versions\/6.5.3\/wp-blog-header.php(19): require_once('\/wordpress-vers...')", "#26 \/wordpress-versions\/6.5.3\/index.php(17): require('\/wordpress-vers...')", "#27 {main}", "thrown" ]}
Attached files: fatal-errors-2024-06-04.log
Excellent, spot on, I did have a calculated column and removed it and lo and behold the table front end reappeared so thx for the quick fix for now !
You can always go to the admin side where you edit the reports in the wpdatatables-constructor, scroll down and the report should work even with the calculated formula. You can export from this page normally.
Hi guys,
I can confirm we are able to reproduce this bug, it only happens for version 6.5 - if we reroll to 6.4, the error goes away.
It is related to our Formula columns - they render on the back-end correctly, while the front-end tables throw that critical error.
For now, we will send the previous installation version to David here on a private message;
and as another temporary measure, you can try removing any formula Columns for now until we fix it.
@primalforce, as mentioned on your other ticket, if you need us to also send you the previous premium installation, you need to open a new private ticket and confirm your licence details there.
-
I will keep you posted on both tickets on updates from our end - our developers are looking into this right now.
Thank you for your patience.
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
Hello again guys,
We have a positive update from our developers, there is a temporary fix you can apply for the 6.5 Plugin version.
They will work to build the final version of this fix as quickly as possible.
If you wish to apply this temporary fix, please follow these steps :
Find this PHP file in our Plugin via FTP or your Hosting's File Manager ( or you can install a file manager Plugin), in this path :
../wp-content/plugins/wpdatatables/integrations/wdt-integrations-loader.php
around line 65 find this piece of code :
// Include Hidden Column if (is_file(WDT_INTEGRATIONS_PATH . 'hidden-column/wdt-hidden-column-integration.php')) { require_once(WDT_INTEGRATIONS_PATH . 'hidden-column/wdt-hidden-column-integration.php'); }Beneath that, add this :
// Include Formula Column if (is_file(WDT_INTEGRATIONS_PATH . 'formula-column/wdt-formula-column-integration.php')) { require_once(WDT_INTEGRATIONS_PATH . 'formula-column/wdt-formula-column-integration.php'); }So in the end, that part of the code in its entirety should look like this :
Save the changes of the file, then purge cache on your site and refresh the Page with the table, it should be fixed.
Let us know how it goes.
If you need us to edit this code for you, we would need a WP Administrator user credentials along with FTP credentials.
And please send me an URL of a Page with the table so that we can test if it is solved.
If you send us access, please make sure it is in a PRIVATE Reply for security reasons, then only we can see the details.
Same goes for anyone else who comes across this ticket, if you apply this and it does not solve it for you, please open a separate PRIVATE ticket where you will send us the required access so we can try to apply this fix for you.
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
Thanks Miloš for your reply. i will apply the patch temporarily.
Hello @primalforce,
You're welcome.
Let us know how it goes, you can write here or on the other ticket, as you wish;
we will keep following up with all the users who reported this.
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
Hi guys,
I am happy to report, our developers released a small update today which contains this fix in version 6.5.1.
Can you please update wpDataTables now and this issue should be fixed?
If you need help with the update, please follow our Guide from this article : Updating the plugin to the latest version.
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
Thanks Miloš for the update.
Hi primalforce,
No problem at all, I am glad to see our developers managed to build this fix fairly quickly and it seems to be completely resolved for all the users who reported it.
If anyone notices any other/unrelated issue, please don't hesitate to open new/separate tickets, we will do our best to help.
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