Create #confirm property to ensure equality of two input fields

Created on 21 January 2007, about 18 years ago
Updated 19 March 2025, 21 days ago

Problem/Motivation

Provide two e-mail fields (e-mail and 'confirm e-mail') to ensure accuracy on user registration. The LoginToboggan module does this.

Proposed resolution

Abstracting this to a new property name "#confirm" that can be applied to any Form API element.

Remaining tasks

Review the patch in comment #32.

User interface changes

  • New option to enable 'E-mail address confirmation field' in the user accounts settings page (in the 'registration/cancellation' fieldset).
  • If that option is enabled, an additional field on the user registration form (user/register) for 'Confirm e-mail address'.

API changes

  • Addition of #confirm property to the Form API.
  • TBD. Potential removal of the Form API element type 'password_confirm'.

Original feature request by birdmanx35

Part of a series of reforms for the login system, this patch would ideally provide two e-mail fields to ensure accuracy on registration, a feature that has previously been provided by the LoginToboggan module.

The login functionality applies to all Drupal installs, and this usability feature seems to me to be applicable to all Drupal installs and therefore the 6.x-dev core.

NOTE: I have no coding skills whatsoever, however, I hope I can contribute my ideas and hopes to Drupal.

✨ Feature request
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

forms system

Created by

πŸ‡ΊπŸ‡ΈUnited States birdmanx35

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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 smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024