Hello We are using Discourse to power our Wiki. It’s been working pretty well. Since updating to 1.7 we’ve run in to a slight snag. It seems that the ordering of the links to other Wiki pages is not necessarily respected. If you see our Table of Contents for the Wiki here, you will see that Apple TV is the second to last link, and we would like it to be the second to last category to appear. Our script scrapes the links array. I have noticed that the JSON of the post lists Apple TV first. At first I thought Discourse may be ordering links by post ID, but this does not seem to be the case. I tried editing the post and removing all links, and then re-adding them, but this did not change the situation. Is there an explanation for how the links array is ordered? Would it make sense for the links to be listed in the JSON in the order that they are referenced? "links":[ { "url":"https://discourse.osmc.tv/t/apple-tv/10039", "title":"Apple TV", "fancy_title":null, "internal":true, "attachment":false, "reflection":false, "clicks":0, "user_id":1, "domain":"discourse.osmc.tv" }, ] Thanks Sam

app/models/topic_link.rb main ftl.internal, ftl.domain, MIN(ftl.user_id) AS user_id, SUM(clicks) AS clicks FROM topic_links AS ftl JOIN posts AS source_posts ON ftl.post_id = source_posts.id LEFT JOIN topics AS ft ON ftl.link_topic_id = ft.id LEFT JOIN categories AS c ON c.id = ft.category_id LEFT JOIN posts AS target_posts ON ftl.link_post_id = target_posts.id /*where*/ GROUP BY ftl.url, ft.title, ftl.title, ftl.link_topic_id, ftl.reflection, ftl.internal, ftl.domain ORDER BY clicks DESC, count(*) DESC LIMIT 51 SQL builder.where("ftl.topic_id = :topic_id", topic_id: topic_id) apply_source_post_visibility_filters(builder, guardian, source_post: "source_posts") apply_link_visibility_filters( builder, link: "ftl", target_topic: "ft", [immagine] eviltrout: I believe those links are ordered in terms of popularity. The most clicked on links will be at the top. Yes.

Thanks for the information. I’ll have to find an appropriate workaround. Sam

You have link_counts, so you could add correct ordering there, but preserve links as is in a future version of Discourse, or maybe add a ‘links_raw’. If you would accept a new JSON property that offers links in the correct order then I can PR this. I will have to work around this temporarily by taking cooked and taking links from that or patching Discourse. Sam

JSON link array does not match link order in post

Product Support

eviltrout (Robin Ward) 10 Febbraio 2017, 3:35pm 2

I believe those links are ordered in terms of popularity. The most clicked on links will be at the top.

Argomento		Risposte	Visualizzazioni
JSON API, get topics sorted by created_at Development	5	3178	Ottobre 17, 2016
API topic post creation ordered by updated_at or created_at? Product Support	7	1370	Aprile 12, 2018
Can discourse display topic replies in reverse order? Feature	16	6601	Dicembre 9, 2024
Replies in thread showing out of order Product Support	13	2619	Dicembre 2, 2020
Backlinks make certain posts more popular than they should be! Product Support	7	334	Settembre 25, 2025

JSON link array does not match link order in post

Argomenti correlati