Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Steve Bridges 51 posts 72 karma points
    Sep 19, 2012 @ 04:54
    Steve Bridges
    0

    Duplicate nodes in content tree after deployment with Courier

    My Development region is fine and the tree looks like this:

    Home

    --Category

    ----subpage A

    -------- supbage A1

    ---------subpage A2

    ---subpage B

    -------------subpage  B1

    ------------- subpage B2

    (etc)

     

    After deploying to the staging environment with Courier, the staging environment looks like this

    Home

    --Category

    ----subpage A

    -------- supbage A1

    ---------subpage A2

    ----subpage A

    -------- supbage A1

    ---------subpage A2

    ---subpage B

    -------------subpage  B1

    ------------- subpage B2

    --subpage B

    -------------subpage  B1

    ------------- subpage B2

    (etc)

    All nodeids for this category section are duplicated.  I"ve tried deleting the section completely from staging and redploying - with the same result.  I've confirmed via fiddler that the treedataservice.ashx is returning duplicate nodes.

    Please help!

    Umbraco 4.9

    Courier 2.7.2

     

  • Steve Bridges 51 posts 72 karma points
    Sep 19, 2012 @ 05:13
    Steve Bridges
    0

    Just a bit more info - i just added a subpage to another "category" page - and that transferred fine.

    So far it seems to be only the children of this one particular node.  

  • Steve Bridges 51 posts 72 karma points
    Sep 19, 2012 @ 16:52
    Steve Bridges
    0

    UPDATE:  

    I narrowed this down to one particular doctype.  This doctype allowed two templates.    When i removed the 2nd template and only allowed 1 template the problem went away.

    I haven't looked into the core sourcecode - but could there be an issue with the joins in the queries for the tree loading?

    I can't mark this as solved as if i still need a doctype with two templates it's still broken.  But at least i found a temporary workaround.

     

     

  • 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.

Please Sign in or register to post replies