Last modified: 2013-06-18 16:42:21 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 T17604, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15604 - Protection logs and expiry date oddity
Protection logs and expiry date oddity
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-14 18:09 UTC by Karla Harman
Modified: 2013-06-18 16:42 UTC (History)
2 users (show)

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


Attachments

Description Karla Harman 2008-09-14 18:09:12 UTC
I have just been testing out MediaWiki on localhost before using it for my website, the install went well.

However, the protection logs seem a bit out of place, with the expiry time before the reason field, as with this example:

    * 17:57, 14 September 2008 WikiSysop (Talk | contribs | block) protected "Test page" ([create=sysop] (indefinite)) ‎ (Preventing re-creation of testing content) (hist) (change)
    * 17:38, 14 September 2008 WikiSysop (Talk | contribs | block) protected "Main Page" ([edit=sysop] (indefinite) [move=sysop] (indefinite) ) ‎ (High traffic page: high-visibility) (hist) (change)

Surely it should be:
    * 17:57, 14 September 2008 WikiSysop (Talk | contribs | block) protected "Test page" (Preventing re-creation of testing content [create=sysop]) (hist) (change)
    * 17:38, 14 September 2008 WikiSysop (Talk | contribs | block) protected "Main Page" (High-traffic page:High visibility [edit=sysop:move=sysop]) (hist) (change)

Thank you for adding a new reason field, as with blocking and deletion. I think that if protection is indefinite it doesn't need to be mentioned, but that the edit expiry should be like this:
[edit=sysop expiry date (UTC):move=sysop] if expiry is just set for edit=autoconfirmed/sysop restriction or [edit=sysop:move=sysop expiry date(UTC)] as it was before for both edit/move protection.
Comment 1 Karla Harman 2008-09-14 18:09:34 UTC
I should add this only applies to the latest trunk build from SVN, which I am using at the moment.
Comment 2 Alex Z. 2008-09-14 18:19:03 UTC
The expiry time was moved before the reason in r40713, so that the details wouldn't get cut off if a long reason was used.

I added the (indefinite) in r40770, so as to avoid confusion. Prior to 40770 each protection type (edit/move) used the same expiry time, so you would have something like "[edit=sysop:move=sysop] (expires 15:02, 18 September 2008 (UTC)" for protection that expired on 18 September, and "[edit=sysop:move=sysop]" for indefinite protection. However, with 2 separate expiry times, "[edit=sysop] [move=sysop] (expires 15:02, 18 September 2008 (UTC)" is vague, it would mean that [edit=sysop] is indefinite, but it looks like they both expire on 18 September due to the similarity to the old log type.
Comment 3 Karla Harman 2008-09-14 18:20:41 UTC
The reason field should be before the edit/move/create=sysop bit, though.
Comment 4 Karla Harman 2008-09-14 18:24:00 UTC
Sorry... still getting used to it, probably because I was so used to seeing edit=sysop move=sysop or edit=autoconfirmed move=autoconfirmed a lot.

I'm surprised that test.wikipedia didn't update to it there.
Comment 5 Karla Harman 2008-09-14 18:25:48 UTC
Sorry... still getting used to it, probably because I was so used to seeing edit=sysop move=sysop or edit=autoconfirmed move=autoconfirmed a lot.

I'm surprised that test.wikipedia didn't update to it there.

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


Navigation
Links