Edit User

[jriker1]

I just installed the latest version of 3.3 from SVN.  In compiling and deploying it, when I click on my profile, there is no edit option.  Is something wrong here or is that something new?

Thanks.

JR

Edit:  Seems to be based on this check that is new <#if profile.capabilities.isMutable> but not sure what it's checking.

[kevinr]

Do you have LDAP or similar in your authentication chain on the repo side? That is why if you do.

Kev

[jriker1]

Thanks for the reply.  Yes I do.  I am authenticating with LDAP and using LDAP sync.  I was assuming since there is a google username field that may be tied to editing docs with google but can't set it because of this.  Was going to override and set it back to the way it worked in 3.2R2 as you could edit things there but wasn't sure if this was required as I couldn't find anything on how Google Docs works with Alfresco.

Thanks.

JR

[kevinr]

We are looking at solving the problem to allow non LDAP managed properties to be edited.

Kev

[jriker1]

Or just go back to the old way of letting a person edit anything and live with the sync updating syncable properties.

[jriker1]

By the way, perhaps I'm missing something, however how now does a user add an avatar image when using LDAP?

Thanks.

JR

[pharis]

By the way, perhaps I'm missing something, however how now does a user add an avatar image when using LDAP?

Thanks.

JR

I'm having the same issue …. anyway of adding an avatar image when having LDAP users ?

[jriker1]

I'm having the same issue …. anyway of adding an avatar image when having LDAP users ?

I'd give more details but not in a place where I can pull up code.  I would suggest looking at my original post where I identify what changed, and then download say the 3.2 version of that profile code and change it.  After all, you could always edit the profile before and sync would overwrite it if someone changed something they shouldn't have.  Alfresco team decided to just turn it off entirely until they could figure something out so why not just reimplement the old check which just checks if the current user is the user that's profile is trying to edit and allows editing of the fields.

JR

[kevinr]

This has been fixed for 3.3SP1 - appropriately mapped LDAP (or whatever)  external fields will now be individually greyed out in the UI. Other fields such as photo and bio etc. will be available for editing as normal. This applies to a users profile and admin user console pages.

Thanks,

Kev

[jriker1]

This has been fixed for 3.3SP1 - appropriately mapped LDAP (or whatever)  external fields will now be individually greyed out in the UI. Other fields such as photo and bio etc. will be available for editing as normal. This applies to a users profile and admin user console pages.

Thanks,

Kev

Thanks Kev.  Is this enterprise version?  For the 3.3f/g version in head now, I'm thinking I can set the isMutable to true in the function that checks based on the logged in user.  Is there a single function/method that checks the Mutability of editing a user's record?

Thanks.

JR