Extension:ConfirmAccount

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 ext-confirmedit>Special:MyLanguage/Extension:ConfirmEdit|ConfirmEdit extension can be used (in conjunction with the ConfirmAccount extension) in order to use captchas to stop flood requests.

Optional
There are several configuration variables that can be adjusted in LocalSettings.php (after the require_once line that includes ConfirmAccount.php). See ConfirmAccount.config.php for all the variables that can be set. (The default values are in ConfirmAccount.config.php, but you should not edit that file).

For example, to set the person's bio as their userpage, set $wgMakeUserPageFromBio = true.

To disable the biography, set   to  :


 *  In other languages you have to replace "Main Page" and "Special:RequestAccount" with their local names, for instance "Hauptseite" and "Spezial:Benutzerkonto_beantragen" in a German wiki. 

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.

Minimal
To attempt to prevent spam, instead of captchas, blacklists and filters; manually moderate new user registrations, with a simpler Request account. Requesting only a username, email address and brief message. Add the following to <tvar|1>LocalSettings.php</> after the line <tvar|2>require_once "$IP/extensions/ConfirmAccount/ConfirmAccount.php";</>.

Optionally tweak 1>Help:system message</>|system messages: <tvar|2>requestaccount-text, requestaccount-notes, requestaccount-ext-text, requestaccount-acc-text</>.

Usage





 * 1) As a bureaucrat (or other user with the <tvar|1>confirmaccount</> permission), browse to <tvar|special> </>


 * 1) Click Review


 * 1) You will see the whole form with the users' data. Carefully review the form, and proceed to creating the account or rejecting the request.


 * 1) 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.
 * 1) After an account is created, the data input by the user at the time of the request can be referred to by typing the username at <tvar|special> </>

Sending notification email to multiple users
This extension allows sending emails to multiple approvers to confirm the account if these users have the  permission. This is in addition/alternative to the  setting.

This can be achieved (for instance for bureaucrats) by providing them this permission by adding the following to :

Pruning Frequency
To combat robot-requests, default settings prevent rejected email accounts from re-requesting an account for a random period of time after rejection.

If you want rejected emails to be able to re-request accounts immediately after rejection, or after a fixed wait-time (days, weeks, months, or even years after rejection), apply the following 2 steps:

1) In LocalSettings.php, after required declaration, set Rejected-Age to 0 (for immediate expiration on rejection), or to your desired wait-time, in seconds:

2) Add one line to the file <tvar|php> </> at the very end of the function <tvar|showForm> </> which shows the Request form, to force pruning right before any new request:

 original code: 

 new code: 

"Request account" Link
If you would like to add a "Request account" login link add the following to the "<tvar|1>LocalSettings.php</>" file:

as well as the text "Request account" to page "MediaWiki:Requestaccount".

Known issues

 * Do not set <tvar|1> </> to <tvar|2>true</> in <tvar|3>LocalSettings</>, it will override the request login and allow users to sign up without confirmation.


 * Do not set/create <tvar|1>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 <tvar|1>Special:RequestAccount</> at the user login form. You can edit <tvar|1>MediaWiki:loginprompt</> to remedy this.


 * 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 pwdreset>Special:MyLanguage/Extension:Password Reset</>|Extension:Password Reset or <tvar|1>Special:ResetPassword</> 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. This prevents email addresses from re-requesting accounts for an unknown time period.  You can override this behavior, and allow immediate re-requests, by forcing prune right before any new Request is submitted. 1>Extension:ConfirmAccount#Pruning_Frequency</>|Instructions here.


 * ext-ldap>Special:MyLanguage/Extension:ConfirmAccount/Integration with LDAP Authentication extension</>|Integration with LDAP Authentication extension

Troubleshooting

 * Notification emails do not get sent

If you are testing, note that a user must first confirm their email address through the link emailed to them, and then the email will be sent to the bureaucrat to confirm the account.

Make sure that setting(s) related to extension are introduced after the require_once line.

Not before, otherwise extension doesn't see these settings and they fail silently. e.g.

Also note that when using the 'confirmaccount-notify' setting, that each user in the group (e.g. sysop) will not receive notices unless their <tvar|options></> in <tvar|1>Special:Preferences</> allow "<tvar|email></>" and that they have confirmed their email address within the same form.