Page caching via _config->get_string('pgcache.engine')); ?> is currently enableddisabled">disabled.

To rebuild the page cache use the nonce_field('w3tc'); ?> disabled="disabled" class="button" /> operation.

postbox_header('General'); ?>

For many blogs this is your most visited page, it is recommended that you cache it.

Even if using a feed proxy service (like FeedBurner), enabling this option is still recommended.

Cache SSL requests (uniquely) for improved performance.
_config->get_string('pgcache.engine') == 'file_generic'): ?> disabled="disabled" />
Search result (and similar) pages will be cached if enabled.

Reduce server load by caching 404 pages. If the disk enhanced method of disk caching is used, 404 pages will be returned with a 200 response code. Use at your own risk.

Cache only requests with the same URL as the site's site address.

Users that have signed in to WordPress (e.g. administrators) will never view cached pages if enabled.

nonce_field('w3tc'); ?>

postbox_footer(); ?> postbox_header('Advanced'); ?> _config->get_string('pgcache.engine') == 'memcached'): ?>

Multiple servers may be used and seperated by a comma; e.g. 192.168.1.100:11211, domain.com:22122
_config->get_string('pgcache.engine') != 'file' && $this->_config->get_string('pgcache.engine') != 'file_generic'): ?> disabled="disabled" /> seconds
If caching to disk, specify how frequently expired cache data is removed. For busy sites, a lower value is best.

Never send cache pages for these user agents.

Never cache pages that use the specified cookies.

Always ignore the specified pages / directories.

Cache the specified pages / directories even if listed in the "never cache the following pages" field.

Cache the specified pages even if they don't have tailing slash.

Specify additional page headers to cache.

nonce_field('w3tc'); ?>

postbox_footer(); ?> postbox_header('Cache Preload'); ?>

seconds
The number of seconds to wait before creating another set of cached pages.

Limit the number of pages to create per batch. Fewer pages may be better for under-powered servers.

A compliant sitemap can be used to specify the pages to maintain in the primed cache. Pages will be cached according to the priorities specified in the XML file. Google XML Sitemaps is recommended for use with this feature.

nonce_field('w3tc'); ?>

postbox_footer(); ?> postbox_header('Purge Policy'); ?>

Specify the pages and feeds to purge when posts are created, edited, or comments posted. The defaults are recommended because additional options may reduce server performance:












Specify the feed types to purge:


nonce_field('w3tc'); ?>

postbox_footer(); ?> postbox_header('Note(s):'); ?>
  • Enable HTTP compression in the "HTML" section on Browser Cache Settings tab.
  • The TTL of page cache files is set via the "Expires header lifetime" field in the "HTML" section on Browser Cache Settings tab.
postbox_footer(); ?>