As far as I understand, when you right click and republish the entire site or /umbraco/dialogs/republish.aspx?xml=true, the xml cache on disk is updated from the xml cache in the database. Those republishes are sort of a shallow republish. As you have seen, to do a more thorough republish that will regenerate the cmsContentXml table, you can go to each individual node and click "Save and Publish" because that causes the full republish all the way down to the cmsContentXml. You should be able to right click on a node in the umbraco backoffice (probably the home page in your case) and then click publish and check "Publish Homepage and all of its subpages" to cause the deep republish to happen to nodes en masse. Because the deep republish hits the database, this mass, deep republish might take a while to complete.

Hope that helps.

I thought the XML=true option was supposed to refresh the cmsContentXML table as well as rebuild the umbraco.config file but maybe I am wrong, which seems to be the case based on my testing. To actually republish all the nodes would take a very long time and I am pretty sure when I have tried this before from within umbraco by right clicking on the top level of a large website it ends up timing out.

Is anyone able to clarify either way whether or not I should be able to rebuild the cmsContentXml table without having to publish every single node in my website?

If I do have to publish every single node then I will need to write something do this by looping through each node because I am sure that the publish features in Umbraco will time out with the sheer amount of nodes in my website.

You could try doing it in chunks. Start at a lower level node maybe?

I was looking around in the umbraco services documentation and found something that looks promising on the ContentService. Haven't tried it yet. Let me know if it works:

.RebuildXmlStructures(params int[] contentTypeIds)

    Rebuilds all xml content in the cmsContentXml table for all documents matching the IDs passed in.
    If none then rebuilds the structures for all content.

https://our.umbraco.org/documentation/Reference/Management/Services/ContentService

Hi Mark,

Thank you for the response, I had a look at this but it appears the .RebuildXmlStructures option no longer exists, the only one I could find that was similar was .RepublishAll but I tried that and it does not update the cmsContentXml table.

Any other suggestions or does it look like I am going to have to split the nodes into chunks and use .PublishWithStatus or .PublishWithChildrenWithStatus?

Hi Mark,

I'm encountering this too, what approach did you take in the end please?

Previously, republish.aspx?xml=true did indeed rebuild the cmsContentXml table but since v7 it looks like the query string doesn't do anything anymore.

My site has 100k + nodes. A manual republish just isn't feasible.

Really hope to hear back from you!

I had to write a custom usercontrol that looped through all nodes and published them manually. This wasn't too much of an issue for me because I was working on a test site.

I've got a workable solution to updating the cmsContentXml table without using the built-in republish.aspx?xml=true feature and without doing a monster republish:

@inherits Umbraco.Web.Mvc.UmbracoTemplatePage
@using System;
@using umbraco.cms.businesslogic.web;

@{
    Layout = null;
    var start = DateTime.Now;

    Server.ScriptTimeout = Int32.MaxValue;
    System.Xml.XmlDocument xd = new System.Xml.XmlDocument();

    var startNode = Request.QueryString["start"];

    var docsToClear = Umbraco.TypedContentAtRoot().DescendantsOrSelf(Request.QueryString["dt"]);

    if (startNode != null)
    {
        docsToClear = Umbraco.TypedContent(startNode).DescendantsOrSelf(Request.QueryString["dt"]);
    }
}
<ul>
    @foreach (var doc in docsToClear)
    {
        try
        {
            var d = new Document(doc.Id);
            d.XmlGenerate(xd);
            <li>Created Xml for:  @doc.Id @(doc.Name)</li>
        }
        catch (Exception e)
        {
            <li>ERROR Xml for:  @doc.Id <br /><br />@e.Message</li>
        }
    }
</ul>
@{
    umbraco.library.RefreshContent();
}
@docsToClear.Count() nodes refreshed. Time expired: @(DateTime.Now - start)

I'm under no illusions - this is a bit quick and dirty and is suited to my purpose of refreshing all the nodes of a particular type but is easy to change and might be useful to someone...

B

is working on a reply...