A move is a significant modification to a page and it should be possible to mark it patrolled. Recent changes displays the move log entry, and log entries in RecentChanges are always patrolled when saved, so we could make an exception for moves (when the user is not autopatrolled) and display a red mark. The RC entry could be patrolled from the footer of the moved page or the null diff for the move. This might be useful for T14363.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Implement Special:Newmoves and allow patrol of moves | mediawiki/core | master | +650 -34 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | GTrang | T72518 Tags for page moves should apply to auto-generated edits | |||
| Open | None | T70950 rc_this_oldid (resp. log_params) should contain revision ID of null revision (resp. redirect) created by moves | |||
| Resolved | Cenarium | T127852 Publish of recent change for a log entry should be deferred | |||
| Resolved | Cenarium | T127848 Should be possible to associate a revision to a log entry without making it unpatrolled | |||
| Open | None | T70936 rc_this_oldid should contain the revision IDs of null revisions created by log events | |||
| Stalled | None | T159028 Unpatrol moved pages on English Wikipedia | |||
| Open | None | T98617 Make page moves patrollable | |||
| Resolved | Cenarium | T122089 Log entries and associated page revisions are not actually associated in the database |
Event Timeline
Comment Actions
Change 211656 had a related patch set uploaded (by Cenarium):
Allow patrol of page moves and uploads
Comment Actions
This can be done without much difficulty for any logged action with an associated revision, since we can reuse the patrolling interface that exists in diffs/article footers. It also solves the log problem mentioned by Bawolff in T11501. So this can be done for moves, uploads and protections (maybe a few others ?), but for protections I don't see much use in that. Patrolling of arbitrary log entries would be much more complex and likely require rewriting all the patrol logic, for what I see as too little gain. What other logged entries would it be useful to patrol besides moves and uploads?
Comment Actions
Hi all. I recently proposed on enwiki "that any time an article is moved it should lose its patrolled status, so that it is flagged for new page patrol (again, if necessary), other than page moves by editors with the page mover or autopatrolled rights, or perhaps all extendedconfirmed users." The proposal discussion has closed with consensus to implement the change. I was adivsed to leave a link to the discussion here, so please see the discussion. I'm not familiar with Phabricator so if I need to do something else here please leave me a note on my enwiki talk page. Cheers.
Comment Actions
Change 251794 says:
This implements Special:Newmoves, that lists recent moves (only the latest if a page was moved several times).
This is problematic if the list is meant to protect against this existing-page hijacking. Moving a page to a totally different name and then quickly moving it to another similar name would result in only the "reasonable" move being shown in the list.
To avoid this, I think the list should show all moves, with some kind of indication that a move has been superseded.
Comment Actions
Removing task assignee due to inactivity, as this open task has been assigned to the same person for more than two years (see the emails sent to the task assignee on Oct27 and Nov23). Please assign this task to yourself again if you still realistically [plan to] work on this task - it would be welcome.
(See https://www.mediawiki.org/wiki/Bug_management/Assignee_cleanup for tips how to best manage your individual work in Phabricator.)