7 Components: the Function Pages - Developers

Permitting user
registration
Database tables
122
��
��
��
Thus, there is no whitelist for editing and none for reading pages.
That means that non-registered users are not excluded from having
access. In addition, visitors can register as users. If you want to limit
editing privileges only to registered users, you should activate the
edit whitelist:
$wgWhitelistEdit = true;
$wgWhitelistRead = false;
Here, it is not possible to release only certain pages for general editing.
On the other hand, for a read whitelist, the individual pages
must be explicitly cleared for reading:
$wgWhitelistRead = array("Page1", "Page1");
This means that you will have one or more openly accessible introductory
pages for your wiki, but that all others can only be accessed
upon registration.
The previously discussed settings assume that users will first
make themselves known to the system before reading or editing anything.
This is done by logging in, or if a user does not yet have an
account, registering. In principle, this means that reading and editing
is still open to anyone. If you would like to prevent this (e.g. because
you have a fixed team of authors), you must limit the possibility of
opening new accounts to sysops.
$wgWhitelistAccount = array ( "user" => 0,
"sysop" => 1, "developer" => 1 );
If you, as an administrator, wish to register a new user, you must
first log in yourself and then access the page Special:Userlogin.
Since it is not listed among the special pages, it must be activated via
a search or URL. Enter a user name and the email address of the new
user and click via email. A random password will then be generated
and sent to the user.
8.2
Database Structure
Almost all data created in working with MediaWiki is stored in the
database. It is the final resort for edits to the data if no corresponding
special page is available for the desired tasks. Thus, we provide an
overview of the tables in the database below (see Tab. 8.2):
8 Administration