[MGNLRSSAGG-43] Content element not extracted from Atom feeds Created: 21/Jan/11  Updated: 07/Apr/11  Resolved: 05/Apr/11

Status: Closed
Project: Magnolia RSS Aggregator Module
Component/s: None
Affects Version/s: 1.1, 1.1.2
Fix Version/s: 1.1.3, 1.2.1

Type: Bug Priority: Neutral
Reporter: Antti Hietala Assignee: Felix Rabe
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File combined-feed-paragraph.png    
Issue Links:
Cloners
dependency
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

RSS Aggregator is not extracting post content from Atom feeds. It stores an empty value for description in JCR although the feed XML includes full post content. This issue appears to be limited to Atom feeds since content from RSS 2.0 feeds is extracted and stored correctly.

Examples:

In Atom feeds post content is in a <content> element whereas in RSS 2.0 feeds it is in <description> element (or a summary is in <description> and full post in <content:encoded> as in Gregory's/Wordpress case).

On the Magnolia corporate website we have a Combined Feed paragraph of staff blog posts (screenshot). The issue manifests itself by displaying only post titles regardless of whether the blogger chose to publish full content in their feed. Title alone does not tease the content very well.

Reproducible on corp website (rssaggregator 1.1.0) and demo (1.1.2).



 Comments   
Comment by Antti Hietala [ 25/Mar/11 ]

Dropping priority to Neutral. Adding ?alt=rss at the end of blogspot feed URLs pulls an RSS 2.0 feed instead of Atom. The aggregator can extract the content element correctly. This is a reasonable workaround.

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