Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
user.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 May 2006 at 17:06 UTC
Updated:
29 Jul 2014 at 17:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
killes@www.drop.org commentedNo new features will be added to 4.7.
Your patch does nor comply with our coding standards.
Comment #2
corris commentedoh, yea, should have been cvs, sorry.
was it the indentation? how's this one?
Comment #3
Tobias Maier commentedhave a look at http://drupal.org/node/53103
I think this would be userful for your purpose
Comment #4
dries commentedCoding style needs work; incorrect use of spaces. Also, we write 'e-mail' not 'email'. All minor changes. ;)
Now, with Drupal 4.7.0, an LDAP authentication module might actually be able to modify the user.module's generated forms. Maybe that's a better solution? Worth exploring? It wouldn't require fiddling with permissions when the LDAP authentication module is enabled.
Comment #5
dries commentedCross-posted an issue at http://drupal.org/node/65159. Let's see what the LDAP integration module maintainers think/need.
Comment #6
dries commentedSee also http://drupal.org/node/63246.
Comment #7
Bèr Kessels commentedOne big problem with implementing http://drupal.org/node/65159 cleanly is that Drupal has hardcoded the requirement of an emailaddress.
user_validate_mail($mail) is called, instead of the default Form Api validation. We would need to implement a better way in core first, then LDAP auth can simply override the forms with form_alter. Right now we cannot simply unset a form, because of this harcoded requirement of an email address.
Comment #8
panchoNew features go to the D7 branch.
Comment #9
Jaza commentedSurely this can be achieved by form_alter'ing the 'email' and 'password' fields to be 'value' or 'hidden' types?
Closing.