Hello Ghost Community,
I am currently facing one persistent issue with my Ghost website where changes made to an existing post appear to save successfully inside the Ghost editor, but the published version of the same post sometimes continues displaying an older version of the content. The main problem is not that I cannot save posts; the editor confirms that the changes have been saved and the updated content is visible when I return to the editor. However, when I open the public URL in a separate browser or from another device, the page can still show the previous title, text, image, or formatting instead of the newly saved version. The behaviour is intermittent, because some edits become visible immediately while other edits appear to remain stuck on the older published version for an extended period before eventually updating.
I have verified that the changes are actually being stored in Ghost because reopening the post from the admin area shows the latest content exactly as I entered it. The issue therefore appears to occur between the saved post and what is being served to visitors through the public website. I have tested making small edits as well as larger changes and noticed that the problem can occur with both. Sometimes changing a sentence and publishing the post results in the new content appearing immediately, while at other times the public page continues showing the previous version even though the editor clearly contains the updated version. The public URL remains the same, and there is no visible error in the Ghost admin interface indicating that publication failed.
I have already tried the usual browser-side troubleshooting steps, including opening the public post in an incognito window, clearing the browser cache, and testing the URL from different devices and networks. The older version can still appear even when the page is accessed from a completely separate browser, which makes a local browser cache problem seem unlikely. I have also checked the page source and refreshed the page several times to determine whether the content eventually changes. In some cases it updates after repeated refreshes or after waiting for a while, but there is no predictable amount of time after which the new version becomes available. Because the editor consistently shows the correct version while the public URL intermittently serves stale content, I am trying to determine whether some form of caching or content delivery behaviour could be involved.
The problem is particularly noticeable when I make several updates to posts during the same session. An earlier change may appear correctly on the public website, but a subsequent edit can remain invisible to visitors even though Ghost reports that the post has been published successfully. I have checked that I am editing the correct post and that the public URL corresponds to the same content item shown in the Ghost admin area. I have also avoided making changes to multiple posts at the same time while troubleshooting so that I can isolate the behaviour to a single publishing operation. Despite this, I have not found a consistent pattern that explains why some publication updates become visible immediately while others continue serving the previous content.
I am also trying to determine whether the behaviour could be related to the way my Ghost installation is hosted or how requests are being delivered to visitors. The website is running normally, and visitors can access existing pages without general connectivity problems. There are no obvious application errors when the stale version is displayed, and the Ghost admin interface continues functioning normally. I have checked the server logs around some of the affected publication attempts, but I have not yet found a clear error that indicates why the public response would contain outdated content. Because the problem disappears eventually without me changing the post again, I suspect that some caching layer or publication propagation process may be retaining an older response longer than expected, but I would like to confirm this rather than making unnecessary configuration changes.
I would appreciate guidance from the Ghost community on how to properly diagnose this specific stale-content issue between the Ghost editor and the public website. I would especially like to know how I can verify whether Ghost is serving the latest published revision, whether there are particular cache mechanisms I should inspect, and what logs or request headers would help determine where the older version is being returned from. If there are recommended ways to force or verify publication propagation without repeatedly editing and republishing the post, that information would also be very useful. My goal is to make sure that whenever Ghost confirms a post has been published, visitors consistently receive the latest version at the public URL without having to wait, refresh repeatedly, or rely on browser-specific workarounds. Very sorry for long post!