The discussion revolves around issues with embedding RSS feeds into Discourse. laurakalbag initially reports three issues: attributing posts to the correct author, setting the timestamp to the original post’s publishing time, and maintaining chronological order. eviltrout responds that the embedding tool was meant for “going forward” and doesn’t support dates via embedding, but it’s something that can be added.
Later, enoch85 and geoff777 report issues with RSS feeds being posted to the “Uncategorized” category, despite setting the correct category. simon explains that the category is based on the domain of the feed’s link attributes, not the domain of the feed itself. He provides guidance on how to set the correct category and updates the plugin’s text to make it clearer.
geoff777 asks if the fix is for feeds not stopping or for feeds going into the “Uncategorized” category. simon clarifies that he fixed the issue with feeds not stopping when the plugin is disabled.
geoff777 expresses confusion about the plugin’s configuration and suggests that it should be able to automatically slice and dice the URL into Allowed Hosts and Path Whitelist without requiring manual input. simon agrees that configuring the plugin can be difficult and provides an example of how to set it up correctly.
efeefe revisits the topic and reports that the plugin is not likely to work for their needs due to the link attribute in each entry pointing to a different domain. However, they later find a solution by generating a different feed from the source.
efeefe reports another issue where the plugin is not fetching the contents of each item, and the body of the topic says “this is a discussion related to this original message” with a button to “show full message” that stays “loading” indefinitely. simon suggests that the problem is due to Discourse not finding the content on the page and provides guidance on configuring the embed whitelist selector site setting.
efeefe reports that the suggested solution did not work, and simon provides additional suggestions for whitelisting and clearing the cache.
I’m having a few issues with embedding from RSS. I’m going to enable comments for each original post, but I want to ensure that the comments end up in the right location in Discourse with the correct attributed author and publishing date.
Issue 1: embed username key from feed
I need each topic to be correctly attributed to the right author. I’m set up as the default. My RSS has a format of <discourseUsername>jo</discourseUsername>, so I entered discourseUsername as the value for embed username key from feed. It just attributes all topics to the default user. Have I done something wrong here?
Issue 2: pubdates
I need each topic’s timestamp to be the same as the original post publishing time. Otherwise adding our RSS feed of ~70 posts floods the forum with outdated topics that have recent timestamps. (Pushing newer manually-created topics down.) Is there a way to set the timestamp for topics pulled from RSS to the same time as the RSS <pubdate>?
Issue 3: chronology
Maybe related to Issue 3, the topics imported via RSS are not in the same chronological order as the original posts.
I hope none of these are stupid questions! Any help, suggestions, or workarounds would be much appreciated!
Thanks! It’d also be pretty cool if you could feed different (multiple) RSS feeds into different categories, or put RSS-fed topics into different categories dependent on a key value.
Our use case is that we have a couple of blogs, one “newsy” and one “developer-y”, I’m using a combined RSS feed for now so that we can pull them all into Discourse, but having their separate posts/topics in their own categories would make it easier for audiences who favour one blog or the other.
That looks correct to me. Can you give me a sample of the RSS feed you’re trying to import?
Another option is to use the embed by username site setting if you are okay with all posts coming from the same user.
This is unfortunately not possible right now. The embedding tool was originally meant to be “going forward” so it doesn’t have support for dates via embedding. It’s something we could definitely look at adding. (This is the same as issue 3 as far as I can tell).
<item> <title>The Social Web: A Glorious Dystopia</title> <link>https://ind.ie/blog/the-social-web-a-glorious-dystopia/</link> <guid>https://ind.ie/blog/the-social-web-a-glorious-dystopia/</guid> <description><p>This week we're going to dive straight into the activities of those cheeky corporations. There's so much to share!</p> <p><a href="https://ind.ie/blog/the-social-web-a-glorious-dystopia/">Read the full post on the Ind.ie blog</a>.</p></description> <pubDate>Fri, 24 Jul 2015 18:30:00 GMT</pubDate> <author>laura@ind.ie (Laura Kalbag)</author> <discourseUsername>laura</discourseUsername> </item>
I’ve got the embed by username set to my username, but also got embed username key from feed. Will these conflict? I’d rather have them all assigned to the original author, not just me. Though I write the most blog posts, so having it set to me isn’t a bad default…
That makes sense. We’re going to use it “going forward” now too
It’s not exactly the same as issue 3 (but would have the same solution.) Even though the RSS is imported all at once, the topics are still ordered (because that’s how they’re presented in Discourse.) However it’s unclear what the topics are ordered by, as it’s not the same order as the <item>s in the RSS.
늦게 답변드려서 죄송합니다. RSS 피드 항목이 게시될 카테고리는 피드 항목의 link 속성에 사용되는 도메인에 따라 결정됩니다. RSS 피드 자체의 도메인에는 기반하지 않습니다. 예를 들어, RSS 피드가 www.example.com에 있지만 RSS 피드의 link 속성이 blog.example.com을 가리키고 있다면, blog.example.com에 대한 호스트 항목을 추가하여 피드의 카테고리를 설정해야 합니다.
위 방법으로 해결할 수 없는 RSS 카테고리 관련 문제를 겪고 계신 경우 알려주시면 원인을 조사하겠습니다.
피드의 게시물에 카테고리를 설정하는 방법을 명확히 설명하도록 플러그인에서 사용되는 문구를 업데이트하겠습니다.
이것은 수정이 필요합니다. 플러그인이 비활성화되어 있을 때 RSS 피드로부터 주제를 계속 생성해서는 안 됩니다. 당분간은 플러그인의 도메인에 대해 설정한 호스트 항목을 삭제하면 주제가 생성되지 않도록 할 수 있습니다.
RSS 피드를 확인해 보니, 피드 항목의 link 속성에 www.svedala.se 도메인이 사용되고 있습니다. 스크린샷의 호스트 레코드는 svedala.se 도메인에 대한 것입니다. www.svedala.se에 대한 호스트 레코드를 추가하고 그 범주를 RSS로 설정해 보세요. 이 변경 사항을 적용한 후에도 여전히 올바른 범주로 게시되지 않는다면 알려주시겠습니까?
확인해야 할 한 가지 사항은 RSS 피드 도메인에 대한 호스트 레코드를 생성해야 하는지, 아니면 피드의 link 속성에 사용되는 도메인에 대해서만 호스트 레코드를 추가하면 되는지입니다. 제 사이트에서 직접 테스트해 보고 여기서 결과를 공유하겠습니다.
허용된 호스트(Allowed Hosts) 섹션에 설정한 도메인은 올바르게 보입니다. 다만, 현재 설정된 경로 화이트리스트(Path Whitelist) 설정은 잘못된 것으로 보입니다. 이 설정의 목적은 웹사이트에서 서로 다른 경로에 있는 게시물을 특정 Discourse 카테고리에 게시할 수 있도록 하는 것입니다. www.svedala.se의 모든 게시물을 RSS 카테고리에 게시하려면 이 설정을 비워 두시면 됩니다.
도메인에서 서로 다른 경로가 서로 다른 Discourse 카테고리로 게시되도록 하려면, 추가하는 경로는 와일드카드 기호로 끝나야 합니다. 예를 들어, /paverka/nyheter/.*와 같이 설정할 수 있습니다.
플러그인이 비활성화될 때 피드가 멈추지 않는 문제를 수정했습니다. 또한 피드 URL을 설정할 때 플러그인이 표시하는 텍스트를 업데이트하여, 피드의 주제가 속할 카테고리를 어떻게 설정하는지 명확히 했습니다. 피드가 게시되는 카테고리는 피드의 link 속성 도메인에 기반합니다. 이는 변경할 수 없는 부분입니다.
