Last modified: 2011-01-21 14:37:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T20184, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18184 - Got $wgNamespaceProtection, lack $wgNamespaceNoWatch
Got $wgNamespaceProtection, lack $wgNamespaceNoWatch
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Watchlist (Other open bugs)
1.15.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-26 21:14 UTC by Dan Jacobson
Modified: 2011-01-21 14:37 UTC (History)
1 user (show)

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


Attachments

Description Dan Jacobson 2009-03-26 21:14:46 UTC
In includes/Namespace.php there is:
	/**
	 * Can pages in a namespace be watched?
	 *
	 * @param $index Int
	 * @return bool
	 */
	public static function isWatchable( $index ) {
		return $index >= NS_MAIN;
	}

However, things are not so simple these days.

Now that there is $wgNamespaceProtection, administrators also need a
similar mechanism to say e.g., "don't encourage the user to watch a
page that is not even allowed to ever be created." Or who knows what
might be on the admin's mind.

You don't want to just "do they have read permission according to
$wgNamespaceProtection etc." as the basis for deciding if they can
watch a page. It is more complicated than that.

E.g., a NS_CATEGORY page that they are looking at because it has
members, but will never have content, because the admin has set
$wgNamespaceProtection[NS_CATEGORY]=$wgNamespaceProtection[NS_CATEGORY_TALK]=array('editinterface');
The admin doesn't want them thinking that watching it will notify them
when a new member is added to the category, etc. (As I bet it
currently doesn't.)

So anyways, you still need to offer the admin an array
($wgNamespaceNoWatch?)that he can tinker with like
$wgNamespaceProtection, so he can have the flexibility to institute
whatever devious watchlist restrictions he has in mind.

No rush, but will come in handy one day.
Comment 1 Chad H. 2009-03-26 23:26:33 UTC
$wgNamespaceProtection has nothing to do with read rights. Nor is there any (core) way of managing per-namespace read rights. 

I can't see any reason why a user shouldn't be allowed to watch a page they can't edit. Nor do I really see a reason for disallowing watching of any particular namespace, except those that can't be watched ($index < NS_MAIN). Inclined to say WONTFIX.
Comment 2 Antoine "hashar" Musso (WMF) 2011-01-21 14:37:20 UTC
Will not fix this one since it is irrelevant.

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


Navigation
Links