View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004003 | OXID eShop (all versions) | 2. ----- eShop backend (admin) ----- | public | 2012-05-06 13:01 | 2012-05-28 09:01 |
| Reporter | WBL_BjoernLange | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Product Version | 4.6.0 revision 44406 | ||||
| Fixed in Version | 4.6.1 revision 45706 | ||||
| Summary | 0004003: Deactivation of modules does not seem to work correctly | ||||
| Description | If you enable and disable a Module in the Shop-Backend, the Extended module files are still a part of the module chain in config var "aModules", even when the Module seems to be disabled. Module_Main::activateModule -> oxModule::activate() saves the module chain in oxConfig::setConfigParam('aModules', $aModules);. But oxModule::deactivate() in Module_Main::deactivateModule() changes only the Tpl-Blocks and the config array "aDisabledModules". | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
This behavior is correct. Deactivated modules should not be removed from aModules array. So you can in Installed modules list which modules are deactivated. There is additional check which checks if module is active and only then it extends core classes. |
|
|
Sry, please close it again. I see the check in oxUtilsObject::_getActiveModuleChain, than this is a sideeffect i have no more insights of yet. |
