PHP 8.1 warnings

  • Resolved Darko G.

    (@darkog)


    2 years, 8 months ago

    Just posting those here. Hope this helps.

    [15-Mar-2022 22:17:23 UTC] PHP Deprecated:  Return type of QM_Collectors::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vagrant/code/xxx/xxx.test/wp-content/plugins/query-monitor/classes/Collectors.php on line 14
[15-Mar-2022 22:17:23 UTC] PHP Deprecated:  Return type of QM_Dispatchers::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/vagrant/code/xxx/xxx.test/wp-content/plugins/query-monitor/classes/Dispatchers.php on line 12
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks. Are you using the latest version of Query Monitor? These warnings were fixed in 3.8.2.

    ah, okay my question is similiar in nature but seems to be slightly different ones appearing for me now, even with the latest one:

    https://snipboard.io/vrpocI.jpg

    Sorry, can’t find the button to put screenshot in, and just will not paste, so have to send you to the snipboard.io place (please scan it if you’re not sure about it!), or I can email it to you.

    I actually think this appeared only after I got the more up to date version of query monitor, but maybe I’m wrong on that.

    Really appreciate your thoughts and would also be interested in knowing in the meantime, what this might mean in terms of any risks/effects that might be relevant using it in the meantime.

    Thank you!

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    @hyperpolymath Thanks for the report but these errors are coming from the admin-menu-editor plugin (see the path in the error message). Query Monitor does unfortunately blame itself for some errors when it can’t reliably determine which plugin or theme caused the error — it sends its apologies! (I’ll hopefully get this fixed soon.)

    ah, thanks for letting me know. Well, I have gone through the entire list, looked for the plugins and reported the errors to everyone who ‘gets a mention’ there. So if they get onto their ones, I’ll let you know when these ones disappear and what is left over afterwards.

    Presumably the easiest way to isolate it would be to turn off the plugins (or switch the theme) and see which ones disappear? Or is there a better (quicker, faster, more reliable, less disruptive) way to do it? Or is there a more useful set of data I could send you that will help you to identify it (or where I can look to find it myself) to isolate what is going on?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP 8.1 warnings’ is closed to new replies.