Yes, this is a fantastic idea! Whoever created the package manager and ACP page should totally do this 😄
... what? What do you mean it's me? 😦
Edit: Please add your suggestions here 👍
@phenomlab Are you using an old version of the plugin? This should be fixed in https://github.com/barisusakli/nodebb-plugin-rss/commit/950dbf392290b38c4b29f458c49fe97caae4949c.
Plugin no longer uses the yahoo api.
@baris Yes, because I need the body populated with the text from the link. If I use the 2.x version, this gets removed.
Will there be any further updates to the 1.x train ? I have an alternative lined up to meet my needs, but it's a script and not a plugin.
I am looking at 1.x and I don't see it using the yahoo api either https://github.com/barisusakli/nodebb-plugin-rss/blob/1.x/feed.js. What version are you using?
@baris I think I might know what caused this. I ran an
npm audit fix --force which may have downgraded as I was previously on
1.3.2. Just updated to that, and am testing now.
EDIT - suspicion confirmed - works fine now Sorry for the fire drill.
I set it up with a podcast RSS, but instead of posting the description of an item, it posts a link instead in the topic. Is there anyway to change this?
Edit: Nevermind solved it, installed version 1.3.0
Why do need to spoil the plugin? Why doesn't it extract the contents of the channel now? What should I do about it? What is the point of using a non-working plugin?
Even discourse didn't think of such a thing
@antosik The actual RSS feed content is no longer included in the post body since 1.3.3 onwards. I believe this route was taken to prevent database bloat from what would land up being hundreds of records from external RSS feeds.
@phenomlab Any new post and comment is a bloat of the database. This is the meaning of the forum, more useful content. 30 years ago, this was relevant, but not now. But if someone wants to save on disk space, it is better to use postgres
@volanar then if you need that functionality your should use version 1.3.2
@phenomlab 1. This version is outdated and not supported.
2. The question was, why spoil the plugin, if you can make an additional setting to disable or enable content extraction.
If this is a key function for any community, then developers will have to independently support the fork of the plugin or switch to a more loyal discourse
@volanar I understand. I took the other route and used a custom script I wrote that does this independently of NodeBB but uses the API to create the posts.
@phenomlab I have a wordpress site that is closed from search bots, which automatically extracts content from some sites and translates the content. I wanted to use this plugin to fill the forum with news from my site, but I see that this will not work. Now I'm also thinking of using a third-party script or switching to discourse before it's too late