• Resolved Jonathan Jewell

    (@hyperpolymath)


    Sorry, cannot seem to add a screenshot in the form editor so put the link to the error message and all the details I have in the Snipboard.io link above.

    I wanted to find out what this means, what the impact is, what can be done about it, and if I can unique/specific I need to sort myself for my site or it is something that you need to fix in the plugin (if so, hope the feedback here is helpful)?

    Thank you – it’s a great plugin and not had any issues so far apart from this. It might be related, perhaps, to an upgrade install on PHP8.1. I cannot think of a reason that makes sense for any other substantive change to anything else, but then it is just speculation on my part here. Oh, and I have a paid licence, which seems to be active with the pro plugin installed. It makes reference to it in the text there, so just in case something like that might be part of the problem?

    Kind regards,

    Jonathan

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Jonathan Jewell

    (@hyperpolymath)

    oh, I just noticed a whole load of these things too, listed as ‘deprecated’ rather than an big warning error, just in case this might be related (well, regardless of that, but I am putting it here in case they are linked):

    Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

    OR the same thing, but with that CAseInsensitiveDictionary (kind of ironic there) with the Requests_Cookie_Jar (linked to the items below)

    There are several of these, only difference being the page numbers (where the page numbers at the end of these are what I have put X or Y for):

    wp-includes/Requests/Utility/CaseInsensitiveDictionary.php:X
    wp-includes/Requests/Cookie/Jar.php:Y

    where the page numbers for:

    X are 40, 51, 68, 82, 91
    Y are 63, 73, 89, 102, 111

    Hope this is useful feedback for you, and keen to know if there’s anything deadly here that means I should switch some setting on/off or uninstalling the plugin.

    Thanks, Jonathan

    • This reply was modified 2 years, 8 months ago by Jonathan Jewell. Reason: just noticed a small difference in the error that I needed to add
    Plugin Author WebFactory

    (@webfactory)

    Morning,
    Thank you for the detailed info. The code you’re referring to is from the PRO version. The issues noted in the screenshot will be fixed ?? It’s PHP v8.1 related.

    I don’t think the issues in the second message are related ??

    If you need any additional assistance please contact us via email as we can’t provide any PRO related support in this forum. Thank you for understanding.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘odd error (through Query Monitor plugin) – what does it mean, can it be fixed?’ is closed to new replies.