Thanks! I’ll take a look.
Re 1, can you expand one of the messages and let me know what it says?
Re 2, Query Monitor sometimes likes to blame itself for an error if it doesn’t have enough confidence in which component is actually causing it. If you take a look at the “Location” column for these errors they’re actually coming from the admin-menu-editor plugin. You’d best report these to the author of that plugin.
Hi @johnbillion,
Thank you for the reply. In response:
1. As requested, I have expanded the Developers’ Console error messages. Screenshots below.
Screenshots:
https://prnt.sc/ma9-TNgtsfdy
https://prnt.sc/X4_OsZgJoHY-
https://prnt.sc/FMORme9_QwZ7
https://prnt.sc/WReTKZF89EQ4
2. Yes, the issue appears to occur between your plugin and Admin Menu Editor (plugin). We do not get the “query monitor” deprecation notice for any other plugins we have installed. See screenshot below for expanded information. We will contact the developers of Admin Menu Monitor informing them of this finding as well. If you have access to PHP 8.1.9, you should be able to replicate our finding.
Screenshot:
https://prnt.sc/te9_H9svVpxw
Hope this helps.
Cheerio!
Thanks. Those deprecated errors in the Ajax response are also being triggered by the admin-menu-editor plugin.
I’m going to make an adjustment to Query Monitor so it can correctly identify which component is responsible for this type of deprecated error instead of blaming itself. I’ll hopefully include this in the next release.
Thank you. The developers of Admin Menu Editor have been notified.
Have a great week.
Cheerio!
Hi @johnbillion,
Today, the developers of Admnin Menu Editor released a fix for their plugin’s PHP deprecation notices.
Cheerio!
