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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
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 curtidas
E aĂ, pessoal,
Acabei de ser pego por isso no FĂłrum do Keyboard Maestro.
Tivemos um usuário deixando rastros por toda parte relacionados à mesma tarefa, e eu consolidei-os. (Uma tarefa chata por si só.)
Infelizmente, a ordem dos posts está bem fora do lugar.
Embora seria bom poder arrastar e soltar para reordenar, algo como mover-post(es)-selecionado(s)-para-o-topo e/ou mover-post(es)-selecionado(s)-para-o-fundo seria muito melhor do que nada.
- Chris
1 curtida
Houve algum progresso nisso? Os casos de uso são convincentes e eu recentemente me deparei com o mesmo problema ao tentar consolidar posts. @gerhard, onde posso descobrir como alterar o carimbo de data/hora de uma resposta? Há uma sugestão aqui, mas é complicada. Acredito que, se tiver acesso ao servidor, possa ser mais fácil (mas não quero quebrar nada).
1 curtida
Eu também gostaria de ver progresso nisso. Separei várias respostas que estavam um pouco fora do tópico, mas, por si só, elas precisavam de algum contexto. Então, tentei adicionar uma postagem citando o conteúdo relevante do tópico original, mas essa postagem acabou ficando no final das postagens que movi.
No final, eu a excluĂ porque nĂŁo fazia sentido estar fora de lugar.
1 curtida
Aqui está uma pequena ajuda sobre como alterar o carimbo de data/hora da sua postagem. O esforço manual necessário depende se se trata de um novo tópico (postagem original) ou de uma resposta.
Você também pode pesquisar aqui no Meta por change post time stamp e encontrará vários resultados para conferir. Talvez um deles tenha exatamente o que você procura.
1 curtida
Obrigado, @JimPas. A “solução alternativa” para reordenar as respostas me levou à minha solução final, muito simples. Criei uma nova postagem com minhas referências introdutórias ao original e, em seguida, movi as respostas da divisão original para o novo tópico. Depois disso, excluà a divisão original.
Precisei atualizar o link de referĂŞncia Ă divisĂŁo no tĂłpico original para apontar para o tĂłpico correto, já que havia excluĂdo o intermediário. De agora em diante, se eu quiser adicionar uma introdução novamente, devo criar esse tĂłpico primeiro e, em seguida, mover as respostas relevantes para ele. Isso deve evitar o problema de links desatualizados.
3 curtidas
Algum progresso nisso?
VocĂŞ deveria adicionar em Selecionar Posts.
1 curtida
Tentei esta solução alternativa, mas como faço para excluir a primeira referência introdutória sem excluir o tópico?
Muitas vezes, recebo usuários postando em tópicos existentes e preciso separá-los em seus próprios tópicos sem perder a ordem cronológica original, portanto, essa funcionalidade é importante. Espero que possa ser implementada.
1 curtida
Olá @ianm, não tenho certeza do que você está tentando alcançar. No meu caso, eu estava, na verdade, excluindo a postagem de contexto que adicionei no final depois de dividir o tópico, porque estava fora de ordem.
A postagem principal de um tĂłpico nĂŁo pode ser excluĂda (sem excluir o tĂłpico inteiro). No entanto, ao dividir o tĂłpico, vocĂŞ pode escolher entre enviar as postagens para um tĂłpico existente ou para um novo. Se vocĂŞ primeiro criar sua postagem introdutĂłria como o inĂcio do novo tĂłpico e, em seguida, dividir para o seu novo tĂłpico, vocĂŞ Ă© o proprietário da primeira postagem e pode fazer o que quiser com ela. Caso contrário, a primeira resposta em sua divisĂŁo se torna o inĂcio do tĂłpico.
Essa segunda abordagem foi a que acabei usando. Claro como lama?
1 curtida