Class Legacy_ModuleInstallAction
- Legacy_Action
- Legacy_ModuleInstallAction
See:
See:
See:
Brief: Module Install function having possibility to extend by module developers. The precondition is that the specified module has been not installed.
Section: cinstall The custom-installer Module developers can use their own custom-installer in this action. Unlike the module update function, the standard installer in this action is perhaps no problems. But, duplicatable modules or some modules with the special framework may need the custom-installer.
Subsection: convention Convention See Legacy_ModuleInstallAction::_getInstaller(). \li $modversion['legacy_installer']['installer']['class'] = {classname}; \li $modversion['legacy_installer']['installer']['namespace'] = {namespace}; (Optional) \li $modversion['legacy_installer']['installer']['filepath'] = {filepath}; (Optional) You must declare your sub-class of Legacy_ModuleInstaller 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']['installer']['class'] = "Installer"; You must declare News_Installer in XOOPS_ROOT_PATH . "/modules/news/admin/class/Installerr.class.php". In the case where you specify the filepath, take care you describe the filepath with absolute path.
Subsection: process Install Process \li Gets a instance of the installer class through Legacy_ModuleInstallAction::_getInstaller(). \li Sets the new XoopsModule built from xoops_version, to the instance. \li Sets a value indicating whether an administrator hopes the force-mode, to the instance. \li Calls executeInstall().
Located at html/modules/legacy/admin/actions/ModuleInstallAction.class.php
Legacy_ModuleInstallAction::_getInstaller()
See:
Legacy_ModuleInstaller
See:
Legacy_ModuleInstallUtils
Brief: Module Install function having possibility to extend by module developers. The precondition is that the specified module has been not installed.
Section: cinstall The custom-installer Module developers can use their own custom-installer in this action. Unlike the module update function, the standard installer in this action is perhaps no problems. But, duplicatable modules or some modules with the special framework may need the custom-installer.
Subsection: convention Convention See Legacy_ModuleInstallAction::_getInstaller(). \li $modversion['legacy_installer']['installer']['class'] = {classname}; \li $modversion['legacy_installer']['installer']['namespace'] = {namespace}; (Optional) \li $modversion['legacy_installer']['installer']['filepath'] = {filepath}; (Optional) You must declare your sub-class of Legacy_ModuleInstaller 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']['installer']['class'] = "Installer"; You must declare News_Installer in XOOPS_ROOT_PATH . "/modules/news/admin/class/Installerr.class.php". In the case where you specify the filepath, take care you describe the filepath with absolute path.
Subsection: process Install Process \li Gets a instance of the installer class through Legacy_ModuleInstallAction::_getInstaller(). \li Sets the new XoopsModule built from xoops_version, to the instance. \li Sets a value indicating whether an administrator hopes the force-mode, to the instance. \li Calls executeInstall().
Located at html/modules/legacy/admin/actions/ModuleInstallAction.class.php
public
|
|
public
|
|
public
&
|
|
public
|
|
public
|
|
public
|
|
public
|
|
public
|
|
public
|
Legacy_Action(),
executeViewError(),
executeViewIndex(),
executeViewPreview(),
hasPermission()
|
public
|
$mInstallSuccess | null |
|
public
|
$mInstallFail | null |
|
public
|
$mXoopsModule | null |
|
public
Legacy_ModuleUinstaller
|
$mInstaller | null |
$_mAdminFlag
|