# My changes do not appear on the site

> You change a price, a description, an image. The site says "saved". And the public page stays identical. It is almost never a failed save: between your screen and the server, several layers keep a copy of the previous page, and one of them was not told.

- Source canonique : [https://allaux.fr/en/problemes/modifications-invisibles-en-ligne](https://allaux.fr/en/problemes/modifications-invisibles-en-ligne)
- Langue : EN
- Dernière mise à jour : 2026-09-30

## Direct answer

> Reload the page in a private window: if the change shows there, it is your browser and nothing else. Otherwise clear in order: Advanced Parameters > Performance on PrestaShop, or the contents of var/cache over FTP; wp-content/cache and the optimisation plugin cache on WordPress. Purge the CDN last, since it keeps its copy even once the site has been cleared.

## Four places a page can be frozen

The first copy is in your browser, which keeps recently received files to avoid asking for them again. The second is any content delivery network in front of the site, serving copies from distributed servers. The third is the server cache, or a cache module installed in the CMS. The fourth is the CMS’s own compiled cache, holding templates and stylesheets in assembled form.

Each is cleared differently, and clearing the wrong one changes nothing. That is why the same symptom can vanish after a simple forced reload for one person, and persist for hours for another.

## Finding which one is at fault

1. **Open the page in private browsing** — If the change appears, the frozen copy is in your browser, and your visitors already see the right version. Solved without touching the site.
2. **Ask someone else, on another connection** — If they see the old version while private browsing shows you the new one, the copy is server-side or in the delivery network.
3. **Add a pointless parameter to the address** — Many caches treat a slightly different address as a new page. If the page then shows the right version, a page cache is confirmed.
4. **Check the content really was saved** — Reopen the record in the admin. If the changed value is not there either, this is not a cache problem: the save genuinely failed.

## When it is not the cache

Three situations give the same symptom with no cache involved. A change made in the wrong context: on a multilingual or multistore shop, the edited field belongs to a language or store other than the one displayed. A value overridden by a higher-priority rule: a specific price, a promotion or a customer group setting beats the base price. And a change made in a file that is not the one in use: parent theme instead of child theme, or a duplicated stylesheet.

On a site with staging, also check you are not working on the copy.

On a site with a page builder, the builder content overrides the classic editor content.

## Clearing the cache is not a fix

> If you have to clear a cache after every change, the configuration is wrong. A properly configured cache invalidates itself when data changes. Repeated manual clearing is the symptom of a cache ignoring the CMS signals.

## Carry on with the right page

- **Clearing the PrestaShop cache** — PrestaShop’s different caches and the order to clear them in. ([/guides/vider-cache-prestashop](/guides/vider-cache-prestashop))
- **Clearing the WordPress cache** — The WordPress equivalent, cache plugins included. ([/guides/vider-cache-wordpress](/guides/vider-cache-wordpress))
- **Caching explained** — What each cache level is for, and which one keeps what. ([/glossaire/cache](/glossaire/cache))
- **CDN explained** — If a delivery network sits in front of the site. ([/glossaire/cdn](/glossaire/cdn))

## FAQ

### Do my customers see the old version too?

Not necessarily. If the frozen copy is in your browser, you are the only one affected. That is the first thing to check, and it saves a pointless intervention.

### How long does a cache keep a page?

It is a setting, not a fate: from minutes to days depending on configuration. A high value on product pages is a poor choice for a shop whose prices move.

### I replaced my image but the old one still shows. Why?

Because the file name did not change: every layer believes it holds the right version. Uploading the image under a new name fixes it instantly.

### Style changes never show first time. Is that normal?

That is classic behaviour for a CMS that assembles and compresses stylesheets. The assembled file has to be regenerated, otherwise it keeps serving the old version.

### Can I disable caching entirely?

Technically yes, but the site becomes noticeably slower and more fragile under load. Better to configure it properly than remove it.