• Hello.

    After the recent updates we get these errors:

    Deprecated: Non-canonical cast (boolean) is deprecated, use the (bool) cast instead in /home/asafdevc/hobbies4.life/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/xmlrpc.php on line 235

    Deprecated: Non-canonical cast (double) is deprecated, use the (float) cast instead in /home/asafdevc/hobbies4.life/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/xmlrpc.php on line 216

    It affects many things, including breaking the sitemap.

    In prevous treads, I saw recommendation for changind the DB user prevliges – unfortunately it doen’t seem to be possible on shared hosting.

    How can we solve it?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @asafm7,

    We already support up to PHP 8.5, but there are a few deprecation notices such as these to address. They are already scheduled in for an upcoming version release. As deprecation notices are non-fatal and simply warn that something won’t work in future versions, you wouldn’t normally need to take action.

    In a production environment I’d always expect visible PHP error logging to be turned off, but it sounds like that’s not that case if a sitemap is being malformed. Are you able to confirm if that’s the case, or whether another plugin or diagnostic tool might be displaying notices/errors on the front-end instead?

    Many thanks,
    Peter.

    Thread Starter asafm7

    (@asafm7)

    Thanks, @wfpeter.

    The warnings seem to originate from the WAF Extended Protection. Fot this reason, they show up even when Wordfence is deactivated and WP_DEBUG is disabled.

    When the Extended Protection is removed, the errors disappear.

    The presence of the warnings in the HTML breaks things as AJAX/FETCH and the sitemap.

    Let me know if more information is needed.

    Thanks.

    Plugin Support wfpeter

    (@wfpeter)

    Please ignore: the forum is listing 0 replies, when in fact my initial response has now become visible.

    Thread Starter asafm7

    (@asafm7)

    @wfpeter, I’m not sure I understand your recent reply. In case you missed it, I posted a reply a few seconds before you did.

    Plugin Support wfpeter

    (@wfpeter)

    Ah, you replied as I had re-written my initial reply because I thought it hadn’t saved. Apologies for any confusion there @asafm7.

    Just so I can check the site settings and actually visit the front-end of your site and sitemap myself, could you send a diagnostic to wftest @ wordfence . com by using the link at the top of the Wordfence > Tools > Diagnostics page? Click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it as the inbox is unmonitored.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks again,
    Peter.

    Thread Starter asafm7

    (@asafm7)

    Thanks, @wfpeter.

    Should I reactivate the Extended Protection before sending the diagnostic?

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.