Miscellaneous options control a few details which can be important for performance and convenience. Note that several options pertain to the handling of
.htaccess rules, but for best performance on any Apache-based site, WordPress should be rescued from its usual reliance on
.htaccess by employing
.conf rules instead.
Update .htaccess Directives Now?
.htaccess file will be updated by WordPress whenever it needs to be, and the special rules required for operating the cache will automatically be included when that process occurs. Activation of this plugin will have triggered an update to place the cache rules in the file, but you can also set the option below to perform an additional update at any time. (For example, you might need to do this if your
.htaccess file was not writable when the plugin was activated.) If you set the option,
.htaccess will be udpated when you submit this page. NOTE: To remove the cache rules altogether, just deactivate this plugin, and it will happen automatically (provided
.htaccess is still writable at that time).
- Yes — Update
.htaccess Update OK?
If you have manually updated your
.htaccess file, or you otherwise know that the file is correct, you can set the option below to clear the error message that this plugin will keep displaying once it has detected that WordPress failed to make a requested update to your
- Yes — Don’t Pester Me About
Insert HTML Comment in Cached Pages?
By default, the Faster Cache will mark cached files with a brief HTML comment at the very bottom of the page source to assist in determining whether you are viewing a page retrieved from cache or a page that was generated on the fly. If you’d rather switch this off, meaning there will be no external indication that you are running a cache — apart from the speed increase — you can indicate that here.
- Yes — Mark Cached Files With HTML Comment
How Long to Wait to Write a Cache File?
You can tweak how long you’d like Faster Cache to wait for your server to be ready to write cache files. A longer wait time reduces the chances that the caching engine will have to give up before the server is ready, but it also means that viewing a page which is waiting to be cached may get delayed by roughly that same amount of time. For most environments, a wait of up to 1000 milliseconds (1 second) is probably a good compromise.
- Total time to wait in milliseconds. Recommended: 1000 milliseconds (1 second)
Post IDs to Exclude?
You can indicate specific posts or pages which should never be cached by entering their numerical post IDs as a comma-separated list below.
- Comma-separated list of post IDs.