Last modified: 2011-03-13 18:04:51 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 6381 - Restricted Articles
Restricted Articles
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
PC All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-06-20 12:08 UTC by sspecter
Modified: 2011-03-13 18:04 UTC (History)
0 users

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


Description sspecter 2006-06-20 12:08:48 UTC
HI, im using a Calendar extension in my wiki, and wanted to create a Agenta
feature for any user create his own Agenda. But I cant make any Agenda extension
work because wikiMedia dont have any mechanism to block article viewing.

Is there any plans to make an option to restrict articles per user?


I know many will complain that this hurt the wiki Idea to be edited by all
users, but I disagree. Not all wikis have ALL contents to be viewed/altered by

It would solve many wiki problems like
* banning specific users in a specific page (to prevent banning users from wiki
for disputing disputed articles).
* creating administrator-only pages (blocking editing and viewing), like edit
pages for Commons.CSS, LocalSettings.php, etc...
* Protect User subpages to be seen by other users and listed by wiki
* Allow Moderators (non-administrator users) allowed to modify certain Special pages
* protecting '''Special''' pages, and allow the same mechanism be used by
special pages, configuration page, main page, normal pages (against vandalism)


I have a simple idea: Make User subpages only acessed by himself. A variation of
it would be make any subpage inside the '''protected''' subpage
([Username]/Protected/[any_subpage]) only accessed by himself.

Of course, these pages should be protected from '''editing''' and
'''outputing''' from other users


A much better, more complete idea, but also more complex, should implement:
* '''per-Page variables'''
** list - list of users forbidden or allowed to '''edit''' the article (should
allow adding groups, like administrators)
** isRestricted - If FALSE, the list is ignored and the page can be
viewed/edited by anyone.
** isViewRestricted - If TRUE, the page will be protected from '''view''',
besides protected from edit. If FALSE, the page can be ''''viewed''' by anyone,
but not '''edited'''. This restriction follow the list.
** isWhiteList - If FALSE, the list is a ban list. (anonymous can still edit the
page) If FALSE, the list is a white list and only the users from the list can
'''edit''' the article
** restrictTimer - Timer in minutes to disable the page restriction (by setting
isRestricted = FALSE). 0 = restriction disabled; -1 = infinite (timer disabled)
* '''Global Variables'''
** canUserEditArticleList - if TRUE, the creator of the article can edit article
configurations (change article variables), if FALSE, only the Administrator can
do it.

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