Make email not required for a Drupal site account

Created on 23 July 2008, over 16 years ago
Updated 14 March 2024, 9 months ago

Problem/Motivation

I would like to make a request for Drupal 7 (if it can't be done for any up-and-coming version of drupal 6) that an option be created so that providing an email address at registration is not necessary.

This is very important for school websites as children shouldn't need to provide an email address (and before a certain age shouldn't even have an email address due to inappropriate spam), and perhaps even for businesses which want an internal site for employees without them having to provide a personal contact email.

Currently, we have an option to disable the email authentication, but supplying an email address is *still* always required during sign-up.

Taking my situation regarding a school website, for example:
Duplicate email addresses aren't accepted, so I couldn't just tell the pupils to all use blackhole@ourdomain.com, as each email needs to be unique. I'm going to have to create a subdomain: no-email.ourdomain.com, and tell the pupils to sign-up to the website using name@no-email.ourdomain.com, and try to blackhole any mail based on the subdomain using a cpanel filter.

However, this is messy because:
1) it relies on the pupils following written instructions during sign-up
2) the user contact forms will silently fail when the email is blackholed
3) it would be great for the older children to be able to optionally supply email addresses; for the younger ones not; for drupal to intelligently check that a user has provided an email before trying to use it, and provide a message to users informing them that the intended recipient has not provided an email address.

There is a (currently broken) module which kind-of works around this issue by automating 1).
http://drupal.org/project/localemail

But it doesn't address 2) or 3) and of course, I'd rather see a more complete solution in core!

What do you think?
Cheers.

Steps to reproduce

Proposed resolution

Remaining tasks

Postponed on #2227381: Apply formatters and widgets to User base fields 'name' and 'email' β†’

User interface changes

API changes

Data model changes

Release notes snippet

✨ Feature request
Status

Active

Version

11.0 πŸ”₯

Component
User systemΒ  β†’

Last updated about 15 hours ago

Created by

πŸ‡¬πŸ‡§United Kingdom -Anti-

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States dww

    Also here via search, also building a site involving user accounts for people of all ages, including very young, for whom an email address is inappropriate. It'd be great if this wasn't necessarily a required property/base field.

    I understand the desire to "solve" this via #2227381: Apply formatters and widgets to User base fields 'name' and 'email' β†’ , however, the required bit is not something that can be controlled via widget nor formatter. That's a property of the field/basefield/property itself. Even if we were using regular field widgets for these things, how would we be able to control if this is required or not?

    Can't this proceed as a parallel effort? Don't we need something other than widgets or formatters to both let site builders control if this property is required, and teach the rest of core / contrib that email isn't necessarily always available?

Production build 0.71.5 2024