I have an Umbraco Project based on v4.11.4 with legacy schema. I did upgrade to v6 yesterday evening. This worked like a charm.
But this morning I found out, that when I publish a page, the XSLT macro has a problem. In my case, the macro for the main navigation on the website stopped working (Error parsing XSLT file: \xslt\navi.xslt). I compared the XML content for the node I published in v6, with the XML content from the same node in my v4 backup database. This is what WinMerge (left: v6, right: v4) shows me:
The problem is, as you can see, the data nodes. They have no alias attribute! Interestingly, there is a new attribute on the node called isDoc . This is an attribute for the "new" XML schema, but I have instructed Umbraco to use the legacy schema.
Now it works again, after a/umbraco/dialogs/republish.aspx?xml=truerepublish. (The republish through the backend [right click on "Content" > "Republish entire site"] didn't work.)
But everytime I want to publish a page in the backend, the same error strikes back. It also shows a YSOD to the user who wants to publish the page:
[NullReferenceException: Object reference not set to an instance of an object.]
Umbraco.Web.Models.XmlPublishedContentProperty..ctor(XmlNode propertyXmlData) +230
Umbraco.Web.Models.XmlPublishedContent.Initialize() +2106
Umbraco.Web.DefaultPublishedContentStore.ConvertToDocument(XmlNode xmlNode) +297
Umbraco.Web.DefaultPublishedContentStore.GetDocumentById(UmbracoContext umbracoContext, Int32 nodeId) +89
Umbraco.Web.Routing.NiceUrlProvider.GetNiceUrl(Int32 nodeId, Uri current, Boolean absolute) +195
umbraco.cms.presentation.editContent.UpdateNiceUrls() +251
System.Web.UI.Control.PreRenderRecursiveInternal() +112
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4296
I have the same problem as well. Did you solve this Sandro? Or do you have to publish using "republish.aspx?xml=true"? Have anyone reported this as a bug?
I don't know the source of the problem. Like you, I also have the standard Examine config. Only that "Save & Publish" generates a bad XML as you can see in my first post. The problem is not yet solved.
v6 upgrade issue: Problem with XML after publish
Hi
I have an Umbraco Project based on v4.11.4 with legacy schema. I did upgrade to v6 yesterday evening. This worked like a charm.
But this morning I found out, that when I publish a page, the XSLT macro has a problem. In my case, the macro for the main navigation on the website stopped working (Error parsing XSLT file: \xslt\navi.xslt). I compared the XML content for the node I published in v6, with the XML content from the same node in my v4 backup database. This is what WinMerge (left: v6, right: v4) shows me:
The problem is, as you can see, the
datanodes. They have noaliasattribute! Interestingly, there is a new attribute on the node calledisDoc. This is an attribute for the "new" XML schema, but I have instructed Umbraco to use the legacy schema.This could be a bug. Maybe try to republish first? http://our.umbraco.org/wiki/reference/api-cheatsheet/publishing-and-republishing
Otherwise you could report it at http://issues.umbraco.org/dashboard#newissue=yes
Jeroen
Now it works again, after a
/umbraco/dialogs/republish.aspx?xml=truerepublish.(The republish through the backend [right click on "Content" > "Republish entire site"] didn't work.)
But everytime I want to publish a page in the backend, the same error strikes back. It also shows a YSOD to the user who wants to publish the page:
I have the same problem as well. Did you solve this Sandro? Or do you have to publish using "republish.aspx?xml=true"? Have anyone reported this as a bug?
I guess that it's the Examine indexer that don't know how to index the legacy schema?
I don't know the source of the problem. Like you, I also have the standard Examine config. Only that "Save & Publish" generates a bad XML as you can see in my first post. The problem is not yet solved.
The issue URL: http://issues.umbraco.org/issue/U4-1721
Edit: Sebastiaan has fixed it http://umbraco.codeplex.com/SourceControl/changeset/48554a2480f7#src/Umbraco.Core/Models/PropertyExtensions.cs.
is working on a reply...