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.
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
-
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.
-
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.
-
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.
-
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.
Carry on with the right page
-
Clearing the PrestaShop cache
PrestaShop’s different caches and the order to clear them in.
-
Clearing the WordPress cache
The WordPress equivalent, cache plugins included.
-
Caching explained
What each cache level is for, and which one keeps what.
-
CDN explained
If a delivery network sits in front of the site.
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.