Hello, does anyone have a suggestion or solution for solving the problem described here pernamently and that doesn't involve deleting the nodes? The fix works, but we are deleting and reentering far too many nodes.
Issue: There has been a random bug in some builds of Umbraco whereby the rich text editor is allowing certain characters (in a variety of character sets) to get entered - which although the database supports, when it comes to Umbraco creating the standard XML umbraco.config file - are not supported, thereby stopping full publishing. This can result in page not found errors, despite the page actually being published. Often this error is as a result of pasting text in from other programs (Notably: Adobe InDesign {wiki: others...}) that are using a variety of character sets.
How to fix:
The way to fix this issue is to find the page that has the problematic characters within and either delete it, or remove the problem characters. The quickest way to find the pages with the bad characters is to open up the Umbraco site database in SQL Server Management Studio Express and issue the following query:
select distinct contentNodeId, path, text
from cmsPropertyData
inner join umbracoNode on umbracoNode.id = cmsPropertyData.contentNodeId
where dataNtext like '%�%'
This should give you a list of nodes which have the bad characters - you can then fix them accordingly. After which, delete the umbraco.config file mentioned above and then do a full site re-publish (right-click the root node in the Umbraco admin panel and select publish)
Umbraco Version: 4.0.1
asp.net version: 3.5
Windows and iis version: 2003 & IIS 7
Stacktrace:
[NullReferenceException: Object reference not set to an instance of an object.]
umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +54
umbraco.controls.ContentControl..ctor(Content c, publishModes CanPublish, String Id) +780
umbraco.cms.presentation.editContent.OnInit(EventArgs e) +368
System.Web.UI.Control.InitRecursive(Control namingContainer) +333
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378
Publishing problems / bug
Hello, does anyone have a suggestion or solution for solving the problem described here pernamently and that doesn't involve deleting the nodes? The fix works, but we are deleting and reentering far too many nodes.
http://our.umbraco.org/wiki/how-tos/fix-odd-publishing-problems
Fix 2:
Issue: There has been a random bug in some builds of Umbraco whereby the rich text editor is allowing certain characters (in a variety of character sets) to get entered - which although the database supports, when it comes to Umbraco creating the standard XML umbraco.config file - are not supported, thereby stopping full publishing. This can result in page not found errors, despite the page actually being published. Often this error is as a result of pasting text in from other programs (Notably: Adobe InDesign {wiki: others...}) that are using a variety of character sets.
How to fix:
The way to fix this issue is to find the page that has the problematic characters within and either delete it, or remove the problem characters. The quickest way to find the pages with the bad characters is to open up the Umbraco site database in SQL Server Management Studio Express and issue the following query:
select distinct contentNodeId, path, text from cmsPropertyData inner join umbracoNode on umbracoNode.id = cmsPropertyData.contentNodeId where dataNtext like '%�%'
This should give you a list of nodes which have the bad characters - you can then fix them accordingly. After which, delete the umbraco.config file mentioned above and then do a full site re-publish (right-click the root node in the Umbraco admin panel and select publish)
Umbraco Version: 4.0.1
asp.net version: 3.5
Windows and iis version: 2003 & IIS 7
Stacktrace:
[NullReferenceException: Object reference not set to an instance of an object.] umbraco.controls.ContentControl.addControlNew(Property p, TabPage tp, String Caption) +54 umbraco.controls.ContentControl..ctor(Content c, publishModes CanPublish, String Id) +780 umbraco.cms.presentation.editContent.OnInit(EventArgs e) +368 System.Web.UI.Control.InitRecursive(Control namingContainer) +333 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378
is working on a reply...