Last modified: 2014-03-06 03:58:47 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 3185 - Page move rollback should not leave a redirect
Page move rollback should not leave a redirect
Status: NEW
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Low enhancement with 8 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 13602
  Show dependency treegraph
 
Reported: 2005-08-18 13:37 UTC by Chris M
Modified: 2014-03-06 03:58 UTC (History)
7 users (show)

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


Attachments

Description Chris M 2005-08-18 13:37:48 UTC
When using the page move rollback tool to counter page move vandalism, a
redirect is left at the vandal title that still needs to be deleted by hand. See
for example the deletion log for today (18 August) to see how much work this can
be for admins.
Comment 1 p_simoons 2005-08-30 17:35:29 UTC
Agreed. Currently, you require four clicks (one to rollback, one to confirm
destroying the redirect over which you're rollbacking, one to delete the
redirect you're creating by rollbacking, and one to confirm that).
Comment 2 Duncan Harris 2006-10-15 12:41:27 UTC
If implemented, this needs to be an option as you may want to revert a move and
leave a redirect.
Comment 3 Rotem Liss 2006-10-15 12:55:40 UTC
(In reply to comment #2)
> If implemented, this needs to be an option as you may want to revert a move and
> leave a redirect.

Only for sysops, of course.
Comment 4 Chris McKenna 2006-12-22 00:59:36 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > If implemented, this needs to be an option as you may want to revert a move and
> > leave a redirect.

The way to do this is probably to have a check box labeled "Create redirect from
<current title> to <previous title>", which defaults to unchecked (i.e. no
redirect).
If the page was moved over a redirect (e.g. if [[George W. Bush]] was moved to
[[Dubya]]), the box should default to checked (i.e. the pre-existing redirect is
retained).

I've got no idea how difficult this would be to program though?

> Only for sysops, of course.
Only sysops currently have the page move rollback, so this isn't an issue now.
If at some point in the future non-sysops are given access to the tool, then 
they should be able to choose whether a redirect is created or not. If they do
not have the privs to delete pages then they should have no option but to leave
a pre-existing redirect in place (either the checkbox does not appear, or it
appears checked and greyed out). 
It is possible that a bad redirect is left in this situation if the following
happens:
1. [[George W. Bush]] is moved to [[George W. Bush is a plonker]]
2. The article is moved back, but a redirect is left (e.g. it was moved without
using the rollback tool, or the box was accidentally checked)
3. The article is moved to the vandal title again, over the redirect.
4. A non-sysop user rolls back the move but is unable to remove the redirect.
The risk of this happening is slight however, and in any case can be cleaned up
using normal processes (e.g. on the English Wikipedia it would be marked for
speedy deletion under criteria G3).
Comment 5 BD2412 2008-10-26 09:50:18 UTC
Not so easily cleaned up when a serious pagemove vandal moves 30-40 pages before getting nabbed. Maybe not a problem for 'pedia, but it just happened a few minutes ago on en:Wikiquote.
Comment 6 Mike.lifeguard 2008-11-25 03:50:37 UTC
The option to not create a redirect when moving a page has been added to the UI, though not permitted to any users by default. That should of course be changed - rollbackers and sysops should have access to it. Global rollbackers and Stewards have access to this, and it works /very/ nicely.
Comment 7 Mike.lifeguard 2009-03-18 20:03:45 UTC
(In reply to comment #6)
> The option to not create a redirect when moving a page has been added to the
> UI, though not permitted to any users by default. That should of course be
> changed - rollbackers and sysops should have access to it. Global rollbackers
> and Stewards have access to this, and it works /very/ nicely.
> 

That's been done, but it's still not *rollback* of a page move, which is key.
Comment 8 Chris McKenna 2011-04-17 15:31:12 UTC
I think that if this bug were fixed then it would also solve bug 13602 
I would mark them as interlinked in this way but I don't know how to do that!
Comment 9 MZMcBride 2012-11-17 23:00:54 UTC
I'm going to go ahead and mark this as easy.
Comment 10 Shikha Shree 2014-02-15 20:08:16 UTC
 I am new to FOSS and mediawiki
how do I start on this bug
how do I replicate the error on my local machine
Comment 11 PiRSquared17 2014-02-15 20:25:01 UTC
(In reply to Shikha Shree from comment #10)
>  I am new to FOSS and mediawiki
> how do I start on this bug
> how do I replicate the error on my local machine

What does this bug mean by "page move rollback"? There is no such thing, cf. bug 4433. There is a "revert" button in the move log which includes an option to suppress redirect for users who have the suppressredirect right (e.g. sysops).
Comment 12 PiRSquared17 2014-03-06 03:58:47 UTC
(In reply to Chris M from comment #0)
> When using the page move rollback tool to counter page move vandalism, a
> redirect is left at the vandal title that still needs to be deleted by hand.
> See
> for example the deletion log for today (18 August) to see how much work this
> can
> be for admins.

What "page move rollback tool"?

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


Navigation
Links