[MGNLRSSAGG-38] Update demo RSS Agg example Created: 26/Oct/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia RSS Aggregator Module
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: 2.2.x

Type: Improvement Priority: Minor
Reporter: Antti Hietala Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

demo project


Attachments: PNG File Importer job.png     PNG File Reuters channel.png    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Please fix the following issues in the news RSS Aggregator example in demo project:

  1. If you run the import manually you don't get any new content entries for the BBC and Wired channels. Are the feed URLs correct?
    BCC feeds http://news.bbc.co.uk/2/hi/help/rss/default.stm
    Wired feeds http://www.wired.com/about/rss_feeds/
  2. The news aggregator example uses filters. Make sure that the filters work in a meaningful way after you change the feed URLs. This an example for new users.
  3. The bootstrapped feed examples are very old. ("McCain takes lead over Obama" Really?) Run the feed import and store fresh content entries in bootstrap data so that when the demo instance is refreshed hourly it has more recent data.
  4. Enable the automated feed importer job in /modules/data/config/importers/rssAggregator and set the CRON job to fire every 5 minutes (0 0/5 * * * ?).
  5. Delete the Reuters channel. There is no corresponding Reuters feed URL so the bootstrapped content entries confuse new users. "Where are these coming from?"


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:04:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.