Patch #4643
closed
Allow on-the-fly creation on member addition
Added by Marcel Waldvogel almost 15 years ago.
Updated almost 12 years ago.
Description
In our setup, our users are in LDAP, with onthefly creation enabled.
The standard workflow for inviting a new member into a project is rather awkward:
- Send mail to invite the user with request to login once
- That user logs in
- Wait for that user's acknowledgement mail
- Add the user to the project
This patch allows the following simplified procedure:
- Add new user directly in the member screen to the project
- Notify the user
You now can enter a login name from any onthefly LDAP source in the settings/members search box, select a role, and click "add" to have everything happen at once. For larger group additions, you can even add multiple names separated by whitespace. This is IMHO the most straightforward way to add new users, although it might not be obvious to first-time users.
The code is not the nicest and user feedback is minimal, but it fulfills the purpose. Feel free to adapt it.
Files
Your patch is also rather... minimal :)
Holger Just wrote:
Your patch is also rather... minimal :)
Sure, especially after removing my logger events. Be aware that I am not a senior Rails expert (yet :-)).
To my defence, I basically do consider my patch to be in line with the member addition UI, whose error visualisation is minimal (just entering a name and not selecting a user or not selecting a role will not give any visual feedback. Therefore, I would not know how to integrate this function into the code.
However, if there you could give me concrete advice how to improve the code, I would be glad to try and implement it.
Marcel Waldvogel wrote:
However, if there you could give me concrete advice how to improve the code, I would be glad to try and implement it.
Well, I think the first step on improvement would be to upload the actual patch. Your attachment consists only of 9 random chars. Like I said: rather minimal :)
Oh, I did not take the comment as serious as I should have. In fact, this was my submission for the Obfuscated Rails Coding Contest :-). Here's the real thing:
This patch has been superseded by #4755 (nicer code and also LDAP group support)
- Status changed from New to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by