安装W3 Total Cache后需配置吗？Divi Builder内容回退疑缓存问题

Hey there! I’ve dealt with this exact Divi + W3 Total Cache conflict plenty of times, so let’s walk through what you need to know.

First off: don’t rely on default settings if you’re using Divi Builder. While W3 Total Cache works out of the box for basic sites, Divi’s dynamic editing system and built-in caching/minification will clash with default W3TC configs—this is almost certainly contributing to your content rollback issue.

Here’s the critical configuration you need to tweak:

1. Page Cache Exclusions #

Divi Builder uses special query parameters (like et_fb=1 for front-end editing) and admin pages that should never be cached. Go to Performance > Page Cache and add these to the Never cache the following pages field:

• *et_fb=1* (blocks caching for Divi’s front-end editor)
• /wp-admin/admin.php?page=et_divi_options (Divi settings page)
• /wp-admin/post.php* (post/page edit screens)
• /wp-admin/post-new.php* (new post/page screens)

Also, make sure Cache URIs with query string variables is disabled—this prevents W3TC from caching versions of your page that have Divi’s editor parameters attached.

2. Minification: Disable or Exclude Divi Assets #

Divi has its own built-in CSS/JS minification and file combining. If you leave W3TC’s minification enabled by default, it’ll overwrite or conflict with Divi’s optimized files, leading to stale content display.

Your best bet:

• Go to Performance > Minify and set Minify mode to Disabled if you’re using Divi’s native minification (check Divi > Theme Options > Performance to confirm this is on).
• If you want to use W3TC’s minification instead, manually exclude all Divi-related CSS and JS files (look for files containing divi, et-, or builder in their URLs) from the minify lists.

3. Auto-Cache Purge Triggers #

To prevent stale content from sticking around, configure W3TC to automatically clear cache when you update content. Go to Performance > Page Cache and ensure:

• Automatically prime the page cache is enabled
• Purge policy is set to Page (so only the updated page’s cache is cleared, not the entire site)
• Under Advanced, check Purge post on publish/update and Purge page on publish/update

4. Browser Cache Adjustments #

Divi generates dynamic CSS files for your customizations—if browser cache is set to hold these files for too long, visitors (and you!) will see old styles/content. Head to Performance > Browser Cache:

• For CSS/JS files, set Expires header lifetime to 7 days (not longer—this balances caching efficiency with freshness)
• Enable ETag to help browsers recognize when files have updated

Quick Troubleshooting Tip #

After making these changes, do a full cache purge via the W3TC toolbar button or Performance > Dashboard > Empty All Caches. Then test editing a page with Divi Builder, publish the changes, and hard-refresh your browser (Ctrl + F5 or Cmd + Shift + R) to confirm the new content sticks.

If you still see rollbacks, double-check that you didn’t miss any Divi-related pages in your cache exclusions, and ensure Divi’s own cache (under Divi > Theme Options > Performance > Static CSS File Generation) is configured to clear when you update content.

内容的提问来源于stack exchange，提问作者Vinod G