Last modified: 2011-03-13 18:04:58 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 10169 - Allow "page swap" to move a page to an existing name
Allow "page swap" to move a page to an existing name
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-06 14:51 UTC by (none)
Modified: 2011-03-13 18:04 UTC (History)
2 users (show)

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


Attachments

Description (none) 2007-06-06 14:51:45 UTC
Occasionally, there is a problem of a vandal who will move a page, then edit the resulting redirect to prevent most users from reverting the move. I suggest that a page should be movable anyway, if:
1) The destination page was originally a redirect.
2) The destination page is currently a redirect.
3) The origin page had, at some point, been moved from the destination name. If there had been several moves, this should apply to each name the page had ever had.
In this case, the redirect page with the destination name should be moved to the origin name. A new version of the page, which is a redirect to the destination name, should show up with the edit summary of "Page swap" or something like that.
Comment 1 Rob Church 2007-06-07 13:52:55 UTC
Sysops can already do this.
Comment 2 (none) 2007-06-11 10:58:20 UTC
But non-sysops can't. My recommended change allows such revert moves to be done by any user. In addition, it keeps the history of the other page, so it's not like deletion.
Comment 3 Rob Church 2007-06-18 06:59:02 UTC
The current behaviour allows for a page to be moved over another page *if* the destination is a redirect to the page being moved, which allows for a standard move reversion.

Where the destination is not a simple redirect, then a determination needs to be made with regards to whether or not the destination page is worth preserving, in which case it is moved out of the way, or whether it can be deleted. This decision is left to a user with permission to delete pages, i.e. a sysop.

I see no good reason to change the existing behaviour and complicate matters.
Comment 4 (none) 2007-06-19 11:32:48 UTC
With my requested improvement, the history will be preserved. This can also help allow for quick correction of a page move vandal, such as what User:Sev Snape did - one of the moved pages was deleted accidently.
Comment 5 Rob Church 2007-06-19 14:09:38 UTC
(In reply to comment #4)
> With my requested improvement, the history will be preserved.

Not so far as I can see:

"In this case, the redirect page with the destination name should be moved to the origin[sic] name. A new version of the page, which is a redirect to the destination name, should show up with the edit summary of "Page swap" or something like that."

How does this preserve any additional history?
Comment 6 (none) 2007-06-20 06:12:15 UTC
By moving the history from destination name to target name. 
Comment 7 Rob Church 2007-06-20 06:19:49 UTC
(In reply to comment #6)
> By moving the history from destination name to target name. 

That doesn't make any sense whatsoever; "destination" and "target" are the same thing.

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


Navigation
Links