is there a way to reorder posts in a topic? the problem occurs when threads are created by select + move posts by multiple moderators.
8개의 좋아요
Why? Are the posts always supposed be in order of time? …because that’s not what I’m seeing.
I reproduced by selecting 10 posts from the bottom of a long topic and moving them into a new topic. Then I selected 3 from the top of the same topic and moved them into the same new topic. The 3 are showing up at the end, the 10 are showing up above the 3.
If that’s not what you were implying, ignore this post 
3개의 좋아요
Oh yes I forgot about that. Good point. We thought it would be bizarre if previously sequential posts had other posts randomly interspersed with them. So a pure time order of insertion when splitting topics seemed like a bad idea…
2개의 좋아요
Your decision was a good one, and the ability to move posts to an existing topic is awesome way of cleaning up the site, but it gets confusing if you can’t reorder.
It helps a ton when trying to keep topics on-topic.
8개의 좋아요
Hi, I just had the same problem and, I think, an easy an elegant solution would be to allow for posts to be “moved from one topic into the same topic”. At the moment it is not possible to press “Move into existing topic” and then enter the same topic ID as the original topic (e.g. moving posts from ID 10820 to ID 10820, for them to appear at the end of the post list).
What do you think about it?
3개의 좋아요
Today, I was trying to illustrate a potential use case for Discourse. We have some “weekly update” communications from various teams that are currently sent via email. I wanted to show how this would look if we did this in Discourse instead, so I was going through my inbox and copying/pasting messages into an example topic in Discourse. I wanted to change the dates to match the original email dates. This way the “gaps” and the “timeline” in the progress bar would look more “real”.
Would be cool if we could do this. (Might come up again if there’s enough interest in actually migrating old content into Discourse, though perhaps that will just be done by some other means).
4개의 좋아요
Not sure if this is the right place for this query but it was pointed out to me in reply to a topic I recently created. As I stated:
I’ve got a few dozen comments that I’m manually importing (we’re talking copying and pasting into the comment box) from Commentics to Discourse. Supposing a previous user from Commentics has set up an account with my new Discourse install I discovered that I can change ownership of the comment from me (as the copier and paster) to said user. What I’m wondering is, now that I’ve done that is it also possible to change the timestamp of said comments in a similar way to how it’s possible to change the timestamp of a topic? If not, would it be possible via some non-GUI method?
In the process of moving some wikis to discourse, I came across this issue. I’d like to do what I’ve seen here on meta where a topic has a series of wiki posts in it. This is helpful because it lets those that follow (including our future selves) to quickly edit a section without having to scroll through loads of markdown.
Reordering these posts after they have been posted becomes a challenge. Am I right in understanding that the “official” method for slotting in a post later is to select the ones that should go below, move them to a new temporary topic, then move them back again after adding the new post?
Or, if all the posts you want to reorder exist already, you’d move them into new temporary topics and then move them back in order you want?
This somehow seems.. complicated. Also, it seems to leave behind artifacts like this that I am not seeing a way to remove.
Is there something I am missing here?
5개의 좋아요
Dear all, apologies for resuming a quiet topic after some time.
For our community the ability to change the timestamp of single posts is quite important. Let me explain my case.
My community deals with space missions. I have developed a small bot that opens a new topic via API when a mission is “officially” announced, but this does not prevent our users discussing that very same mission quite in advance with respect on the API-created opening of a new topic.
Now, our need is the ability to merge the topic created via API with the one created (earlier) by our users, but having the first post of the former as the first topic of the merged topic.
As the API-created topics are (usually but not always) having one post only, at the moment our workaround is to change the timestamp of that topic and only after proceed with the merger. The situation becomes quite more complicated in case some user decides to comment in the the API-created topic before we merge. In this case a shift back of the timestamp will “drag” all posts back in time, and this is something we really don’t want.
Long story short, the abiliy to merge topics and then cherry pick posts we want to move up/down in time would be precious. If doing this in UX is considered too much of an effort, no worries. I think that even a dedicated rake task (something that takes a post_id and a ISO date as parameters) that after the change calls for the existing rake task to reorder posts in a topic could be enough.
4개의 좋아요
So, the posts:reorder_posts rake task isn’t enough for you? You can change post timestamps via API or UI before executing that task.
3개의 좋아요
Yes and no.
As said, I need a specific post to be the first of the merged duscussion thread.
Using the posts:reorder_posts option would place this “special” post right where it belongs in order of time, but that would be a no go.
So the list of actions should be:
- apply a new timestamp to a specific post (or posts)
- merge the topics
- run
posts:reorder_postsrake task to put everything where it belongs
The change of timestamp available today is applicable only to an entire topic, and all posts in that topic will be re-timestamped according to the delta time applied.
3개의 좋아요
여러분,
Keyboard Maestro 포럼에서 이 문제로 인해 곤란을 겪었습니다.
한 사용자가 동일한 작업과 관련된 여러 흔적을 남겼고, 저는 이를 통합했습니다. (그 자체가 귀찮은 작업이었죠.)
불행히도 게시글의 순서가 제자리에서 크게 벗어나 있습니다.
드래그 앤 드롭으로 순서를 바꿀 수 있다면 좋겠지만, 선택한 게시글을 맨 위로 이동하거나 맨 아래로 이동하는 기능도 없는 것보다는 훨씬 낫겠습니다.
- Chris
1개의 좋아요
이 문제에 대해 진행 상황은 어떻게 되나요? 사용 사례가 매우 설득력이 있고, 저도 최근 게시물을 통합하려고 시도하면서 동일한 문제에 부딪혔습니다. @gerhard 답글의 타임스탬프를 변경하는 방법을 어디서 알 수 있을까요? 여기에 한 가지 제안이 있지만, 절차가 복잡합니다. 서버에 접근 권한이 있다면 더 쉬울 것 같지만(아무것도 깨뜨리고 싶지는 않으니) 확실하지 않습니다.
1개의 좋아요
저도 이 부분에 대한 진전을 보고 싶습니다. 약간 주제에서 벗어난 몇 가지 답변을 분리했는데, 각각에 맥락이 필요했습니다. 그래서 원래 주제와 관련된 내용을 인용하는 게시글을 추가해 보았지만, 해당 게시글은 이동한 게시글들 맨 아래에 위치하게 되었습니다.
결국, 제자리에 맞지 않아 삭제했습니다.
1개의 좋아요
게시물의 타임스탬프를 변경하는 방법에 대한 간단한 안내입니다. 새 주제(원문)인지 답변인지에 따라 수작업으로 해야 할 작업의 양이 달라집니다.
Meta에서 change post time stamp를 검색하면 꽤 많은 결과를 확인할 수 있습니다. 그중에는 원하시는 내용이 정확히 포함되어 있을 수도 있습니다.
1개의 좋아요
감사합니다, @JimPas. 답변 순서 변경에 대한 ‘우회 방법’ 덕분에 최종적으로 매우 간단한 해결책을 찾았습니다. 원래 게시물에 대한 소개를 포함하여 새 게시물을 만들고, 원래 분할된 게시물의 답변들을 새 토픽으로 옮긴 다음, 원래 분할된 게시물을 삭제했습니다.
중간 단계의 게시물을 삭제했기 때문에, 원래 토픽의 분할 참조 링크를 올바른 토픽을 가리키도록 업데이트해야 했습니다. 앞으로 다시 소개를 추가하고 싶다면, 먼저 해당 토픽을 생성한 후 관련 답변들을 그쪽으로 옮기는 것이 좋습니다. 이렇게 하면 오래된 링크 문제를 방지할 수 있습니다.
3개의 좋아요
이 부분에 대해 진전이 있나요?
Select Posts에 추가해야 합니다.
1개의 좋아요
이 우회 방법을 시도해 보았지만, 스레드를 삭제하지 않고 첫 번째 소개 참조를 삭제하는 방법은 무엇인가요?
종종 기존 스레드에 게시물을 올리는 사용자가 있고, 원래 날짜 순서를 유지하면서 이를 별도의 스레드로 분리해야 하므로 이 기능은 매우 중요합니다. 구현되기를 바랍니다.
1개의 좋아요
안녕하세요 @ianm, 정확히 어떤 결과를 원하시는지 잘 모르겠네요. 제 경우에는 토픽을 분리한 이후에 토픽 끝에 추가했던 컨텍스트 게시글이 순서가 어긋나서 삭제했습니다.
스레드의 첫 번째 게시글은 (스레드 전체를 삭제하지 않는 한) 삭제할 수 없습니다. 하지만 토픽을 분리할 때는 기존 토픽으로 게시글을 보내거나 새 토픽으로 보낼 수 있습니다. 먼저 새 토픽의 시작이 될 소개글을 작성한 다음, 해당 새 토픽으로 분리하면 첫 번째 게시글이 내 소유가 되어 원하는 대로 처리할 수 있습니다. 그렇지 않으면 분리된 첫 번째 답변이 스레드의 시작이 됩니다.
결국 저는 두 번째 방식을 사용했습니다. 이해가 되시나요?
1개의 좋아요