This page in the RunCache gives you granular control over the RunCache’s automatic cache purging behavior. By configuring these rules, you can ensure that your website’s content remains fresh and up-to-date for your visitors without requiring you to manually clear the cache after making changes.
Purge All Cache
These options trigger a complete purge of the entire site cache. This is necessary when a change affects site-wide elements like your theme, plugins, or navigation.
- When the custom permalink structure is changed
This rule purges the entire cache if you modify your site’s URL structure in WordPress settings. Since this changes every link on your site, a full purge is required to prevent broken links. - When switching to a different theme
Activating a new theme fundamentally alters your site’s design and layout. This option clears all cached pages to ensure the new design is applied correctly across the entire website. - When the site title/tagline / WordPress address/site address is changed
This purges the full cache when you update core site settings. These elements often appear in global headers or footers, so a full purge is necessary to reflect the change on every page. - When the customizer is saved/updated (Appearance-Customize)
Changes made in the WordPress Customizer often affect site-wide elements such as headers, footers, fonts, and colors. This setting clears the cache to apply these global design changes immediately. - When a theme/plugin is updated
Updating a theme or plugin can introduce new features, styles, or scripts. This option purges the entire cache to prevent conflicts and ensure the updated code is loaded correctly. - When a plugin is activated/deactivated
Activating or deactivating a plugin can significantly alter your site’s functionality or appearance. This rule clears the cache so that the plugin’s effects can be correctly applied or removed globally. - When a nav menu is updated
Since navigation menus typically appear on every page of your site, this setting purges the entire cache whenever a menu is created, updated, or deleted. - When a sidebar widget is updated
This rule clears the whole cache when a widget is added, removed, or reordered. This is useful because sidebars are often present on many pages throughout the site. - When a widget parameter is updated
This option purges the entire cache when you save changes to an individual widget’s settings. This ensures the updated widget content is visible across all pages where it appears.
Purge Homepage
These rules specifically target your site’s homepage cache, ensuring that your most important page always shows the latest content.
- When a post/page/CPT is published/modified
This purges the homepage cache whenever new content is published or an existing piece is updated. It is necessary to ensure that your latest posts or news appear on the front page immediately. - When a published post/page/CPT is trashed
This rule purges the homepage, removing links or excerpts of content you have just deleted. This prevents visitors from seeing links to pages that no longer exist.
Purge Post/Page/CPT
These settings manage the cache for individual posts, pages, and custom post types (CPT).
- When a post/page/CPT is published/modified/trashed
This clears the cache for the specific post or page being edited or deleted. This ensures any content changes are immediately visible to your visitors. - When a comment is approved/unapproved/trashed
This option purges the cache for a specific post when its comments are moderated. This allows the new comment (or its removal) to be displayed on the page right away.
Purge Archives
These rules ensure that your category, tag, author, and date-based archive pages remain updated when content changes.
- When a post/page/CPT is published/modified/trashed
This is the master toggle that enables all archive-related purging. It ensures that when a post’s status changes, all relevant archive pages are updated as well. - Purge post type archive page
When a post is updated, this rule specifically clears the cache for the main archive page of that post type (e.g., /blog/ or /portfolio/). - Purge category/tag/taxonomy pages
This purges the cache for any category, tag, or custom taxonomy archive that the updated post belongs to. This keeps your listings of related content fresh and accurate. - Purge author page
This option clears the cache for an author’s archive page when one of their posts is updated. This ensures the author’s page correctly reflects their latest contributions.
Custom Purge URL
- Enable custom purge URL path.
This option lets you specify additional URLs or paths to purge during general cache-clearing events. This is useful for related pages that aren’t automatically detected, such as a custom sitemap page.
Scheduled Purge
- Enable Scheduled Purge
This feature automatically clears the entire site cache at a regular interval that you define. It is most useful for sites with a very long cache lifespan to ensure all content is periodically refreshed.
Debug Options
- Enable HTML Footprint in HTML
This is a troubleshooting tool that adds an HTML comment at the bottom of your site’s source code. The comment confirms if a page was served from the cache and when it was created, which is helpful for debugging. This option should be disabled on a live production site.
If you have any other questions or need help – please feel free to get in touch with our 24/7 support team. We’re here to help!