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.
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.
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
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?
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.
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
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.
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.
All good Ernst :-)
I've also switched to MSSQL for Umbraco solutions depending on the size of the site.
is working on a reply...