RSS polling plugin ignores items’ pubDate

I’m using the RSS polling plugin: Configure the Discourse RSS Polling Plugin

It seems to ignore the pubDate of each item.

This is linked with the following observations:

  1. It sucks up every item in the RSS feed and can’t be told only to get the latest x items.

  2. The Discourse post date is the date of import rather than the date of item.

  3. It doesn’t necessarily post them in the right order.

  4. If an old RSS item changes (the guid anyway) a new Discourse post will be created.

  5. If a post is deleted the plugin re-creates it as if it had never existed.

Admittedly most of these are only relevant when initially adding a feed.

1 Like

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.

1 Like

Thanks for replying.

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.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.