Open raamdev opened 8 years ago
Tested using:
WordPress Version: 4.7 Current WordPress Theme: Twenty Seventeen version 1.0 Active Plugins: Comet Cache Cache Pro Version 161227 +All In One WP Security 4.2.4 PHP Version: 7.0.10-2+deb.sury.org~xenial+1 MySQL Version: 10.0.28-MariaDB-0ubuntu0.16.04.1
After enabling most applicable security settings in All In One WP Security, (Firewall settings, Brute Force Protection, Bot Protection, File Permissions settings, etc). I checked to see if the front end site behaved properly and if Comet Cache was running.
Comet Cache is working fine on the front end and has no issues with redirection or 404 pages. I have seen previous reports in support about Login errors and 404 issues with Comet Cache while a security plugin is active. I did not encounter this issue.
I suspect the customers have changed Database settings they did not fully understand for security along with Login Lockdown/User registration settings that hardened admin login settings. They may have also changed the /wp-login
slug or the actual login url itself.
Please note though that the cache does not Automatically clear when changing/updating settings in All In One WP Security. I believe the cache should be cleared after a change as some tweaks in All In One WP Security deal with the front end such as IP Blocking, Maintenance Mode, Firewall settings, restricting access to or visibility of specific pages/posts (user archives, 404 pages, old archived posts, etc.)
Disabling the plugin does clear the cache
Thanks, Renz. So it sounds like all that needs to be done here is to figure out what we can hook into that gets fired with All In One WP Security settings are saved, so that we can clear the cache at the same time.
I'll remove the needs testing
label for now and leave this as a todo.
We have at least one report of the All In One WP Security plugin resulting in 404 errors when enabled alongside Comet Cache.
I'm opening this GitHub issue so that we can track progress towards researching the specific compatibility issue.
2017-01-03 Update: See https://github.com/websharks/comet-cache/issues/803#issuecomment-270278570