Bug 793508 (JBEPP-589) - RSS gadget displays wrong publish date
Summary: RSS gadget displays wrong publish date
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-589
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.0.ER03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER04
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-29 09:08 UTC by Michal Vanco
Modified: 2013-04-30 23:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-02 13:08:44 UTC
Type: Bug

Attachments (Terms of Use)
rss_wrong_time.png (75.29 KB, image/png)
2010-10-29 09:08 UTC, Michal Vanco 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-589 0 None None None Never

Description Michal Vanco 2010-10-29 09:08:37 UTC 
project_key: JBEPP

RSS Gadget displays time of publish "less than a minute ago" for all feeds.
I verifed with gatein + cnn rss (see screenshot).

This was already happening - JBEPP-340 (491 months ago)
Comment 1 Michal Vanco 2010-10-29 09:08:58 UTC 
Attachment: Added: rss_wrong_time.png
Comment 2 Thomas Heute 2010-11-02 11:05:25 UTC 
Link: Added: This issue is related to GTNPORTAL-1619
Comment 3 Thomas Heute 2010-11-02 13:07:10 UTC 
Link: Added: This issue is related to GTNPORTAL-1621
Comment 4 Scott Mumford 2010-11-08 04:16:04 UTC 
Release Notes Docs Status: Removed: Not Required Added: Documented as Resolved Issue
Release Notes Text: Added: The RSS reader gadget was displaying incorrect publication dates for items fetched from feed sources.
Each item was being displayed with a publish date of 'less than a minute ago', regardless of when it was published by the feed.
The RSS aggregator has been patched to fetch and display the correct publication date.
Note You need to log in before you can comment on or make changes to this bug.