hi, I think is the node 's cache in umbraco.config not exist, so is Link to document property will be [parentNotPublishedAnomaly]
when you do this action [Republish entire site] will cause this problem, but this bug already fix in ver 6+
Other way when you do load balance , if the back office site's url not config in umbracoSettings.config or have no right to visit TEMP, also cause the problem, because
when you publish node, it could not exec webservice to refresh the cache, so the node will be [parentNotPublishedAnomaly]
the server is just a single system without load balancing. Anyway, this issues happens to all nodes when we install this ImageGen package. Republishing the entire site doesn't help. We have to republish every single node to make our site work again. That's pretty much annoying and a lot of effort.
Thanks for your reply. Your english is fine for me. ;-)
I had the same thing happen to me after I deployed an upgrade to an Umbraco website. I figured it has to be some cache thing, so after restarting the application pool (with no changes) I went and deleted the APP_Data/umbraco.config file and now it works.
parentNotPublishedAnomaly exception
All nodes Link to document property have become
[parentNotPublishedAnomaly]
why?
thanks in advance
Hi Yumin
What version of Umbraco are you using?
/Jan
4.11.7
is a bug already fix in 6.1.1
Strange, we have 6.1.1 running and this happened today twice to us when we installed the ImageGen package.
hi, I think is the node 's cache in umbraco.config not exist, so is Link to document property will be [parentNotPublishedAnomaly]
when you do this action [Republish entire site] will cause this problem, but this bug already fix in ver 6+
Other way when you do load balance , if the back office site's url not config in umbracoSettings.config or have no right to visit TEMP, also cause the problem, because
when you publish node, it could not exec webservice to refresh the cache, so the node will be [parentNotPublishedAnomaly]
my english very poor ,wish you can understand,hah
Hi,
the server is just a single system without load balancing. Anyway, this issues happens to all nodes when we install this ImageGen package. Republishing the entire site doesn't help. We have to republish every single node to make our site work again. That's pretty much annoying and a lot of effort.
Thanks for your reply. Your english is fine for me. ;-)
Best
Jörg
Hi,
I had the same thing happen to me after I deployed an upgrade to an Umbraco website. I figured it has to be some cache thing, so after restarting the application pool (with no changes) I went and deleted the APP_Data/umbraco.config file and now it works.
Cheers
Bjørn
is working on a reply...