In a support discussion about the RSS polling plugin, Jonathan5 reports that the plugin ignores the pubDate of RSS items, leading to issues such as importing all feed items indiscriminately, setting Discourse post dates to import time rather than original publication time, posting items out of order, and recreating deleted or modified items. simon confirms that pubDate is ignored and explains that the plugin uses the item’s link URL to detect duplicates — meaning changes to an old item’s GUID or link may trigger a new post. Simon suggests unlisting instead of deleting topics to prevent recreation. Jonathan5 clarifies that he initially misunderstood the “Maximum number of posts to embed” setting, hoping it would limit items by pubDate, and notes that while the plugin has limitations, it functions adequately after initial setup, since future items’ pubDate and import date will typically align. The discussion highlights the plugin’s current design trade-offs and practical workarounds for managing feed imports.
You are correct that the pubDate is ignored. The topic’s timestamp will be set to when the topic was created on Discourse, not when the RSS post was initially published.
I’m not sure if there is any way this could be prevented. The feed item’s URL (the value of its link attribute) is used to determine if the topic already exists on Discourse.
The easiest work around for this is to unlist the topic instead of deleting it. That way it won’t be re-created.
The plugin could be told only to get the last n items from the feed based on pubDate, so if the link of an old item changes it would be ignored.
This is was I originally thought Maximum number of posts to embed was for (hence some of my initial confusion).
This is what I did in the end.
Putting it all in perspective, I can see that the RSS plugin works all right, and after the initial few items the pubDate and topic creation date will be the same, and usually it won’t be a problem to create a new topic for every item in the feed.