# Riordina i post uniti
**URL:** https://meta.discourse.org/t/re-order-merged-posts/116268
**Category:** Support
**Created:** [29 Aprile 2019, 6:01pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268 "2019-04-29T18:01:54Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Loki](https://meta.discourse.org/u/Loki)
#### Post date: [29 Aprile 2019, 6:01pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/1 "2019-04-29T18:01:54Z")
We merged some threads and were hoping the order of the posts in the result would the order of post creation. But they are not. Is there any way to re-order them into creation order, or at least be sure they stay in creation order next time we merge?
Found this related topic, but it’s closed:
> [@How to fix an out of order mistake after moving two sets of posts to a new topic](https://meta.discourse.org/t/how-to-fix-an-out-of-order-mistake-after-moving-two-sets-of-posts-to-a-new-topic/41757):
>
> I have some editing rights (but I’m not in charge) on the Discourse Forum where I participate. I marked some posts to move…skipped a few…and marked others below that. All the ones I needed were marked. I moved the lot. Then, noticed the 1st marked post and its replies did not move. I went back and moved those over, expecting they would list themselves in date-time order. They did not. So how can I fix my mistake, so that Post 1 is back in 1st position? And, is is wrong to skip posts when…
---
### Author:  [@HAWK](https://meta.discourse.org/u/HAWK)
#### Post date: [29 Aprile 2019, 6:22pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/2 "2019-04-29T18:22:04Z")
AFAIK there is no way to change this behaviour, no. In good news, it’s likely that no one will notice.
---
### Author:  [@Loki](https://meta.discourse.org/u/Loki)
#### Post date: [29 Aprile 2019, 7:50pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/3 "2019-04-29T19:50:37Z")
Actually, we merged three fairly long moderator topics about one individual that was causing problems. It made it really hard to follow the flow of what had transpired and caused the boss to make a mistake in dealing with that individual. Oh well, won’t be doing that again.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [29 Aprile 2019, 8:29pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/4 "2019-04-29T20:29:45Z")
Posts get pulled in `post-id` order. Pulling in another order would be a performance issue, and would only be useful in the very rare edge case. . . that you managed to find.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [14 Agosto 2022, 2:35pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/5 "2022-08-14T14:35:54Z")
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [14 Agosto 2022, 5:03pm UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/6 "2022-08-14T17:03:34Z")
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [16 Agosto 2022, 4:21am UTC](https://meta.discourse.org/t/re-order-merged-posts/116268/7 "2022-08-16T04:21:12Z")
Esiste un rake task che potrebbe aiutare in queste situazioni:
`cd /var/discourse`
`./launcher enter app`
`rake posts:reorder_posts`
Questo task imposterà l’ordine di tutti i post sul tuo sito in base a quando sono stati creati.
E per indirizzarlo invece a un argomento specifico:
`rake "posts:reorder_posts[TOPIC_ID]"`