Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Have an odd one with a couple of sites hosted on Azure App Services, both on latest Umbraco 8.6.3 version.
In short, for some properties, when a node is saved & published, the content cache appears to not get updated, and the change cannot be seen on the front end of the site.
These properties vary in type, 1 is a Multi Url Picker, another is an RTE, another is nested content...
This seems to affect only certain nodes. If I update properties on nodes picked by those affected, those updates come through.
There's no custom caching strategy on the affected nodes, so it's not that.
I have added the config outlined in the Umbraco docs (https://our.umbraco.com/documentation/getting-started/setup/server-setup/azure-web-apps) but this has not helped.
To note, the only way I can get the content changes to show are by restarting the App Service itself.
Even using Diplo God Mode to restart the app pool doesn't help, nor clearing all of the caches. Only a hard restart seems to do the trick.
Obviously this is not a good solution to restart the site every time a change is made on given content nodes!
If anyone has had the same/a similar issue specifically with Umbraco 8, I'd love to hear if/how you have solved it!
I am seeing the same issue on 8.6.2. I have a process that is sycning data every 30 minutes, I can confirm that in umbraco the data was synced and it shows published on the node but the site's cache is not updated. This is very disconcerting that the api isn't working correctly.
As a work around I'm setting up an umbraco api controller to publish the branch which I hope fixes the issue but this is really hard to deal with.
var content = Services.ContentService.GetById(1077);
Services.ContentService.SaveAndPublishBranch(content, force: false);
Have you received any support or feedback on this?
We have a related problem. The problem site (umbraco 8.8.0) is hosted in Azure, with one copy serving the public domain and the other copy serving the editor, with Front Door managing the traffic (usually 100% to Public). The problem only seems to happen with non-UI based publishing thats implemented via a service or scheduled task. Items published in this way do not appear on the public domain, and a reset is required to update the cache.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted