Español
Deutsch
"I made a change and nothing happened" is one of the most common support questions, and it's usually caching, not a broken update.
Why This Happens
Browsers store copies of pages and files locally to load returning sites faster. If you're viewing a cached copy, your browser simply hasn't fetched the updated version yet.
Clearing Your Browser Cache
In most browsers, a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) reloads the page while bypassing the local cache — often faster than digging through browser settings.
Full Cache Clear
For a more thorough clear, each browser's settings menu has a "Clear browsing data" option where you can specifically target cached images and files.
Try a Private/Incognito Window
A private browsing window typically starts with no cache at all, making it a quick way to confirm whether caching is really the issue.
Don't Forget Server-Side Caching
If a hard refresh still doesn't show your change, server-level page caching (through Plesk or a CMS caching plugin) may also need to be cleared before the update appears for anyone.
CDN Caching Too
If you use a CDN, it caches content at its own edge locations separately — most CDN dashboards include a "purge cache" option for exactly this situation.
