Hi Bo,

A way to create/publish new nodes that's always worked for me is:

DocumentType docType = DocumentType.GetByAlias("something");
User nodeAuthor = User.GetUser(0);
Document doc = Document.MakeNew(titleString, docType, nodeAuthor, parentNodeId);
doc.getProperty("someProperty").Value = contentString;
doc.Publish(nodeAuthor);
library.UpdateDocumentCache(doc.Id);

I hope this helps.

David

Hi David,

Thanks for your input :-)

I just tried to skip the umbraco.library.RefreshContent();, but that didn't work either. Also, I just installed a completely fresh copy of Umbraco JUNO and after the first document was created, it started to make duplicates again. It seems like I'm the only one having that problem ;-) This is the simple test I just did on the new Umbraco installation:

Frontend:

<p>
  <asp:TextBox TextMode="MultiLine" runat="server" ID="txtContent" Height="223px" Width="404px"></asp:TextBox>
</p>
<p>
    <asp:Button ID="Button1" runat="server" Text="Submit" onclick="Button1_Click" />    
</p>

And the codebehind:

DocumentType dt = DocumentType.GetByAlias("LinkTest");
Document doc = Document.MakeNew(DateTime.Now.ToShortDateString(), dt, new User(0), 1047);
doc.getProperty("bodyText").Value = txtContent.Text;
doc.Save();
doc.Publish(new User(0));
umbraco.library.RefreshContent();
umbraco.library.UpdateDocumentCache(doc.Id);

What exactly am I doing wrong? 

All the best,

Bo

Also, if i'm looking at the content section in Umbraco, then create a new document from the webform, refresh the content tree, switch to i.e. the Settings section and back to the contenttree - the newly created documents name is duplicated after each other until I reload the nodes again (?) Like this:

Here I have switched back and forth between the Content section and the Settings section three times (as you can see, the name of the node(s?) is duplicated x 3.

Something is wrong.. ;-)

Hi again David and thanks for your reply.

I've been looking at the 4.6.2 changesets but failed to find the one (c3327b2d6a99) Niels wrote about on the workitem you linked to. Was just wondering if this fix is underway or if I'm just plain blind ;-)

Thanks again for your help! Appreciated!

/ Bo

Edit: turns out that I was just blind. Found the workitem, but I'll just use MSSQL for my future umbraco projects since it seem to solve the problem.

Hi Bo,

I'm having the same problem (I'm using mySql as database) - but it seems that a republish of the parentnode, and subnodes, fixes the double node issue.

Found the tip with republishing here: http://our.umbraco.org/forum/developers/api-questions/13132-Nodes-listing-two-times-in-node-tree

code should look something like this

                    // After creating your nodes that normally doubles
                    

           sb.Append("Republishing parentfolder with subnodes");

                    Document parentDocument = new Document(parentId);
                    parentDocument.PublishWithSubs(new User(0));
                   

           sb.Append("Republishing done");

Update: seems a RefreshContent() is needed after re-publish for Umbraco not to puke

          umbraco.library.RefreshContent();

/Søren

Hi Søren,

Thanks a lot ! Hero of the day! ;-)

It works like a charm, but i'm running into a problem where any unpublished documents that are scheduled to publish on a certain day/time, will be publieshed aswell :-/ Any workarounds for this?

Thanks again!

/ Bo

Hi Bo,

Great to hear it workd for you too :)

Off the top of my head I would guess that the [document].ReleaseDate could be checked to see if it is to be published in the future, and that [document].ExpireDate could be checked to see if it has been unpublished. You should however make a loop on the subs of your parentnode, instead of using parentDocument.PublishWithSubs(new User(0));

so code would look something like this:

   foreach (Document document in Document.GetChildrenForTree(parentId))
        {   

   if (document.ReleaseDate is not to be published yet thene...)

   else { document.Publish(new User(0)); }

        }

Do let me know if it works out for you :)

Hey Søren,

Looping through the childnode collection was my first idea, but wouldn't it be the publishWithSubs() method that solves the issue? Could just do a check on the document.IsPublished() method, but I'm not sure if it works just by calling the Publish() method on the node. Seems to be the parent node that needs to be published with all the childnodes. I might aswell be very wrong about this ;-) I'm working on-site today so I can't test it yet, sadly.

Thanks again!

- Bo

is working on a reply...