Class Legacy_ModuleUninstallAction

See:Legacy_ModuleUninstallAction::_getInstaller()See:Legacy_ModuleUninstallerSee:Legacy_ModuleInstallUtilsBrief:
Module Uninstall function having possibility to extend by module developers. The
precondition is that the specified module has been installed &&
none-actived.Section:
cuninstall The custom-uninstaller Module developers can use their own
custom-uninstaller in this action. Unlike the module update function, the
standard uninstaller in this action is perhaps no problems. But, duplicatable
modules or some modules with the special framework may need the
custom-uninstaller.Subsection:
convention Convention See Legacy_ModuleUninstallAction::_getInstaller(). \li
$modversion['legacy_installer']['uninstaller']['class'] = {classname}; \li
$modversion['legacy_installer']['uninstaller']['namespace'] = {namespace};
(Optional) \li $modversion['legacy_installer']['uninstaller']['filepath'] =
{filepath}; (Optional) You must declare your sub-class of
Legacy_ModuleUninstaller as {namespace}_{classname} in {filepath}. You must
specify classname. Others are decided by the naming convention without your
descriptions. Namespace is ucfirst(dirname). Filepath is
"admin/class/{classname}.class.php". For example, "news" module.
$modversion['legacy_installer']['uninstaller']['class'] = "Uninstaller"; You
must declare News_Uninstaller in XOOPS_ROOT_PATH .
"/modules/news/admin/class/Uninstallerr.class.php". In the case where you
specify the filepath, take care you describe the filepath with absolute path.Subsection:
process Uninstall Process \li Gets a instance of the uninstaller class through
Legacy_ModuleUninstallAction::_getInstaller(). \li Sets the current XoopsModule
to the instance. \li Sets a value indicating whether an administrator hopes the
force-mode, to the instance. \li Calls executeUninstall().Located athtml/modules/legacy/admin/actions/ModuleUninstallAction.class.php