Email whitelist is a module that helps you to specify a list of email address (comma separated values). After you save the settings, During user-registration process, this module will compare the email address entered with the list saved by admin. If it matches, only then the new user can successfully register. Example: efgh@gmail.com,"abcd@example.com",ijkl@xyz.com (so, only these email addresses are allowed to register in the site)

Apart from email address, you can also specify host names (comma separated values) in the similar way.
Example: yahoo.com,gmail.com,example.com,adf.com,asdf.in (so, only email addresses with these host names are allowed to register)

There is also a "negate" option - which does the opposite. If this option is enabled, it allows any email/host other than the listed ones.

There is "Access Rules" for the similar kind of functionality. There are also modules which only handles "host".
This is much more user friendly and works directly with comma separated values (csv) and take care of emails as well as hosts.

Project page: http://drupal.org/sandbox/amrit_b/1768342
GIT repo: http://drupalcode.org/sandbox/amrit_b/1768342.git

Thanks!

Comments

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Needs review » Needs work

Welcome,

please get a review bonus first. Then try to fix issues raised by automated review tools: http://ventral.org/pareview/httpgitdrupalorgsandboxamritb1768342git

mschudders’s picture

mschudders commented

1. Basic application checks

1.1 Ensure your application contains a repository and project page link.
Ok
Git link is not correct !!

1.2 Ensure your project is not a duplication.

Can't you accomplish the same with : Drupal > access_control > access rules ?

1.3 Ensure you don't have multiple applications.
You also have token input please close one of these because only one project needs to be review.

2. Basic repository checks

2.1 Ensure the repository actually contains code.
ok

2.2 Ensure you are working in a version specific branch.

ok but master branch is still there remove it please.

2.3 Ensure your project contains a minimum of handwritten code.
OK

3. Security Review

3.1 Ensure the project does not contain any security issues.

Looks ok , but maybe remove the dpm,... looks cleaner that way.
You made an typo in .admin.inc you typed : vaidation in stead of validation.

in admin.inc: you check if != "" (an empty string maybe just use isset of empty() functions ? idk this is just my opinion and not really necessay i guess

4. Licensing checks

4.1 Ensure the repository does not contain a ‘LICENSE.txt’ file.
ok
4.2 Ensure the repository does not contain any 3rd party (non-GPL) code.
ok
5. Documentation checks

5.1 Ensure the project page contains detailed information.

Maybe just add some headings;

5.2 Ensure the repository contains a detailed README.txt.
ok

Maybe add some more commeting to your functions what its supposed to do naming and functions looks clear but yea just in case.

6. Coding standards and style

6.1 Run an automated review and ensure there are no major issues.
See above = NOT ok.

7. API and best practices Review

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application.

If you reopen this please keep in mind that we are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and I'll take a look at your project right away :-)

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented
Issue summary: View changes

Git repo link corrected