Last modified: 2007-11-21 16:37:53 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 12027 - Different error message when attempting to mark non-mainspace pages as patrolled
Different error message when attempting to mark non-mainspace pages as patrolled
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Low normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-11-18 16:40 UTC by Gurch
Modified: 2007-11-21 16:37 UTC (History)
1 user (show)

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


Description Gurch 2007-11-18 16:40:51 UTC
Right now new pages patrolling is enabled on the English Wikipedia for articles only. If one attempts to mark a non-mainspace page as patrolled, the message returned is "The Recent Changes Patrol feature is currently disabled.", which is slightly misleading; something like "Patrolling is not enabled for this namespace" might be better.
Comment 1 Raimond Spekking 2007-11-21 08:00:07 UTC
New pages patrol works for all namespaces, see for a patrolled new page by me in the image talk namespace.

Maybe you tried to patrol a subsequent version (non new)?
Comment 2 Gurch 2007-11-21 16:37:53 UTC
Yes, I've realized that now... I definitely still got a message telling me it was disabled when it wasn't, though. It must have been for some other reason.

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