constructor warnings php 8.1

Hey there,

Thanks for reporting this and for including the exact warnings and environment details.

Could you please confirm whether you’re using wpDataTables Lite/free or the Premium version?

• If you’re on Lite, please ensure it’s updated to the latest version, 6.3.3.12.
• If you’re on Premium, the latest version is 7.3.2, so please confirm that this is the version installed on your site.

It would also help if you could send us a copy of your System Info from the wpDataTables dashboard so we can see your full WordPress, PHP, and server environment.

I’ll pass the PHP warnings you shared to our developers so they can check whether this has already been addressed for an upcoming update or, if not, create a task to fix it in a future release.

Just to clarify: these are PHP warnings only and should not affect the actual functionality of the plugin. Could you confirm that everything is working as expected on that page (table creation, etc.)?

We currently test wpDataTables with PHP 7.4 (minimum requirement since wpDataTables 6.0), 8.0, 8.1, and 8.2, and our internal tests also cover higher PHP 8.x versions. In some cases, if WP_DEBUG is enabled, you may see warnings or notices in the logs even if the plugin itself is working correctly.

For live/production websites, we generally recommend keeping WP_DEBUG disabled to avoid filling the log with non-critical notices.

Kind regards,
Milos

• This reply was modified 6 months, 3 weeks ago by Milos Jovanovic.

Hello,

Thank you for the follow-up and for confirming that the warnings are still present in version 7.3.3, while functionality remains unaffected.

In order for our developers to properly investigate and attempt to reproduce the issue, we will need a bit more information from your environment.

Please send us a copy of your System Info from the wpDataTables dashboard (you can find it under wpDataTables → System Info). This will allow us to review your full WordPress, PHP, and server configuration.

Once we have that, I will forward everything to our developers so they can:

• Try to reproduce the warnings under the same conditions
• Confirm whether this has already been addressed internally
• Or create a task for a future patch if needed

Additionally, please confirm whether WP_DEBUG is enabled on your site. If it is enabled on a live/production environment, we strongly recommend disabling it to prevent PHP warnings/notices from being logged or potentially displayed.

It’s perfectly fine to keep WP_DEBUG enabled on a staging or development site for testing purposes, but on live sites it’s generally best to keep it disabled unless actively debugging.

Looking forward to your System Info so we can proceed further.

Kind regards,
Milos

Hello,

Thank you for your detailed follow-up and for confirming the updated environment (PHP 8.3, WP 6.9.1, wpDataTables 7.3.3).

Based on the file path in the warning:

/wp-content/plugins/wpdatatables/templates/admin/constructor/steps/query_builder_parts/constructor_2_woo_commerce.inc.php

this is indeed originating from wpDataTables, specifically from the WooCommerce constructor step.

Since functionality is not affected and the warnings are only appearing in the debug.log, this appears to be a PHP 8.x compatibility issue (most likely stricter type handling in newer PHP versions, such as object vs. array access). We will escalate this internally to our developer team so they can review the code in that file and adjust it accordingly if needed.

Thank you for reporting it clearly — even non-breaking warnings are important to keep the codebase clean and fully compatible with newer PHP versions.

If you would prefer to continue this investigation in a private and fully secure environment (for example, if our developers need to ask for additional details later), you are welcome to open a ticket on our main support system by following this guide:

https://help.wpdatatables.com/en/articles/39-how-to-contact-support-with-your-premium-license

If you are using the free/Lite version, you can simply choose the “Pre-purchase question” category and reference this forum thread there. That ticket will be completely private and visible only to you and our team.

For now, I will escalate this internally and we will let you know if our developers need anything else from your end.

Kind regards,
Milos