Last modified: 2007-01-14 12:04:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10632, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8632 - Protection history bug
Protection history bug
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-14 11:51 UTC by Luna Santin
Modified: 2007-01-14 12:04 UTC (History)
0 users

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


Attachments

Description Luna Santin 2007-01-14 11:51:04 UTC
Not sure how to describe this. Sorry if I'm a bit roundabout.

I tried out the new cascading protection on en.wikipedia.org, and everything
seems to work well enough, except for one thing: usually, when I protect a page,
the edit shows as on-top, but when I use cascading protection, it doesn't.

In fact, an *older* edit still shows as on-top. Page history shows the correct
order, but when looking at a specific diff, the newest version (when
protecting/unprotecting) will still show a "next diff" link, which appears to
compare against the most recent non-protection edit.

Example from [[w:en:Special:Contributions/Luna Santin]]:
# 03:41, January 14, 2007 (hist) (diff) m User:Luna Santin/sandbox (Unprotected
User:Luna Santin/sandbox: Testing unprotection)
# 03:40, January 14, 2007 (hist) (diff) User:Luna Santin/sandbox (wonder what
happens to history if we edit while cascade-protected) (top) [rollback]
# 03:39, January 14, 2007 (hist) (diff) m User:Luna Santin/sandbox (Protected
User:Luna Santin/sandbox: Huh, is it borked? Edits not showing on-top
[edit=autoconfirmed:move=autoconfirmed]) 

Notice that the wrong edit is labelled on-top. The full page history still shows
the correct order, but when viewing diffs, this causes a few odd problems.
Comment 1 Brion Vibber 2007-01-14 11:55:14 UTC
Does not appear to be limited to the use of cascading protection; I see this
when making non-cascading protection.
Comment 2 Brion Vibber 2007-01-14 12:04:25 UTC
Fixed in r19228.

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


Navigation
Links