mahara-contributors team mailing list archive

[Mahara Bot <1298855@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://reviews.mahara.org/3156
Committed: http://gitorious.org/mahara/mahara/commit/75a9f3d0d48ee38810485ab94e7ec7e5469cf62f
Submitter: Robert Lyon (robertl@xxxxxxxxxxxxxxx)
Branch:    master

commit 75a9f3d0d48ee38810485ab94e7ec7e5469cf62f
Author: Tobias Zeuch <tobias.zeuch@xxxxxxx>
Date:   Mon Mar 31 17:26:30 2014 +0200

Bug 1298855: new method Plugin::sanity_check() that is called upon install or
update of the plugin. Caught exception InstallException results in the
error-message being presented to the user and the plugin not being installed
while the installation process continues

Change-Id: Iba04bbfebe7b192409cd2e943d7449f0ec258eca
Signed-off-by: Tobias Zeuch <tobias.zeuch@xxxxxxx>

-- 
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/1298855

Title:
  Sanity check for plugin installation

Status in Mahara ePortfolio:
  Fix Committed

Bug description:
  I propose a sanity check for plugins before they are installed automatically with the system installation. Right now, when the installation of a single plugin fails, all plugins that would have been installed thereafter are skipped as well. 
  The problem occurred with a plugin that depends on a artefact type that comes with another plugins, so with the sanity check the dependent plugin can check, if the artefact type was already installed. 
  A sanity check could also be used to check the installation of PHP-extensions or external programs. 
  The sanity check should also be called before a plugin is offered for installation after the core installation.

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