realtimecrime

Disregard…..I just got it to work! Basically, I followed your instructions of removing extended protection on each, then clearing cache, then adding back the protection to the sub-directory install, followed by the parent install. Phew!

I am having the exact problem described in this thread, so I thought I would chime in. I have two WordPress installations. One is on the parent directory, and one is in a subdirectory. I followed the instructions to optimize first the installation in the subdirectory, but for some reason I am still having problems. The WordPress installation in the subdirectory throws an HTTP Error 500 after optimizing the firewall in the parent directory. I have deleted both Wordfence installations and cleared the cache prior to reinstalling and following the steps anew multiple times, but the result is always the same. I found the following in the error log: PHP Fatal error: Cannot declare class wfWAFWordPressRequest, because the name is already in use in /home3/realtiu2/public_html/social/wp-content/plugins/wordfence/waf/bootstrap.php on line 180.

I wish I knew what to do with the information in the error log, but I am a “newbie”.

I am having the same trouble with the REST API not working, but I was under the impression that the API calls would work until version 4.0 is available. I thought by “deprecated” you all meant that it would no longer be supported and was slated for elimination upon introduction of 4.0. Am I wrong, or should the REST API be functioning for me? (perhaps I am using the wrong syntax)