Are the changes you make saved to the Umbraco Backoffice?
eg if you revisit the page your changes are there?
If you then republish the page do the changes appear?
If you restart the site, do the changes appear? (this would mean somewhere yo have custom caching that is preventing the new changes from being shown)
Are you load balancing? (here some instances might be updated at publish, but not others if you press F5 continually or in different browsers do you eventually see the update and then it disappears again - if so, something wrong with Load Balancing configuration)
Are there any errors in the trace logs after a publish?
Essentially when you publish something, you might have custom events handling the publish, and these may be erroring, if not it tries to update Examine Search Indexes (this might be erroring) and finally it tries to update the Umbraco Published Cache, which for V7 is an XML file held in memory, and a copy of which is maintained in the file system - sometimes if pages update and then revert, it's because the cache was updated in memory, but the IIS site doesn't have the permissions to update the file - so next time site starts it reads from the file and the content disappears!
Updates or edits not being reflected when I publish.
I am using Umbraco version 7 and experiencing issues with updates or edits not being reflected when I publish.
Hi Mehedi
Are the changes you make saved to the Umbraco Backoffice?
eg if you revisit the page your changes are there?
If you then republish the page do the changes appear?
If you restart the site, do the changes appear? (this would mean somewhere yo have custom caching that is preventing the new changes from being shown)
Are you load balancing? (here some instances might be updated at publish, but not others if you press F5 continually or in different browsers do you eventually see the update and then it disappears again - if so, something wrong with Load Balancing configuration)
Are there any errors in the trace logs after a publish?
Essentially when you publish something, you might have custom events handling the publish, and these may be erroring, if not it tries to update Examine Search Indexes (this might be erroring) and finally it tries to update the Umbraco Published Cache, which for V7 is an XML file held in memory, and a copy of which is maintained in the file system - sometimes if pages update and then revert, it's because the cache was updated in memory, but the IIS site doesn't have the permissions to update the file - so next time site starts it reads from the file and the content disappears!
regards
Marc
is working on a reply...