500 is not a “denial” of post edit. It is an actual failure of your Apache/PHP system.
Which PHP version are you running?
WordFence will run with all versions up to at least PHP 7.1 (I am using it), but is does require that your PHP has the right modules and configuration. Something that on all hosting setups is specific to the PHP version.
Some “feature”, yet unknown, is likely used in WordFence that requires you to make sure your PHP is set up correctly. There is another open incident right now on WordFence causing 500 errors if using PHP7 in some configurations.
Can’t say what, since no one has yet reported back with any actual error traces explaining what the 500 error is failing on. “500 – Internal error” in itself says nothing about what failed.
SiteGround (the host) defaults to PHP 7.0.22. I upgraded to PHP 7.1.8 and that fixed the problem. Thanks.
Hi @rcwatson
I understand that this issue was fixed when you upgraded PHP to 7.1.8, I would appreciate if you can check the server error log file for more details regarding this “500 – Internal Server Error”.
Thanks.
Here is one of 10 such matches for the occurrence of the internal server error. They’re all pretty much like this one, differing only on the time stamp and post ID.
68.204.89.247 - - [16/Aug/2017:09:16:34 -0500] "GET /wp-admin/post.php?post=660&action=edit HTTP/1.0" 500 1862 "https://allisonsapiaries.com/recipes/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36"