Create #confirm property to ensure equality of two input fields
birdmanx35 - January 21, 2007 - 06:47
| Project: | Drupal |
| Version: | 8.x-dev |
| Component: | forms system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
| Issue tags: | Novice |
Description
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.

#1
#2
+1 Subscribing!
Setting this to bug report because I feel this is a security related issue. Almost all CMS systems provide this functionality to make sure users are not creating bad passwords.
#3
tagging for novice queue
#4
What about abstracting this to a new property name "#confirm" that can be applied to ANY field?
I will take that on, unless there are objections.
edited for terminology
#5
In this patch:
Not in this patch:
Feedback welcome -- thanks for reviewing & testing
#6
#7
The last submitted patch failed testing.
#8
#9
The last submitted patch failed testing.
#10
+1, subscribing.
Your coding style needs work - please read http://drupal.org/coding-standards and sub-pages about comment standards.
#11
rerolled @ HEAD
#12
Looks like the intent of this issue has changed. +1 for a #confirm property.
#13
Bot hasn't finished testing yet but either way it needs a lot of work from the coding standards standpoint, as sun pointed out.
#14
Can you please be a bit more specific w.r.t coding standards?
I ran it through Coder already.
#15
reroll, with code style and translation related changes
#16
Change component. This is not related to the Field API.
#17
The last submitted patch failed testing.
#18
#21
Guess it's too late for 7.x now.
#22
Is this feature now available in 6.x or have you given up?
#23
Aza: this feature won't make it into 6.x...only bug and security fixes go in at this point, and now that 7.x has reached code freeze, it's not making it in there either, so we can only hope for 8.x at this point.