OXID eShop Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004942OXID eShop (all versions)2.3. Extensions (modules, themes)public2013-02-19 08:282015-12-01 10:35
Reporterb.hasis 
PrioritylowSeveritytweakReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version4.6.5 revision 49955 
Target VersionFixed in Version 
Summary0004942: Changing Module ID will move old module(id) to aDiabledModules and let them stay there until the module directory is deleted
DescriptionIf you changing the module id, not the folder too. The old id will moved to aDiabledModules and stays there until the Module Folder is renamed/removed.

Steps To Reproduce-create a module with id "tets".
-activate
-rename the id to "test"
Additional InformationIn my cases the module(with new id) works fine. Its just a little confusing if you find old entries in $aDisabledModules.
TagsNo tags attached.
ThemeNot defined
BrowserAll
PHP VersionNot defined
MySQL VersionNot defined
Attached Files

- Relationships
related to 0005270resolvedmantas.vaitkunas after deactivation still data in db 
parent of 0004129resolvedLinas Kukulskis metadata.php changes are not committed right to aModules 
parent of 0004025resolvedLinas Kukulskis no update of tbl:oxtplblocks by changing module/metadata.php 'blocks' => array() 
has duplicate 0004017resolvedsaulius.stasiukaitis If is renamed module directory, in the shop is displayed cache 
related to 0004866resolvedLinas Kukulskis Start page header element (including CSS) disappear after ruining installed PayPal module. 
related to 0006037acknowledgedflorian.auer deleted plugins remain in "aDisabledModules" which might cause problems later 

-  Notes
(0009354)
martinwegele (developer)
2013-12-11 13:52
edited on: 2013-12-11 13:56

Actually this can become a big problem if you have old entries in aDisabledModules which block the activation of another module. I saw a support case today where "oe" was contained in this array (don't know how it came there) which probably prevented the mobile theme switcher from working correctly. I think the severity of this issue should be increased. Maybe it is worth considering to implement a kind of flushing/cleanup/repair tool for the module-arrays in oxconfig since it is quite difficult to correct them manually (I know that there is a module for debugging).



Copyright © 2015 OXID eSales AG
OXID Logo