Last modified: 2011-03-13 18:04:40 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 10351 - Prevent cross-namespace moves from non-admins
Prevent cross-namespace moves from non-admins
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-06-24 08:38 UTC by (none)
Modified: 2011-03-13 18:04 UTC (History)
0 users

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


Description (none) 2007-06-24 08:38:23 UTC
Page moves are usually only done within the same namespace. However, recently there was a page-move vandal who moved articles into his own namespace in order to trick admins into deleting them. I see no reason why a user should be able to do such a move. Other than moving an article from a personal sandbox into the main namespace, where there is no reason to preserve the history. In case a cross-namespace move is necessary, an admin should be able to do it.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-24 14:17:35 UTC
Sorry, but this makes too many assumptions about the distinctness of namespaces.  In sites with multiple content namespaces, it may make perfect sense to move articles back and forth if they're misplaced, and surely there's no particular reason to prevent non-admins from userfying pages that would otherwise be deleted for some reason, for instance.  Essays might be moved between project and user space, many moves would be needed if a new namespace is created, all in all this isn't sufficiently distinct from ordinary moves to justify a distinct permission, and certainly not one restricted only to admins.

The answer to move vandals, like to any vandals, is not to make it more difficult for anyone to do anything, but to make it easier to revert them when they do it.  That's the idea of a wiki.

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