Extension:ConfirmAccount/ru

Расширение ConfirmAccount отключает прямое создание учетной записи и требует утверждения новых учетных записей бюрократом. Прямое создание учетной записи все еще можно включить (если вы хотите, чтобы /бюрократы могли создавать их напрямую), настроив.

Расширение можно использовать (вместе с расширением ConfirmAccount), чтобы использовать капчи для предотвращения флуд-запросов.

Дополнительно
Есть несколько переменных конфигурации, которые можно настроить в LocalSettings.php (после строки require_once, содержащей ConfirmAccount.php). См. ConfirmAccount.config.php для всех переменных, которые можно установить. (Значения по умолчанию указаны в ConfirmAccount.config.php, но вы не должны редактировать этот файл).

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

Чтобы отключить биографию, установите  на  :


 * На других языках вы должны заменить "Main Page" и "Special:RequestAccount" их местными именами, например, "Hauptseite" и "Spezial:Benutzerkonto_beantragen" в немецкой вики.

Чтобы дополнительно классифицировать пользователей на основе их интересов, вы можете настроить MediaWiki:Requestaccount-areas. Это должно быть в таком формате:


 * *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. Таким образом, если 0 является индексом для 'авторов', то 'авторы', интересующиеся темой, будут иметь текст group0, добавленный к их биографии. Это может быть полезно, скажем, если пользователи могут быть утверждены как авторы или редакторы. У авторов может быть "категория: X авторы", где X — это тема, например "математика", а у редакторов может быть "категория: x редакторы". У вас может быть столько групп, сколько вы хотите, но вам нужна хотя бы одна.

Минимально
Чтобы попытаться предотвратить спам, вместо капч, черных списков и фильтров; вручную модерировать регистрацию новых пользователей с помощью более простого Запрос учетной записи. Запрашиваются только имя пользователя, адрес электронной почты и краткое сообщение. Добавьте следующее в LocalSettings.php после строки require_once "$IP/extensions/ConfirmAccount/ConfirmAccount.php";.

Optionally tweak system messages: requestaccount-text, requestaccount-notes, requestaccount-ext-text, requestaccount-acc-text.

Usage




Carefully review the form, and proceed to creating the account or rejecting the request.
 * 1) As a bureaucrat (or other user with the confirmaccount permission), browse to
 * 1) Click Review
 * 1) You will see the whole form with the users' data.
 * 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

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 the "LocalSettings.php" file:

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 the "LocalSettings.php" file, 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  at the very end of the function   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, the latest version of the extension already adds it for you. However, if that doesn't work, you will need to update to the latest version of your branch of ConfirmAccount from Git. For instance, if you are using MediaWiki 1.35, you should stay on the REL1_35 branch but pull from Git to retrieve the latest changes.

Known issues
You can edit MediaWiki:loginprompt to remedy this. Since no one knows the passwords, you may want to use Special:ResetPassword to send them new ones. 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. Instructions here.
 * Do not set  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.
 * If your email client loses its mail data before sending it out, users will not get their passwords but may have an account.
 * 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

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 in Special:Preferences allow "" and that they have confirmed their email address within the same form.



См. также

 * Extension:InviteSignup, for administrator-initiated (mass) account creation
 * TwnMainPage extension, offering a "sandbox" where user can create an unprivileged account, propose some edits and ask approval