Let's disable the field locking/unlocking in an institution if these
fields are locked at the site level (No institution).
** Changed in: mahara
Milestone: None => 1.3.0
** Changed in: mahara
Assignee: (unassigned) => Richard Mansfield (richard-mansfield)
--
No institution and Fields Locked / Unlocked
https://bugs.launchpad.net/bugs/547632
You received this bug notification because you are a member of Mahara
Core, which is the registrant for Mahara.
Status in Mahara ePortfolio: Confirmed
Bug description:
Reference : http://mahara.org/interaction/forum/topic.php?id=733#post3632
We have two institutions. One is No Institution and other is ORG_NAME.
In both institutions the first name and last name are locked.
Now, if you unlock these fields in ORG_NAME institution than users in this
institution should be able to change these fields in their profile. But they
are not able to change these as fields are still locked for them even after
unlocked in site administration.
Now, including above changes if you also unlock these fields in No Institution
than users from the ORG_NAME institution are able to change these fields as
they are unlocked for them.
Is it normal? Is it a bug or feature?
If it is a bug okay I can report it to tracker. Wink
If this is a feature than seems irrelevant. Laughing
Note : when these fields are unlocked in No Institutions and locked in
ORG_NAME institution than users of ORG_NAME are not able to change these fields
in profile. This is fair.
This bug was imported from eduforge.org, see:
https://eduforge.org/tracker/index.php?func=detail&aid=3322&group_id=176&atid=739
_______________________________________________
Mailing list: https://launchpad.net/~mahara-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~mahara-core
More help : https://help.launchpad.net/ListHelp
