Hi, you should always indicate the version of Umbraco you are using, what is it?
I have no idea how exactly your deploy script works but the only way that content becomes unpublished is:
the item doesn't exist in your cmsContentXml table
then your umbraco.config cache is rebuilt - maybe you delete this file on deploy?
If the item is in fact published and it's not in your cmsContentXml table then you have data integrity issues and the data integrity health check will indicate this and give you an option to fix it.
The xml cache is independent of if a user is on that node, the published cache is 100% in memory, the umbraco.config xml file is the persisted version of that which gets loaded into memory at startup. It is purely there for startup performance reasons so it doesn't need to be rebuilt form the cmsContentXml table.
Maybe, depending on your deployment your umbraco.config xml file out of date with your cmsContentXml table? I dunno, it certainly seems odd. You could try deleting your umbraco.config file on deployment so that it's rebuilt from the cmsContentXml table on startup.
Web Release Unpublishes Nodes
Hi
Could anyone tell me why when I release an Umbraco site, that sometimes some nodes become unpublished?
I release the site using Octopus Deploy.
Any help would be much appreciated.
Hi, you should always indicate the version of Umbraco you are using, what is it?
I have no idea how exactly your deploy script works but the only way that content becomes unpublished is:
If the item is in fact published and it's not in your cmsContentXml table then you have data integrity issues and the data integrity health check will indicate this and give you an option to fix it.
Sorry, I'm using 7.3 - realised I may have rushed my question and it's too ambiguous.
Unfortunately what makes this topic worse is that these nodes which unpublish are inconsistent, and only happens on some releases.
The content exists in the cmsContentXml table, so I don't think it's that.
And I don't deploy the umbraco.config script as it's rebuilt on deployment. Perhaps this could be why, like you said.
I thought perhaps that if a user is on that node when the site is deploying, it becomes unpublished? That's just a guess though.
Either way, this isn't a massive issue. I'm just curious as to why.
The xml cache is independent of if a user is on that node, the published cache is 100% in memory, the umbraco.config xml file is the persisted version of that which gets loaded into memory at startup. It is purely there for startup performance reasons so it doesn't need to be rebuilt form the cmsContentXml table.
Maybe, depending on your deployment your umbraco.config xml file out of date with your cmsContentXml table? I dunno, it certainly seems odd. You could try deleting your umbraco.config file on deployment so that it's rebuilt from the cmsContentXml table on startup.
For future reference:
Upgrading from 7.3 to 7.5 fixed this issue
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion