# Hoe antwoorden op onderwerpen standaard chronologisch te sorteren
**URL:** https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193
**Category:** Support
**Created:** [27 maart 2024 om 18:03 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193 "2024-03-27T18:03:14Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@SethWilliams](https://meta.discourse.org/u/SethWilliams)
#### Post date: [27 maart 2024 om 18:03 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193/1 "2024-03-27T18:03:14Z")
I recently migrated our forum from NodeBB to Discourse. It’s all going great so far, but I’m finding that all of the replies within each topic are automatically sorted in reverse chronological order (the latest reply is at the top, the oldest reply is at the bottom), which seems backward.
I’ve spent about 30 minutes trying to figure out how to show all topic replies in chronological order by default (oldest reply at the top, latest reply at the bottom), but I cannot find where to adjust this in the admin settings.
What am I missing? Where can I adjust how these replies are sorted?
---
### Author:  [@Firepup650](https://meta.discourse.org/u/Firepup650)
#### Post date: [27 maart 2024 om 18:11 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193/2 "2024-03-27T18:11:35Z")
That’s strange, according to multiple topics here, that’s not even possible:
> [@Can discourse display topic replies in reverse order?](https://meta.discourse.org/t/can-discourse-display-topic-replies-in-reverse-order/13563):
>
> Tried searching but couldn’t find anything. Can the order be changed to newest first within a topic? Some forums have huge topics with hundreds of pages of answers and are IMO better read with newest-first order, where you don’t really care about the old ones.
> [@Can discourse display topic replies in reverse order?](https://meta.discourse.org/t/can-discourse-display-topic-replies-in-reverse-order/13563/14):
>
> This is still not possible, and also not something we’re currently looking to implement.
Are all new topics and posts doing this, or only ones from the import?
---
### Author:  [@SethWilliams](https://meta.discourse.org/u/SethWilliams)
#### Post date: [27 maart 2024 om 18:13 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193/3 "2024-03-27T18:13:54Z")
Good question.
Only the imported topics (which number in the thousands) have their replies sorted in reverse chronological order like this.
The few new ones created after the migration are being sorted chronologically, as they should be.
Is there any way to retroactively sort these imported topic replies chronologically?
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [27 maart 2024 om 18:53 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193/4 "2024-03-27T18:53:13Z")
> [@SethWilliams](#):
>
> Is there any way to retroactively sort these imported topic replies chronologically?
I think there’s a rake task that might be of use:
```plaintext
rake posts:reorder_posts
```
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [27 maart 2024 om 21:03 UTC](https://meta.discourse.org/t/how-to-order-topic-replies-in-chronological-order-by-default/301193/5 "2024-03-27T21:03:21Z")
> [@SethWilliams](#):
>
> Where can I adjust how these replies are sorted?
They are displayed in the `topic_id` order. The problem, I’m guessing, is that somehow the nodeBB importer is getting the data in reverse cron and is therefore creating the posts in reverse order.
You need to see that the import script sorts the posts in chronological order when it does the import. (You’ll also need to wipe the whole database and do the import again).
> [@JammyDodger](#):
>
> I think there’s a rake task that might be of use:
Good one! Looks like that should work, though if it’s not too late, I’d recommend fixing the import script and starting anew.