Old content after updates is normally caused by caching at the browser, application, server, or CDN layer rather than the files failing to update.
Common symptoms
- You changed files but visitors still see the old page
- Some devices show the new content and others do not
- Only images or CSS stay outdated
Troubleshooting steps
- Clear the application's cache and any plugin-level page or asset cache first.
- Purge CDN or proxy cache if one is enabled for the domain.
- Test in a private browser session and force-refresh the page.
- For CSS and JavaScript, change the asset version string or filename if aggressive caching is in place.
- Verify you updated the active document root and not a staging or unused folder.
Additional notes
- Multiple cache layers can stack and make one successful purge appear ineffective.
- A changed file on disk does not guarantee a changed response if edge cache is still serving the old object.
When to contact support
Contact support if the origin files are correct and all caches are purged but old content persists.