The discussion revolves around creating an RSS feed for unanswered topics with a specific tag. tpetrov initially tries to create a feed with https://meta.discourse.org/tag/unsupported-install.rss?max_posts=1, but it doesn’t work as expected.
sam suggests using a custom filter called “solved” and provides examples of how to use it. However, tpetrov points out that this filter cannot be used in an RSS feed.
sam offers an alternative solution by injecting tags into the latest feed using a trick. tpetrov tries this approach, but the RSS version doesn’t respect the tags filter.
blake reveals that the issue is due to the .rss routes not calling the same backend code as the .json routes. blake has created a PR to address this issue, which will allow the /latest.rss route to take into account query parameters.
I’d like to get an rss feed only for the unanswered topics with a tag e.g. https://meta.discourse.org/tag/unsupported-install?max_posts=1
Is that possible?
Tried https://meta.discourse.org/tag/unsupported-install.rss?max_posts=1 but the unanswered filter wasn’t added.
Yeah we have a custom filter for this called “solved”
try
https://meta.discourse.org/c/support/?solved=yes
and
https://meta.discourse.org/c/support/?solved=no
Thanks Sam and Happy Birthday!
Ok, but can I use that filter (or the max_posts) in an rss feed - that doesn’t seem possible?
PS. I should’ve posted the links as code (updated them now).
I think the tag filters are a bit limiting, instead you inject tags into latest using this trick.
https://meta.discourse.org/latest.rss?max_posts=1&tags=unsupported-install
Thanks Sam,
I wouldn’t come to that.
I’m afraid it show the right items in the feed though.
This one is fine https://meta.discourse.org/latest?max_posts=1&tags=unsupported-install - it shows the right topics:
https://meta.discourse.org/latest.rss?max_posts=1&tags=unsupported-installseems to not respect tags=unsupported-install - it shows all from latest.
I have a PR created to address this issue:
https://github.com/discourse/discourse/pull/10350
While looking into this I discovered that the .rss routes don’t actually call the same backend code as the .json routes do so this is why the behavior is a bit different and was ignoring the query parameters. I’m not actually sure they the .rss routes are different, but my change makes sure that the /latest.rss route will take into account any query parameters. If there are any other .rss routes you are hitting we may need to update those as well.
Great, thanks a lot @blake