It seems many people are running into the same type of issue but I have yet to find a definitive answer or fix.
I'm simply using the Publish At feature and the node appears published in the admin. But it does not get a proper URL set until I manually run a "Republish Entire Site".
Here's my audit trail:
Error publishing node: System.NullReferenceException: Object reference not set to an instance of an object.
at umbraco.cms.businesslogic.web.Access.IsProtected(Int32 DocumentId, String Path)
at umbraco.cms.businesslogic.web.Access.GetAccessingMembershipRoles(Int32 documentId, String path)
at umbraco.presentation.nodeFactory.UmbracoSiteMapProvider.findRoles(Int32 nodeId, String nodePath)
at umbraco.presentation.nodeFactory.UmbracoSiteMapProvider.UpdateNode(Node node)
at umbraco.content.UpdateDocumentCache(Document d)
at umbraco.library.UpdateDocumentCache(Int32 DocumentId)
at umbraco.presentation.publishingService.CheckPublishing(Object sender)
Publish At Issues - umbraco v 4.7.0.RC
It seems many people are running into the same type of issue but I have yet to find a definitive answer or fix.
I'm simply using the Publish At feature and the node appears published in the admin. But it does not get a proper URL set until I manually run a "Republish Entire Site".
Here's my audit trail:
Error publishing node: System.NullReferenceException: Object reference not set to an instance of an object. at umbraco.cms.businesslogic.web.Access.IsProtected(Int32 DocumentId, String Path) at umbraco.cms.businesslogic.web.Access.GetAccessingMembershipRoles(Int32 documentId, String path) at umbraco.presentation.nodeFactory.UmbracoSiteMapProvider.findRoles(Int32 nodeId, String nodePath) at umbraco.presentation.nodeFactory.UmbracoSiteMapProvider.UpdateNode(Node node) at umbraco.content.UpdateDocumentCache(Document d) at umbraco.library.UpdateDocumentCache(Int32 DocumentId) at umbraco.presentation.publishingService.CheckPublishing(Object sender)Any help or insight is much appreciated!
Bumpity bump!
When publication is working from separate thread HttpContext.Current=null,
in that case following code could work problematicaly:
HttpContext.Current.Application.Lock();
As for me is better to change this part of code to lock other one, specific [lockobject]
in other cases you have to set: HttpContext.Current to correct value.
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.