Hi Jenna,

we apologise for this inconvenience.

Our developers are aware of this PHP warning and they made a fix.

Our QA Team is just conducting further testing to ensure that the fix does not have any other negative effects before our devs implement this in the Plugin's core.

It should be added within the next couple of Updates,

but we cant guarantee an exact ETA yet.

Best will be to keep a lookout on our wpDataTables changeLog.

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

-

For the time being, here is what you can do to fix this.

Please find this PHP file inside our plugin files,

you can access it via FTP on your Hosting server, or via the Hosting's File Manager, in this path :

..\wp-content\plugins\wpdatatables\source\class.wdttools.php

on line 1357 find this :

return $body && isset($body->info) ? unserialize($body->info, ["allowed_classes" => false]) : false;

replace it with this :

return $body && isset($body->info) ? unserialize($body->info, ["allowed_classes" => [stdClass::class]]) : false;

and this should remove the PHP warnings.

Let us know how it goes.

And just to note, if our developers don't add the final version of this fix in the next Update,

you would have to repeat this code edit again when you update the Plugin.

Let us know if you have any questions, we will be here if any assistance is needed.

If you need us to edit this code for you,

we will need access to your WP-Admin, please send me URL with Admin credentials,

and FTP credentials.

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 because this ticket is private and nobody can see them except us.

Thank you.

Hi Jenna,

I just wanted to follow up to let you know we released a small Update 5.8.2  which includes a fix for those PHP warnings,

so if you can please Update wpDataTables and that should be fixed.

2. In regards to some other deprecated warnings for PHP 8.2,  if you have that installed on your Hosting Server,

we are still not fully compatible for PHP 8.2 ,

but our developers are almost finished with that.

A new Update will launch in couple weeks,  and the optimizations for PHP 8.2 should be implemented by then.

Our QA Team is just still testing everything to ensure it can be safely added to that Update,

so we can't guarantee with 100% certainty, if the full PHP 8.2 optimizations will be added in the next one, or the Update after that.

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.

-

Right now, we are fully optimized for 8.1.13 on our Development Testing,

and we can confirm that there are no functionality issues,

just some warnings and notices are possible to happen if you have WP DEBUG enabled.

( Of course, for production version of websites, the WP DEBUG should be disabled);

-

Please don't hesitate to reach out to us if you have any questions or if you notice any other issues.

Thanks.