Last modified: 2010-03-16 08:33:03 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 22054 - CentralAuth: Wiki sets should be public
CentralAuth: Wiki sets should be public
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Victor Vasiliev
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-01-08 10:15 UTC by Gurch
Modified: 2010-03-16 08:33 UTC (History)
3 users (show)

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


Attachments

Description Gurch 2010-01-08 10:15:50 UTC
Currently the names and contents of wiki sets only seem to be accessible through [[Special:EditWikiSets]], which is restricted to those with the appropriate rights, i.e. stewards.

This data ought to be publicly viewable, as it doesn't contain any private or personal information and is of use to non-stewards. For example, those who have been assigned global rights over a wiki set would like to know which wikis it is their rights are on, and requiring the stewards to maintain a separate, public list is unnecessary and open to errors/inconsistencies.

The way this usually seems to be handled by extensions is to show the same interface, but with read-only input fields and no submission functionality, as done by for example AbuseFilter and CentralNotice.
Comment 1 Victor Vasiliev 2010-03-16 08:33:03 UTC
Should be fixed in r63808.

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


Navigation
Links