mahara-contributors team mailing list archive

[Mahara Bot <1214647@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/2574
Committed: http://gitorious.org/mahara/mahara/commit/6cde02ab80c60e6831d2435fd4c68b64994b63ec
Submitter: Son Nguyen (son.nguyen@xxxxxxxxxxxxxxx)
Branch:    1.7_STABLE

commit 6cde02ab80c60e6831d2435fd4c68b64994b63ec
Author: Aaron Wells <aaronw@xxxxxxxxxxxxxxx>
Date:   Wed Aug 21 11:38:48 2013 +1200

Unset deleted institutions as parent authority to other institutions

Bug1214647

Change-Id: I03a365c4bfb25cd69a8ca83293bf25ed53ca1234

-- 
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 forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1214647

Title:
  When an auth instance is deleted, disable it as a parent authority

Status in Mahara ePortfolio:
  Fix Committed
Status in Mahara 1.7 series:
  Fix Committed

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://mahara.org/interaction/forum/topic.php?id=5627&offset=0&limit=10#post24259
  ) is that it can cause problems when it tries to auto-create or auto-
  update user accounts from the child authority.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1214647/+subscriptions