It turns out a lot of existing code checks the boolean
value of usr.suspendedcusr to determine if a user should
be treated as suspended or not. The LDAP sync cron (and,
indeed, any code suspending users via a cron task) was
setting usr.suspendedcusr to 0, which is boolean false,
so these users would be treated as not suspended.
We are going to update all usr.suspendedcusr = 0
to a valid site admin ID.
Change-Id: Iecfbfd8a4cdd98d5d07149bb40c64308262ea234
behatnotneeded: Test to come later
Reviewed: https:/ /reviews. mahara. org/6765 /git.mahara. org/mahara/ mahara/ commit/ 04defa2c15d7cb7 505114efc09c172 8e08ad1439
Committed: https:/
Submitter: Robert Lyon (<email address hidden>)
Branch: 16.04_STABLE
commit 04defa2c15d7cb7 505114efc09c172 8e08ad1439
Author: Ghada El-Zoghbi <email address hidden>
Date: Mon Jul 25 17:14:01 2016 +1000
Bug 1606101: usr.suspendedcusr must be non-zero
It turns out a lot of existing code checks the boolean
value of usr.suspendedcusr to determine if a user should
be treated as suspended or not. The LDAP sync cron (and,
indeed, any code suspending users via a cron task) was
setting usr.suspendedcusr to 0, which is boolean false,
so these users would be treated as not suspended.
We are going to update all usr.suspendedcusr = 0
to a valid site admin ID.
Change-Id: Iecfbfd8a4cdd98 d5d07149bb40c64 308262ea234
behatnotneeded: Test to come later