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.
プラグインが無効化されたときにフィードが停止しないという問題を修正しました。また、フィード URL を設定する際に表示されるテキストを更新し、フィードのトピックのカテゴリを設定する方法が明確になるようにしました。フィードが公開されるカテゴリは、フィードの link 属性のドメインに基づいて決定されます。これは変更できません。
