Copied to clipboard

Flag this post as spam?

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


  • Ernst Utvik 123 posts 235 karma points
    Sep 29, 2010 @ 22:50
    Ernst Utvik
    0

    Nodes listing two times in node tree

     

    After creating node in UC the node shows two times in node tree (same node ID). If i republish it in umbraco and reload nodes the duplicate goes away. This worked fine on my development server.

    I use the following code for publishing the node.

    doc.Publish(author);
    umbraco.library.UpdateDocumentCache(doc.Id);

    Input appreciated :)

    I use Umbraco 4.5.2 .net4 on a mySql database

  • Ernst Utvik 123 posts 235 karma points
    Sep 30, 2010 @ 11:59
    Ernst Utvik
    0

    Adding an extra

    umbraco.library.UpdateDocumentCache(doc.Id);

    seemed to fix the problem but 5 minutes later it returned. I'm kinda clueless on this one. Could it be a bug of some sort related to the caching?

  • Ernst Utvik 123 posts 235 karma points
    Oct 04, 2010 @ 11:10
    Ernst Utvik
    0

    Still no luck with this one. The nodes on the posted picture shows twice in the tree but has the same node id. Republishing in Umbraco fixes the tree.

  • Jeroen de Visser 5 posts 25 karma points
    Jun 09, 2011 @ 15:19
    Jeroen de Visser
    0

    Same problem here... also with Umbraco 4.5.2/MySQL.

    Some items are shown twice in the content tree. The items have the same nodeID.

    Did you already found a solution for this issue?

    Best regards,
    Jeroen

  • Bo Damgaard Mortensen 719 posts 1207 karma points
    Jun 10, 2011 @ 21:36
    Bo Damgaard Mortensen
    0

    Hi Ernst and Jeroen,

    It seems to be an issue when running Umbraco on MySQL. An easy-but-dirty fix for this is to call the PublishWithResultWithChildren (or is it PublishWithChildrenWithResult() ?! - can't remember) on the nodes Parent node when you publish your new node.

    While this should fix the problem there's some flaws doing it this way:

    1) If there's any documents that's going to be "Published At" a given date, these will be published aswell when running the above method. (I think, haven't actually tested it yet, to be honest)

    2) If there's a lot of childnodes in the parent node, this will eventually cause some overhead.

  • Ernst Utvik 123 posts 235 karma points
    Jun 14, 2011 @ 00:35
    Ernst Utvik
    0

    Thnx for the "dirty-fix" Bo. Will keep that in mind if I run into another Mysql install.

    Never found a solution myself so we went with i mssql database wich works flawlessly.

  • Bo Damgaard Mortensen 719 posts 1207 karma points
    Jun 14, 2011 @ 01:28
    Bo Damgaard Mortensen
    0

    All good Ernst :-)

    I've also switched to MSSQL for Umbraco solutions depending on the size of the site.

Please Sign in or register to post replies

Write your reply to:

Draft