It sounds probably ridiculous since people usually want to avoid or remove duplicate threads. However I have a use case right now where I need to duplicate a thread. How can I do it?
「いいね！」 2
Manually ? You can navigate to the raw contents of the topic by going to /raw/{topic_id} and copying everything there.
So, https://meta.discourse.org/t/195111 becomes https://meta.discourse.org/raw/195111
By the way, Discourse calls topics what you call “threads”
Edit: or, if you are TL4/staff you can just click edit and copy everything there
「いいね！」 4
Actually that doesn’t do what I need. I want all the topic with all the replies. I want an exact duplicate of the thread, but with different topic_id
「いいね！」 1
I found a way to “reproduce” a whole thread which was laborious but no way to truly duplicate it. (Retaining the likes for instance)
I create a new thread and put it in a non accessible category e.g. staff. I copy each reply from the original topic tread and paste it in a reply in the new topic thread. For replies I only need in the new topic thread, I just select and move them. Then I change ownership of the copied reply to the name of the poster of the original reply. Once I am done, I close the original thread and I change the category of the new topic to a public category.
Of course this is too painstaking to use on a regular basis. The reason I needed to do it this time was because someone created a topic with a very long title that could be interpreted in two different topic threads. We (moderators) noted the issue of long title (this will be restricted to less characters now) but didn’t realize at that time that it would cause a problem.
The conversation started and before we knew it, we had two very intertwined delicate conversations going on, with some offensive comments from one member that nevertheless provoked a rich series of responses in both matters.
To retain the richness of the contributions that had taken place, to reprimand the repeated offender, to use the event for community educational purpose and to permit both valuable conversations to grow each their way, I determined that it was best to split the topics apart, keeping only the pertinent interventions to each but not hesitating to repeat in both the interventions that were covering both matters for clarity comprehension purposes.
In the topic thread that retained the offensive reply, I also put a staff notice before the offensive post saying that it wasn’t in accordance with our community values but that we’d let it for educational purpose. I doctored that post in the following manner: I put the markdown code < del >
In front of the offensive language
I explained that to express his opinion in a constructive manner the member
would have been better wording it
< ins > this way instead.
That was a lot of work and thinking. I would not do that again manually. But the use case is definitely there.
「いいね！」 2
That sounds like a lot of work! You might get better feedback next time when you don’t just ask for technical support (“How can I duplicate a topic?”), but explain the situation and what you want to achieve in your initial post. E.g. you probably could have just closed the topic, put a staff note as last post and link it to two new topics where the respective discussions could continue?
「いいね！」 7
I can’t blame you for your comment: we often ask what is the goal when people ask for technical stuff about fmpro on our board.
However I was dead set on my intent to experiment this approach with the current situation. I knew about closing thread and starting two new topics. I wanted to use the existing material for educational purposes.
We have a very good community, lots of great contributions. However, we were born out of frustration with the vendor’s platform. So I have been using various approach and change management techniques to help people move away from the whining and bitching about the vendor.
Most have progressed in the way they express critical opinions about the product or the vendor. Unfortunately a few individuals had the tendency to stir the pot and brought upon the community a bad reputation and valuable members of the ecosystem whom have a closer or privileged relationship with the vendor won’t come near us. Which is unfortunate because we have grown organically as most people when they become aware that we exist like the forums and want to stay and these stellar members were bringing in valuable expertise and content.
Two very reputable and esteemed developers had to withstand bickering and had to “work” too hard to rectify information and lost the motivation and fun to contribute and removed themselves.
We did moderate but it was just unpleasant to constantly have the same irritating behaviours resurfacing and by trying to give everyone the right to their say, I eventually realize that it was somewhat unfair on everyone to have to exercise tolerance and forcing them to witness unpleasantries because a few would not refrain from being jerks.
Our FAQ did nit impress upon them the faculty to observe and recognize the faults in their interactions. Instead of do’s and don’ts, or guidelines people interpret how they want anyway, our new administrator decided to promote values instead. It turns out it is easier to moderate because we just say that post doesn’t abide by our community values so it was edited (or hidden until you modify it).
However we eventually realized that doing this didn’t help people who have been communicating poorly all their lives to know how to do better.
So now we are adding educational interventions, basically metacommunicating, directly in the threads. We’ll se how that turns out.
「いいね！」 5
I know, @HAWK even edited my title to reflect that.
I use threads exactly to avoid what happened here: your suggestion was a solution to duplicate the topic (aka the initial post). However what I wanted was a solution to duplicate the whole thread (which is the the initial post aka topic + all the following replies.
In other words, when you create a new topic and people post replies, what you get is a thread.
That’s the thing – you don’t… There is literally no such thing as a thread in Discourse. The first post and all responses together are called a topic.
「いいね！」 2
I will accept the concept you expose in the context of Discourse. However, linguistically, philosophically, and historically in the online fora domain, thread is what best describe the thing that has for components a titled initial post and the following replies. 
「いいね！」 1
Agreed, but the thing that you’re missing here is that Discourse doesn’t have threading like all other forum platforms do. That is literally why we make this distinction.
「いいね！」 4
You make a point. In this case a discussion or conversation might be a better term since it is less specific about the design uniting the components 
「いいね！」 3
Googleでトピックの定義を検索できます。
top·ic
/ˈtäpik/
テキスト、議論、会話で扱われる問題。主題。
これはかなり正確です。個人的な理由で別の単語を使いたい場合は、Discourseで管理者のカスタマイズから編集できます。
元の件については…
トピックの管理者のレンチを押してトピックを分割し、別のリンクされたトピックに「別の」トピックに関する返信を移動させるのはどうでしょうか？それは、Discourseの多くのツールによってサポートされている、より簡単な行動でしょう。
「いいね！」 2
なぜなら：
「トピックを分割し、それぞれに関連する投稿のみを保持したいのですが、両方にまたがる投稿は明確化と理解のために両方に含めることをためらわないようにしたいのです。」
投稿を元のトピックに残したまま新しいトピックにコピーする方法がまだわからない限り、あなたが提案する方法では、理解を深めるために特定の返信を両方のトピックに残すことができません。
なるほど、引用が多く含まれる絡み合った返信があると複雑になるかもしれませんが、それは比較的まれなケースでしょう。私はほぼ10年間、あらゆる形態のメタでモデレーションを行ってきましたが、トピック全体を複製する必要があったという状況はほとんど思いつきません。通常のトピック分割で十分な場合が多いです。
「いいね！」 2
ジェフ、トピック全体を複製できると非常に役立つユースケースがあります。
私たちは、特に労働組合であるビジネスコラボレーションのためにインスタンスを使用しています。各会議で、TOCスタイルの8つの投稿でスレッドを作成します。
各会議の投稿1〜8は、トピック内で非常に異なりますが、毎月同じ形式で、特定の情報が貼り付けられるだけです。最初の投稿だけでなく、トピック全体をテンプレート化し、毎月複製して月次情報を挿入できる機能があれば、非常に役立ちます。
現在、各投稿1〜8のテンプレートを含むトピックをプライベートカテゴリに作成しました。現在、分割画面で新しいトピックを開き、テンプレートトピックから新しいトピックに投稿1をコピーし、次に投稿2、次に投稿3などをコピーする必要があります。
これは非常に珍しいユースケースですが、トピックをクローンする管理者機能、またはカテゴリにネストされた複数の個別の返信テンプレートをトピックテンプレートに含めるようにトピックテンプレートを拡張する方法があれば、非常に役立つインスタンスがいくつかあります。
現在、トピックテンプレートまたはウィザードであっても、私ができることは、空の投稿#1を複製することだけです。
「いいね！」 1
こんにちは。
Discourse Canned Replies は、この問題に対するより良い解決策にはならないでしょうか？トピックと投稿に対して一度作成すれば、テンプレートを簡単に選択できます。
「いいね！」 4
そうですね…うまくいきそうです。見てみましたが、とても励みになります。@Don ありがとうございます！
「いいね！」 4
こちらもユースケースがあります。プライベートなヘルプ要求の手段としてPMを使用していますが、ユーザーに要求を公開することを奨励しています。支援からより多くの人が恩恵を受けられるように、公開ヘルプ要求を優先しています。
理想的には、OPのヘルプ要求と選択された返信を新しい公開トピックにコピーし、自動応答メッセージと、公開できるかどうかを尋ねる返信などを除外します。
現状では、PMトピックをプライベートカテゴリのフルスレッドにし、表示したくない返信を削除してから、公開エリアに移動する必要があります。
なぜ逆の方法でやらないのですか？公開したい投稿を選択し、新しい会話に移動して、それを公開トピックにするのですか？公開したくないものをすべて削除するよりも、慎重に公開するものを選ぶ方が安全だと感じます。
「いいね！」 4
それは良い点ですね。OPの投稿は新しいトピックに移動できないと仮定していました。いくつかテストをして、どのように機能するか見てみます。提案ありがとうございます。
「いいね！」 1