CacheSettingValues::SETTING_DEFAULT_VALUE, '10 Minutes' => 600, '1 Hour' => 3600, '4 Hours' => 14400, '12 Hours' => 43200, '1 Day' => 86400, '3 Days' => 259200, '7 Days' => 604800, '4 Weeks' => 2419200, ); public static function display() { if ( ! is_network_admin() ) { ?>
init_settings(); self::open_form(); self::display_cache_times_header(); self::display_cache_times_options(); self::display_cache_times_submit_button(); self::close_form(); self::display_custom_notices(); ?>
id ) { // ignoring nonce requirement as we're using settings_fields to handle verification, we only handle display of notice here. // https://codex.wordpress.org/Settings_API . // phpcs:disable WordPress.Security.NonceVerification.Recommended if ( isset( $_GET['settings-updated'] ) ) { // phpcs:disable WordPress.Security.NonceVerification.Recommended if ( 'true' === $_GET['settings-updated'] ) : ?>

Cache Times

Increasing the cache times on the server will allow more users to see Cached copies of your pages. Cached copies of pages are served from outside of WordPress, which conserves server resources and saves time for your users.

The cache is purged in most functions that update post content, so oftentimes it's best to set limits as high as possible. If you regularly update content and notice your posts take a while to update, it may be best to reduce these limits. If you are making a one-off change, the purge cache button will update the content for your visitors.

getMessage()} {$e->getTraceAsString()}" ); } } private static function display_password_protected_info_text() { if ( CacheViewHelper::is_current_site_password_protected() ) { ?>

Your environment is password protected. Cache settings will not apply until the password protection is removed.

get(); ?>

Post Types

Use the below options to alter the cache expiry times on the public post types on your site. Site performance will improve with longer time.
Longer caching timeout will make your website work better.

get( $post_type . '_cache_expires_value' ); ?>
$seconds ) { echo ''; } } private static function display_cache_times_rest_api_namespaces() { $options = CacheDbSettings::get_instance()->get(); ?>

REST API Namespaces

Use the below options to alter the cache expiry times on the REST API end-points on your site.

get( 'smarter_cache_enabled' ); ?>

Smarter Cache

This option will allow your posts and pages to be cached for longer if they haven't been modified in a while.

If your posts and pages have gone more than 4 weeks without being updated, this option will allow you to cache them for up to 6 months by default.
As posts pass 4 weeks without being updated, the cache header will be updated to 6 months.

>
get( 'last_modified_enabled' ); ?>

Last-Modified Headers

Last modified headers will encourage bots and users to use local cache instead of pulling content from the server each time. This will speed up their responses, and decrease the impact a heavy bot crawl could have on your site.

Last-Modified headers are updated on specific posts based on the last time they were modified, and the most recent comment. They are also updated Globally on Theme change, or Menu updates. If a major change is made, the global Last-Modified headers can be updated using the option below. The Last-Modified headers sent from the server are always the most recent of those options.

>