Last modified: 2006-04-25 19:50:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5291 - "older edit" on oldest edit is linked and produces nonsense
"older edit" on oldest edit is linked and produces nonsense
Status: RESOLVED DUPLICATE of bug 2930
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-03-19 07:18 UTC by Greg Price
Modified: 2006-04-25 19:50 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Greg Price 2006-03-19 07:18:29 UTC
The oldest edit on [[Copula]] is
between a May 2001 and a June 2001 revision.
The diff page nevertheless has the "Older edit" link.
Probably it shouldn't -- unless that links to a diff page for the article's

Following this link that shouldn't be there, one arrives at
wherein the *older* revision is a September 2002 revision
and the *newer* one is that same oldest May 2001 revision.
That definitely shouldn't be.

Bug #5242 appears to be a different sort of misbehavior
happening in a similar situation.
Comment 1 lɛʁi לערי ריינהארט 2006-04-25 19:50:38 UTC
Please see bug 2930 and its duplicates
Bug 2930: The edit history is wrong: It is based on timestamps while diff and
direction is based on revision id's

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

Note You need to log in before you can comment on or make changes to this bug.