When an auth instance is deleted, disable it as a parent authority
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Medium
|
Aaron Wells | ||
1.7 |
Fix Released
|
Medium
|
Aaron Wells |
Bug Description
Scenario:
1. Create an "Internal" auth instance (or any auth instance type, it doesn't really matter)
2. Create an XMLRPC auth instance, and set the Internal instance to be its "Parent authority"
3. Drop the Internal auth instance
Expected result: The XMLRPC auth instance should switch to having no parent
Actual result: The XMLRPC auth instance will *say* "None" if you look at its config (and throw a PHP warning) but in the DB it will still be configured to have the deleted internal auth instance as its auth instance
This situation causes a number of problems. The one I'd noticed before was that PHP warning on the XMLRPC auth instance page, which is because pieforms is trying to set the default to be the name of the auth instance that no longer exists. But the bigger problem (as seen here https:/
I think most admins would expect the XMLRPC instance in this case to simply lose its parent authority, not have to go in and manually save an apparently unchanged form instance in order to delete it.
Changed in mahara: | |
status: | In Progress → Fix Committed |
Changed in mahara: | |
milestone: | 1.8rc1 → 1.8.0 |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
https:/ /reviews. mahara. org/2424