WordPress Changes Not Saving: Updates Vanish After Publish (2026)

Two different bugs produce the same symptom: your edit vanishes. Either WordPress never saved it (a real failure), or it saved and you're looking at a cached version (a display failure). Diagnose which one you have before fixing anything - the tests take 30 seconds.

Test First: Did It Actually Save?

Update the post, then open it in an incognito window or append ?v=123 to the URL. If the change appears: the save worked and you're fighting cache - skip to the cache section below. If the change is gone even uncached: the save genuinely failed.

Real Failure Cause 1: REST API Blocked

Gutenberg saves via /wp-json/wp/v2/posts. Security plugins, .htaccess rules, and CDNs that block wp-json kill saves while the UI claims success. Open DevTools → Network, click Update, watch for a 401/403 on wp-json. The invalid JSON guide covers REST API blocks in depth.

Real Failure Cause 2: mod_security

Saving content containing code, multiple URLs, or certain HTML triggers Apache mod_security and the POST dies at 403/406 - invisibly to the editor. Check your host error log for mod_security hits. Fix: ask the host to whitelist the rule, or save the content in smaller chunks to find the triggering element.

Real Failure Cause 3: Plugin/Permissions

A post-lock plugin, a revision plugin, a workflow plugin that requires "review" before publish, or a capability plugin that removed your edit_published_posts right - all produce silent save drops. Test by disabling the workflow/security plugins, and check your user role hasn't been demoted (see the access-denied guide for capability debugging).

Display Failure: The Cache Layer Cake

If it saved but doesn't show, purge in this order - each layer can serve stale content independently:

• Browser: hard refresh (Ctrl+F5) or incognito
• Page cache plugin: purge all caches (WP Rocket, LiteSpeed, W3TC)
• Host cache: server-side cache in your hosting panel - many hosts cache aggressively and it's the most-forgotten layer
• CDN: Cloudflare "Purge Everything" if enabled

If the fix is "purge cache after every edit," your cache plugin isn't auto-purging on save - enable post-update purge in its settings.

Page Builder Variant

Elementor/Divi saves go through their own AJAX, not the WP save. If the builder hangs on "Updating," the failure is admin-ajax.php - see the admin-ajax 400 guide for that diagnosis path.

Keep Reading

• Invalid JSON response - the REST API errors behind silent save failure
• admin-ajax.php 400 - the page-builder save endpoint
• 403 forbidden - mod_security and firewall blocks
• Stuck in maintenance mode
• Bluehost review 2026
• WP-Cron Not Working: Scheduled Tasks Never Run (2026)