Your Moodle version

Authentication: Email-based self-registration with admin confirmation

Maintained by Picture of Felipe Carasso Felipe Carasso
Provides email-based self-registration with admin confirmation instead of user confirmation.
Moodle 2.3, 2.4, 2.5, 2.6, 2.7

The confirmation email is sent to the main admin account's email address.

When the admin clicks on the confirmation link, a "welcome" email is sent to the user.

Note that the admin must use the confirmation link in the email for the user to receive the automatic notification. Approving the account from the user admin interface does not trigger it.

Email body is customizable within the language file.

Based on default email-based self-registration module.

You can customize the e-mail messages by editing the language file or using Moodle's language editor.


Screenshot #0
Screenshot #1


Picture of Felipe Carasso
Felipe Carasso (Lead maintainer)
Please login to view contributors details and/or to contact them

Comments RSS

Show comments
  • Picture of Felipe Carasso
    Wed, Jan 13, 2016, 12:38 PM
    @Muhd: The latest version of this plug-in uses Moodle APIs that require that minimum version. It won't work on an older version. You can still try to use an older version of this plug-in that supports your Moodle version.

    @Alan: If you use the regular 'email self-registration', does the user get the notification? Maybe you customized the notification and made a mistake?
  • Picture of Alan Cherwinski
    Thu, Jan 14, 2016, 12:23 AM
    Thanks Muhd and Felipe,
    I am using the latest release of 2.9.4 and an up to date plug in. I have not modified or customized the any code. The registration results page displays over 1200 lines of code to the end user and still does not send a message to the self registering user. The email is going to the site administrator.
  • Picture of Alan Cherwinski
    Thu, Jan 14, 2016, 12:53 AM
    Thanks Muhd and Felipe, - I figured it out. The email debugging was turned on, the regular debugging was set to minimal - hence the display code. Also the self registration and sr with admin where enabled, but self registration was not enabled on the manage authentication page. Once all those were aligned and the debug code eliminated it worked like a charm. A bad combination of missteps lead to my confusion. Thanks again for your help and the great pluggin.
  • Picture of Alan Cherwinski
    Thu, Jan 14, 2016, 1:15 AM
    Could there be some other setting or configuration required or that I am missing? The confirmation link in the email is not working "Error 500". I've cut and pasted the url and can't see what is the issue. http://<>/auth/emailadmin/confirm.php?data=Yq5SePmiylh7erQ/alantest

    (FYI if a single site admin is selected in the pluggin setting the message is going to all)
  • Picture of Alan Cherwinski
    Thu, Jan 14, 2016, 2:33 AM
    My dedicated server admin checked the log files for the broken confirm code and reported back:
    Based on the logs in the Apache error log, the problem is with the script (Premature end of script headers: confirm.php):

    CT-19331-bash-4.1# tail -f /usr/local/apache/logs/error_log
    [Wed Jan 13 13:07:47 2016] [error] [client] Premature end of script headers: confirm.php
  • Picture of AM Sanat
    Sat, Feb 20, 2016, 6:29 PM
    When install new calendar and set it on site administration- appearance- calendar- calendar type
    If new user create new account
    Automatically In profile set Gregorian for preferred calendar
    But calendar type must set to preferred calendar
    Please check it
  • Picture of Chad Nixon
    Tue, May 10, 2016, 10:43 PM
    Love the plugin! But I am trying to find the settings in the new plugin that allows you to specify userfields?

    I just released a new version where you can use specific user fields in the notification message. See default notification message for example.

    id: 30
    auth: emailadmin
    confirmed: 0
    policyagreed: 0
    deleted: 0
    suspended: 0
    mnethostid: 1

    I just want to display first name, surname, email, password and custom user field only.
  • Picture of Felipe Carasso
    Wed, May 11, 2016, 1:21 AM
    Hi Chad,

    Like the message says, look into the message template. There are three placeholder examples to inspire you. One for a single user field (username, I believe), one for all fields including custom profile fields, and one for just the custom profile fields. If you compare the single user field example with the all fields, you'll notice that all you have to do is refer to the field you want.

    Best regards,
  • DigiDago
    Wed, Jul 20, 2016, 6:28 AM
    Hi Felipe,

    Have you test your plugin with Moodle 3.1 ?
    Best regard.
  • Picture of Felipe Carasso
    Wed, Jul 20, 2016, 9:46 PM
    Hi Clément, not yet, but it's likely to work. I should be updating my moodles sometime soon and we'll see.
  • Picture of Dr. Nellie Deutsch
    Sat, Jul 23, 2016, 3:46 AM
    1000s of my users are out because I just upgraded to 3.1.1. Any suggestions?
  • Picture of Felipe Carasso
    Tue, Jul 26, 2016, 12:45 AM
    Hi Nellie, sorry to hear about your problems.

    Since I haven't tried the plug-in on 3.1 myself just yet, I cannot confirm that your problem is related to it. The best I can suggest is to check your authentication and users configurations for disabled flags.

    Clément, have you tried it with 3.1 yet?

    Best regards,
  • DigiDago
    Tue, Jul 26, 2016, 4:08 AM
    Hi Felipe,

    I just tried with a fresh Moodle 3.1. I usualy use only "user login method" to add users automaticly to courses. So in my test, everything seems to be ok but I don't test other methods (course view / course activity/resource view).
  • Picture of Ziyad Muslat
    Thu, Aug 4, 2016, 12:28 AM
    Hi Felipe,
    I just installed the plugin in my moodle 3.1.1. The plugin works great. However, when a new user registers for an account. A debugging message shows up as follows (after clicking "Create my account") :

    Events API using $handlers array has been deprecated in favour of Events 2 API, please use it instead.

    line 3938 of /lib/deprecatedlib.php: call to debugging()
    line 4216 of /lib/deprecatedlib.php: call to events_dispatch()
    line 809 of /lib/classes/event/base.php: call to events_trigger_legacy()
    line 99 of /auth/emailadmin/auth.php: call to core\event\base->trigger()
    line 86 of /login/signup.php: call to auth_plugin_emailadmin->user_signup()

    As I said, the registeration process goes through, but I'm not sure what do I need to do to comply with this message.
  • Picture of Felipe Carasso
    Thu, Aug 4, 2016, 8:26 AM
    Hi Ziyad,

    For now, you can modify/disable error logging to have that hidden through Site Administration -> Development -> Debugging, have 'Display debug messages' unchecked and maybe change 'Debug messages' to something less verbose like 'Errors'.

    I'll look into it once I'm back home from my volunteer work for the Olympics.

    Best regards,
1 2 3 4 5 6
Please login to post comments