Hi!
The deprecation notice you are seeing is caused by a minor issue in the code that can potentially become a problem in the future. Most plugins have these issues with code, but you shouldn’t be seeing that message from either of them because this message is intended to be shown to developers.
It’s possible that some part of the code is enabling WordPress debug mode, and this is why you’re getting this message on the screen. Here are some examples of how the debug mode can be enabled.
It’s also possible that the server that hosts your site is configured to show these notices by default, but if you haven’t made any changes to it’s configuration, it’s unlikely to be the cause.
Hi @chefboyadee
You’re seeing the warning message because your booking plugin has error reporting turned on. Those deprecated warnings don’t actually affect the site in anyway. It’s just that the code may become deprecated in future versions of PHP and stop working.
I’m not sure why your booking plugin has the error reporting turned on, you may need to contact them to see if there is a way to turn that off.
Hello @chefboyadee,
It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!
Hello,
I am experiencing a similar issue on my booking page where I use the BookingPress plugin. The below errors appear on the booking page. I read the answers here but I couldn’t find how to clean it. Does anyone have any help?
Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /wordpress/plugins/jetpack/13.9-a.7/jetpack_vendor/automattic/jetpack-image-cdn/src/class-image-cdn.php on line 682
Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /wordpress/plugins/jetpack/13.9-a.7/jetpack_vendor/automattic/jetpack-image-cdn/src/class-image-cdn.php on line 682
Hi @duygutasdan,
It’s likely that error reporting is enabled on your server or by the BookingPress plugin. You might want to contact the BookingPress plugin authors to see if there’s a way to disable these notices.
Thank you @alinclamba
Here is what the BookingPress customer service said about the issue:
1. I’ve checked your given URL and it shows that the error displays from the ‘Jetpack’ plugin which seems scanning the whole page content and doesn’t get the proper data from the page and that’s why it shows those warnings. Further, please note that ‘Jetpack’ may checking for the ‘img’ tag but BookingPress uses the vueJS components which loads the image via ‘el-img’ tag and with ‘:src’ attribute so these may cause the conflict. However, the error are coming from the Jetpack plugin, we can’t do much for that. You need to contact the ‘Jetpack’ plugin and ask them to place some precautionary code while scanning and processing the images.
When you say “the bookingPress plugin autors”, do you mean the person who uses BookingPress on the dashboard? Or somebody else? I am using the plugin by myself.
Hi @duygutasdan
You can use the code snippet on this page:
https://jetpack.com/blog/skip-a-image-with-photon/
To exclude that page from being cached in Jetpack’s Site Accelerator, and that should remove the error for you.
I wanted to follow on my colleague’s message above to let you know that we will also work on our end to get that deprecation warning fixed in the next Jetpack release. You can follow our progress on this here:
https://github.com/Automattic/jetpack/pull/39685
