Errors after the recent update

asafm7
(@asafm7)

1 day, 12 hours ago

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 8 replies - 1 through 8 (of 8 total)

Plugin Support wfpeter
(@wfpeter)

2 hours, 54 minutes ago

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)

1 hour, 45 minutes ago

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)

1 hour, 44 minutes ago

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

Thread Starter asafm7
(@asafm7)

1 hour, 40 minutes ago

@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)

1 hour, 39 minutes ago

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)

1 hour, 31 minutes ago

Thanks, @wfpeter.

Should I reactivate the Extended Protection before sending the diagnostic?

Plugin Support wfpeter
(@wfpeter)

1 hour, 12 minutes ago

Yes please @asafm7, if it seems to cause the error to be present, then seeing the site in that state would be best. Feel free to take screenshots of the issue appearing on your sitemap and other places and share them here if you’d prefer to keep Extended Protection disabled to prevent issues for your visitors.

Thanks again,
Peter.

Thread Starter asafm7
(@asafm7)

52 minutes ago

Thanks, @wfpeter.

I’ve re-enabled Extended Protection and sent the diagnostic.

Please let me know if you received it.

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

You must be logged in to reply to this topic.