** Changed in: mahara
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask
on #mahara-dev or mahara.org for
Hi Kristina and RoberL,
This fix was contributed by Federation University Australia:
http://federation.edu.au/
Can we give them credit / mention for this?
Thanks,
Ghada
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matchi
** Changed in: mahara
Status: Confirmed => Fix Committed
** Changed in: mahara
Milestone: None => 16.04.0
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contribut
One of our clients is affected by this. I'll put in the changes I made
for them.
** Changed in: mahara
Assignee: (unassigned) => Ghada El-Zoghbi (ghada-z)
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscript
I agree with low priority also because usersuniquebyusername is an
experimental feature and not in much use afaik.
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors
Marked low priority because it will only rarely cause any problems.
Normally, even if you have $cfg->usersuniquebyusername enabled, we
create auth_remote_user records for each user anyway, with the remote
username set the same as the user's Mahara username.
So, this bug will only cause problems if
6 matches
Mail list logo
