pensato

I have had the same issue on a client site, though it was only affecting /wp-admin. The issue also started 2 or 3 days ago, but is not related to any updates or changes in the firewall AFAIK, since the client has restricted permissions— unless there was an auto-update.

I was also able to fix it using the solution @et linked to. I’m posting it below for future searchers (to save scrolling through to the comment with the fix):

1. Look for a file in your root WordPress directory (the one with wp-config.php) named .user.ini Now, either:

2a. rename, or backup and delete that file or

2b. edit the file and either comment out or delete the lines:

; Wordfence WAF
auto_prepend_file = '/home/dezi3014/public_html/wordfence-waf.php'
; END Wordfence WAF

If that doesn’t work, look for those same lines in .htaccess and php.ini (location of the latter will vary from server to server)

All that said, it would be nice to know what is actually causing the error, since the call is to a file that actually *does* exist. Knowing the problem will help me know how to prevent it from happening again.

Forgot to mark as “resolved”

Amazing. Thank you for the excellent support. It works perfectly.

Donation happily made. Please let me know if there’s any additional way I can contribute to the plugin’s development (help writing documentation, ui assistance, etc). It really fills an important need— especially here in bilingual Canada. ??

Merci.

Sorry for *my* delay.

The updated plugin seems not to have had any effect on either count. Thanks for looking into it.

Any further thoughts?

I’m open to the possibility that the problem is in my server config, but I’m not sure where to begin looking…

I’ve tried all kinds of stuff now in testing. It always, every time, breaks at the first apostrophe.

I’ve tried disabling plugins (I thought maybe Markdown on Save Improved was messing with stuff), but even with all other plugins disabled, no dice.

Any thoughts about where else to look?

Indeed, I had done so! What wasn’t immediately obvious was that the plugin was setting the “reply to” address in the header to the secret user email for posting by email. I saw it at about the same time as I got your reply!

Sorry for the hassle.

Works just fine for me on several P2s!

Oof! You’re getting crazy amounts of spam on the forum! You may want to plug that leak! https://wpkeeper.com/forum/support/oauth-2-provider/