Bug 156370 - invalid date shown and uncorrect sorting
Summary: invalid date shown and uncorrect sorting
Status: RESOLVED DUPLICATE of bug 166495
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-22 12:14 UTC by Dario Panico
Modified: 2008-07-15 22:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot (189.00 KB, image/png)
2008-01-22 12:17 UTC, Dario Panico
Details
Screenshot (251.75 KB, image/png)
2008-06-24 22:40 UTC, Dario Panico
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dario Panico 2008-01-22 12:14:46 UTC
Version:           1.2.50 (using 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22-14-generic

I started to build kdepim three months ago and in my kde-look.org feed I have several feeds dated 02/07/06. (e.g. KDE Four Live, submitted 04-28-07) The date is obviously incorrect but the worse thing is that those entries (several and not only in the kde-look feed) are shown at the top of the list when post are sorted by date with most recent on the top.
Comment 1 Dario Panico 2008-01-22 12:17:37 UTC
Created attachment 23195 [details]
Screenshot

My l10n is italian so dates are shown as dd-mm-yy when english dates are shown
mm-dd-yy
Comment 2 Dario Panico 2008-06-24 22:40:24 UTC
Created attachment 25572 [details]
Screenshot

If my calendar is right we are still in the XXI century, not the XXII!!
It probably means that the problem is still here, try to look at the
screenshot. Maybe you can reproduce it by subscribing to that feed (the link is
clearly shown)
Comment 3 A. Spehr 2008-07-15 22:36:58 UTC
Thanks for the report! I'm dupping this against a newer one, because it looks like that one has the start of a patch. So hopefully this gets fixed soon.

*** This bug has been marked as a duplicate of 166495 ***