Initial public release.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3738344,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3738344,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3737033,"resolution":"1","location":"assets","locale":"","width":900,"height":536},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3737033,"resolution":"2","location":"assets","locale":"","width":900,"height":536}},"screenshots":{"1":"CacheNova Settings Access \u2014 Find the CacheNova settings page under the WordPress Settings menu to configure cache management and optimization features.","2":"CacheNova Dashboard \u2014 Manage automatic cache clearing, toast notifications, public\/private\/object\/browser cache types, cache reports, database optimization, persistent object cache, early-bypass page cache, and uninstall data settings from a modern dashboard."}},"plugin_section":[],"plugin_tags":[146,4932,7913,3853,247],"plugin_category":[52,54],"plugin_contributors":[272695],"plugin_business_model":[],"class_list":["post-372521","plugin","type-plugin","status-publish","hentry","plugin_tags-cache","plugin_tags-developer-tools","plugin_tags-object-cache","plugin_tags-page-cache","plugin_tags-performance","plugin_category-performance","plugin_category-security-and-spam-protection","plugin_contributors-shaounchandrashill","plugin_committers-shaounchandrashill"],"banners":{"banner":"https:\/\/ps.w.org\/cachenova\/assets\/banner-772x250.png?rev=3738344","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/cachenova\/assets\/icon-256x256.png?rev=3738344","icon_2x":"https:\/\/ps.w.org\/cachenova\/assets\/icon-256x256.png?rev=3738344","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/cachenova\/assets\/screenshot-1.png?rev=3737033","caption":"CacheNova Settings Access \u2014 Find the CacheNova settings page under the WordPress Settings menu to configure cache management and optimization features."},{"src":"https:\/\/ps.w.org\/cachenova\/assets\/screenshot-2.png?rev=3737033","caption":"CacheNova Dashboard \u2014 Manage automatic cache clearing, toast notifications, public\/private\/object\/browser cache types, cache reports, database optimization, persistent object cache, early-bypass page cache, and uninstall data settings from a modern dashboard."}],"raw_content":"\n
A general-purpose cache-clearing plugin for any WordPress site. It works identically regardless of which theme or page builder you use \u2014 Divi, Elementor, Gutenberg, a classic theme, all of it \u2014 because it hooks into WordPress's own standard save\/activate\/deactivate events, not anything builder-specific.<\/p>\n\n
What it does, on any site:<\/strong><\/p>\n\n Why \"light\" vs \"full\" clearing matters<\/strong><\/p>\n\n Earlier cache-clearing approaches run a full clear (OPcache reset, full cache-plugin flush, filesystem walks) on every timer tick \u2014 which can itself slow a site down if it happens too often. This plugin splits the work:<\/p>\n\n Automatic bonus support for Divi<\/strong><\/p>\n\n If Divi happens to be active on the site, the plugin detects it automatically and adds continuous purging of Divi's No further configuration is required \u2014 Divi's Static CSS File Generation is disabled automatically the moment the plugin activates.<\/p>\n\n\n Any theme, any plugin. The core of this plugin \u2014 clearing transients, object cache, OPcache, its own optional page cache, and popular third-party cache plugins, on a schedule and on every save \u2014 hooks into WordPress's own standard events ( No. It detects common caching plugins (WP Rocket, W3 Total Cache, WP Super Cache, LiteSpeed Cache, SiteGround Optimizer, Autoptimize) and flushes them as part of a full clear, rather than working against them.<\/p><\/dd>\n On Divi 4 sites: not while this plugin is active \u2014 it's re-enforced on every page load. On Divi 5: there is no longer a setting for this at all (Elegant Themes removed it), so the question doesn't apply \u2014 the plugin purges the et-cache folder after every request instead.<\/p><\/dd>\n Not for the full duration of a request \u2014 Divi 5 has no opt-out for dynamic CSS generation, so it may briefly create files while serving a page. This plugin removes them again immediately after each request finishes, so the folder never persists or accumulates stale files, but it can't be prevented from being written to at all on Divi 5 the way it can on Divi 4.<\/p><\/dd>\n No \u2014 the scheduled background tick only performs a lightweight clear (object cache and expired transients). The heavier full clear only runs when you actually save content in Divi or click \"Clear Cache Now\" manually.<\/p><\/dd>\n With that toggle ON, deleting the plugin (not just deactivating it) removes its settings, its last-cleared\/last-clear-type records, and the wp-content\/cache\/cachenova folder it uses for the built-in Public\/Private page cache, then runs one final full-site cache clear. It does not touch Divi's own et-cache folder, since that belongs to Divi, not to this plugin. It's OFF by default, so a normal delete leaves your settings in place in case you reinstall later.<\/p><\/dd>\n A persistent object cache lets WordPress reuse database query results across page loads (via APCu, Redis, or Memcached) instead of re-querying every time, which typically speeds up admin and front-end response times. It's OFF by default. Turning it on runs a real connection test first \u2014 nothing is installed if that test fails. If it succeeds, the plugin writes a wp-content\/object-cache.php drop-in plus a small config file, and clears the cache once so it starts clean. It will never overwrite a different object-cache.php that's already there (from WP Redis, W3 Total Cache, etc.) \u2014 it detects that and asks you to remove the existing one first. Deactivating this plugin always removes the drop-in again, so caching goes back to WordPress's normal per-request behavior the moment you switch it off.<\/p><\/dd>\n The cache-plugin detection and general WordPress cache clearing work on any site. The Static CSS File Generation override is Divi-specific and has no effect if Divi isn't active.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
et-cache<\/code> directory \u2014 a common source of \"I edited it but nothing changed\" on Divi sites \u2014 plus disabling Divi 4's Static CSS File Generation setting so the folder is never created in the first place. On Divi 5 (which removed that setting entirely), the plugin purges the folder after every request instead. None of this runs, and none of it is needed, on a site that isn't using Divi \u2014 the rest of the plugin works exactly the same either way.<\/p>\n\n\n\n
\/wp-content\/plugins\/<\/code>, or install the zip directly through Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\n\n
Does this only work with Divi, or with any theme and plugin?<\/h3><\/dt>\n
save_post<\/code>, switch_theme<\/code>, activated_plugin<\/code>, and so on), which fire identically no matter what theme or page builder is active. Divi support is a bonus that's detected and applied automatically only if Divi happens to be installed; nothing Divi-specific runs, and nothing is required, on a site that isn't using it.<\/p><\/dd>\nWill this conflict with my other caching plugin?<\/h3><\/dt>\n
Can I re-enable Divi's Static CSS File Generation?<\/h3><\/dt>\n
Does this fully prevent the et-cache folder from ever existing on Divi 5?<\/h3><\/dt>\n
Does the background schedule slow my site down?<\/h3><\/dt>\n
What does \"Delete all data on uninstall\" actually delete?<\/h3><\/dt>\n
What is the Persistent Object Cache feature, and is it safe to turn on?<\/h3><\/dt>\n
Does this work outside of Divi?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n