Also, one thing I forgot to ask. Your contribution will have to conform to our contribution policy, which means you'll have to "sign" your commit. Are you able to post on the bug report saying that you're happy for your patch to be contributed according to the policy?
]]>I need to think about email address that what sort of things should be implemented for General Mahara Users. I will look into this and will come up with some work.
]]>
I posted a cleaner version of your patch on the bug tracker, though I haven't had a chance to test it yet. I think what you are describing about the e-mail makes sense, though if the email field was locked then maybe it could be synced ok - I guess that would require a bit more code to handle. As always in the FOSS world, if you code it, you get the behaviour you want anyway
]]>If user decides to make other email as default and leave the ldap email as another email than usr table's email column is updated with this new email address. And ldap email is added into artefact table.
Now, next time when user logs in and update flag is enabled than usr table's email address will be again replaced with ldap one.
This is unfair as we can't force the user about email preferences. I think this point is not considered.
This is my understanding so far while going through XMLRPC code and LDAP code. Please, correct me if I am wrong.
Just one thing I am not checking the email field. There was confusion about to do or not ! Please, give direction about it so I can add this also.
I tried to upload it on eduforge feature request but end up with creating a new feature request. Please, delete this new feature and upload attachment file on original feature request. Seems no privilege to upload attachment for the feature request at Eduforge.
https://eduforge.org/tracker/?group_id=176&atid=742&func=detail&aid=3392
]]>
Still need to do some testings and need to verify other stuff as I did on the fly.
Will get back when it is finished.
]]>
1.2 should be quite soon now, you might have seen we just released beta 2. After it's released, we wouldn't backpatch a feature to 1.1 - unless at the request of a client.
I'm not sure the feature would take long to be honest, so it would be much funding required - you may even have people in your organisation who could do the work
]]>Please, if you can say tantative time for 1.2 release than we can decide few things about our installation.
]]>
But within Mahara this name is not updated and requires to change manually (we have locked first and last name for all).
Can this be done automatically when user logs in ? With every login it should check with LDAP and update the name/details according to that.
I think this can be good/necessary feature request.
]]>