Extension:ConfirmAccount/de

The ConfirmAccount extension disables direct account creation and requires the approval of new accounts by a bureaucrat. Direct account creation can still be enabled (if you want Sysops/Bureaucrats to be able to directly make them) by configuring user rights.

The ConfirmEdit extension can be used (in conjunction with the ConfirmAccount extension) in order to use captchas to stop flood requests.

The new user log (now obsolete) extension also works with ConfirmAccount.

Configuration
Es gibt mehrere Konfigurationsvariablen, die in der LocalSettings.php eingestellt (Variablen werden nach der Zeile, require_once hinzugefügt.) werden können. Schaue in die ConfirmAccount.config.php für alle Variablen, die eingestellt werden können. (Die Standardwerte sind in der ConfirmAccount.config.php.) Die beiden Dateien sollen nicht bearbeitet werden.

Es gibt keine ConfirmAccount.config.php Datei mehr. Die Einstellungen sind in der ConfirmAccount.php enthalten. Standardmäßig muss bei der Anmeldung von neuen Benutzern in der Biografie 50 Wörter verwendet werden. Dieses kann über die LocalSettings.php mit folgender Variable geändert werden Standardmäßig muss bei der Anmeldung von neuen Benutzern in der Biografie 50 Wörter verwendet werden. Dieses kann über die LocalSettings.php mit folgender Variable geändert werden

Wenn Sysops immer noch Benutzer-Konten erstellen kann, muss dieses über die LocalSettings.php geändert werden: $wgGroupPermissions['*']['createaccount'] = false;

Wenn nur eingeloggte Benutzer die Anmeldeseite aufrufen können, müssen die Anmeldeseite für "Gäste" freigeschaltet werden. Dieses kann über die Variable $wgWhitelistRead in derLocalSettings.php passieren. Zum Beispiel: $wgWhitelistRead = array('Spezial:Benutzerkonto beantragen','Hauptseite');
 *  In other languages you have to replace "Special" and "Main Page" with the words that are used instead of special in your language like "Spezial" and "Hauptseite" in a German wiki, otherwise nobody will be able to create an account.

To further categorize users based on their interests, you can set up MediaWiki:Requestaccount-areas. This should be in a format like:
 * *Topic|Topic wiki page|text to append to all interested users' bios |text to append to all interested users' bios in group0|text to append to all interested users' bios group1|text to append to all interested users' bios in group2|...

These group numbers are based on. So if 0 is the index for 'authors', then 'authors' interested in a topic will have the group0 text appended to their biography. This can be useful, say, if users can be approved as either authors or editors. Authors can have "category:X authors" where X is a topic, like "mathematics", and editors can have "category:x editors". You can have as many groups as you want, but you need at least one.

Use

 * 1) As a bureaucrat (or other user with the confirmaccount permission), browse to Special:ConfirmAccounts
 * 2) Click Review
 * 3) You will see the whole form with the users' data. Carefully review the form, and proceed to creating the account or rejecting the request.
 * 4) If you chose to create the account, the user's biography will become their userpage and the userpage will be automatically created with the default summary of Creating user page with biography of new user.

Note: In order for bureaucrats to get notified of pending requests you need to set an email / mailing list in ConfirmAccount.config.php $wgConfirmAccountContact = 'Bureaucrat@domain.com';

Known issues

 * Do not set $wgGroupPermissions['*']['createaccount'] to true in LocalSettings, it will override the request login and allow users to sign up without confirmation.
 * Do not set/create MediaWiki:Requestaccount-areas/xx where xx is a language code, the first part of each line is used as the keys to store in the DB for the items account requesters check.
 * Older versions of MediaWiki may not show the link to Special:RequestAccount at the user login form. You can edit MediaWiki:loginprompt to remedy this.
 * Name collisions: account creations will be checked and stopped if it collides with a pending name. Requests are checked for pending/account name collisions too.
 * AuthPlugin stuff: If a central login like CentralAuth is used, when accounts are confirmed and made, we may get name collisions if each wiki of the farm lets you request accounts on it. Collisions are dealt with by picking a new name.
 * If your email client loses its mail data before sending it out, users will not get their passwords but may have an account. Since no one knows the passwords, you may want to use Extension:Password Reset to send them new ones.
 * If only a few people view the confirm accounts page, the randomly triggered pruning of old requests will not trigger often, so old rejected requests may persist.
 * Integration with LDAP Authentication extension