Move ForumReply using PublicApi - is that possible?

Move ForumReply using PublicApi - is that possible?

This question has suggested answer(s)

Hi according to the ForumRepliesUpdateOptions I am not able to move a reply from one thread to another. Is it not possible?

Thanks,

Anders

All Replies
  • In the front end, you "split" the thread into a new thread at the selected reply. You can't move single replies from one thread to another.

    It looks like we support a ParentReplyId in the Update Forum Reply REST endpoint: telligent.com/.../29619.update-forum-reply-rest-endpoint.aspx. Let me verify that this is a good way to go...

  • Whoops, I meant ThreadId, not ParentReplyId.

  • We do not (yet) offer the ability to split a thread (or many other moderation-type functionality) via the public APIs. The ThreadId param included in the REST URL (~/api.ashx/v2/forums/{forumid}/threads/{threadid}/replies/{replyid}.xml) or in the In-process API's Get method is used to identify/find the reply not for setting the value.

  • What other options do we have to do this in code? The ForumServices class in CommunityServer.Discussions is no longer. Is there a similar service layer in TC?

    Thanks for the other replies.

  • We do not have anything that is extensible or upgrade safe in the public APIs for doing so.

    The internal APIs for splitting a thread are in the Telligent.Evolution.Discussions.Components.Moderate class, specifically the PromoteReplyToThread() and MovePost() methods.

    Again, because these are not part of the public APIs they are not upgrade safe so use them understanding that our internal APIs can change or disappear at any time.

  • I see you are using Ninject for DI. I have now injected my own ForumService (inherites from Telligent.Evolution.Rest.Resources.ForumReplies.ForumService) class in order to intercept the CreateReply method. And then creating a thread if I need to for the reply. Luckily the Posts.AddThread is still available so that I can specify the author.

    I will add a notice that this should be replaced with the PublicApi when specifying an author becomes available (if ever).

    Thanks Dan.