php warnings!

These warnings are not supposed to be displayed with the “@” operator. Unfortunately, the DOMDocument object does not understand HTML5 well and this is one way to deal with this.

What version of PHP are you using ? Or did you happen to change the code ?

Thank you

PHP version 7.4.4

Any plans releasing an update soon based on my feedback? ??

Ok, I will add an extra layer to deal with the warnings but I’m surprised you can see this considering the current code. Maybe some of your php settings do not take into account the “@” that’s supposed to remove the warnings.

In order to resolve this topic, can you tell me how you got these showing ? apparently it did not show up before if you have been using the plugin for a while so I’m a bit confused here.

The next update will come soon, stay tuned ??

It could be WordPress 5.4. And no I do not sue query monitor on production and on all-time as it’s not good to keep it running once you do not debug.

I will take a more in-depth look at WP 5.4 although it seems more like a pure php related issue.

My question was simply how did these warnings started appearing ? You did not mention the context of the issue and that could be helpful to solve this.

Was the plugin running before on your page and thenm, it started showing up for some reason?
Did it show up from a fresh activation of the plugin ?
After an update of wordpress ?
Anything else that could be related ?

Thank you

I can not help you more there and reply as I enabled query monitor to debug another thing and saw this one from your plugin. It could always have been there or occurred due to a conflict with a new plugin/later version of a plugin or wp core.

I have had the plugin installed for a while but never check SQL queries so unfortunately, I can not give you too much guidance here. If I find something I will let you know! Understand it makes it tricky for you to narrow down what it could be but I share want I can.

[ Please do not bump. ]

I have tried to address those warnings that you were getting on your installation with some minor code modifications.
So far I could not reproduce this, and I have checked my logs before releasing the v1.2.0, nothing like that was showing up.
Are you still getting anything ?