Last modified: 2011-07-12 04:31:11 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 T12102, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10102 - Links to nonexistent pages in protected namespaces cause error page on click
Links to nonexistent pages in protected namespaces cause error page on click
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.10.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-02 00:40 UTC by Dan Jacobson
Modified: 2011-07-12 04:31 UTC (History)
1 user (show)

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


Attachments

Description Dan Jacobson 2007-06-02 00:40:09 UTC
Allow us to explore the effects of
$wgNamespaceProtection[ NS_CATEGORY ] = array( 'sysop' );

Let's say a category has 100 members, but no content. The user will
arrive at the page via action=edit, whereas he will encounter a gruff
message, and _is denied knowledge of the 100 members_.

(And if he arrives not by action=edit, he will be invited to edit,
which of course ends up in him getting the above scolding.)

(So we take $wgNamespaceProtection back out of LocalSettings.php,
whereupon we notice that upon action=edit, one sees the 100 members
only if there is no content in the category. If there is any content,
the 100 members disappear from the screen.)
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-03 01:47:01 UTC
It's not clear what should be done about this, if anything.  Perhaps links to deleted pages in protected namespaces shouldn't go to the edit page if $wgUser can't edit them, but should instead go to the "this article does not exist" without the edit form.  But that would be potentially messy.  Probably the default "this article does not exist" message isn't appropriate, anyway, since it refers to creating it yourself IIRC.  We haven't really had nonexistent protected pages before on any significant scale, so maybe we should work out a different message for that, for view and/or edit.

The category issue I'm not considering because it's not currently intended that categories should have members but no text.  That issue is separate.
Comment 2 Dan Jacobson 2007-06-03 23:21:57 UTC
> The category issue I'm not considering because it's not currently intended that
> categories should have members but no text.  That issue is separate.

But that is the issue I am turning purple about. Please make it a seperate bug then.



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


Navigation
Links