[Mahara-contributors] [Bug 1214647] Re: When an auth instance is deleted, disable it as a parent authority
** 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 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 Released Status in Mahara 1.7 series: Fix Released 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=5627offset=0limit=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 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1214647] Re: When an auth instance is deleted, disable it as a parent authority
** Changed in: mahara/1.7 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 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 Released 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=5627offset=0limit=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 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1214647] Re: When an auth instance is deleted, disable it as a parent authority
** Changed in: mahara Milestone: 1.8rc1 = 1.8.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 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: In Progress 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=5627offset=0limit=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 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1214647] Re: When an auth instance is deleted, disable it as a parent authority
** Changed in: mahara Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contrib members 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: In Progress 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=5627offset=0limit=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 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
[Mahara-contributors] [Bug 1214647] Re: When an auth instance is deleted, disable it as a parent authority
https://reviews.mahara.org/2424 -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contrib members https://bugs.launchpad.net/bugs/1214647 Title: When an auth instance is deleted, disable it as a parent authority Status in Mahara ePortfolio: In Progress Status in Mahara 1.7 series: In Progress 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=5627offset=0limit=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 ___ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
