On 24 Apr, 2009, at 22:13 , cybernytrix wrote:

>
> I reworked some Agilo-AccountManager related features:
> 1. Delete user (not remove user) deletes the user via
> acct_mgr::delete_user as well
Ok, thanks :-)

> 2. Fixed grant permission bug that raises exception if user with same
> credentials is present and you try to create the user again.
This is what trac is doing as well... may be it is as design?

> 3. Do not assign to team_member.full_name team_member.email since it
> creates the user in the DB and acct_mgr::has_user will always return
> true.
So may be we can set it after the user has been created... the whole  
Admin needs rework, we are going to Open the Agilo for Agilo  
development at the end of this sprint, probably this week, we are not  
yet done with the 0.8 but we need your help :-) And we count on the  
community support to fix and move forward the project... so if you  
want to have a "dev" account, please contact us :-)

> 4. Since I am using LDAP to get user info, I made the full name /
> email fields as read only after the account is created. I have
> acct_mgr patches for those interested (it works with windows AD as
> well).
That would be interesting... we can create a contrib area, and put  
there all the "extra" patches... or may be we find a way to do it at  
runtime, and detect on the fly which authentication is set ;-)

Thanks, I'll take the patch in, I think I'll need to modify something  
though, the 0.8 is already pretty changed ;-) Thank you very much for  
the improvements ;-)

Best
ANdreaT


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to