View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004942 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2013-02-19 08:28 | 2023-11-17 14:52 |
| Reporter | b.hasis | Assigned To | |||
| Priority | low | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.6.5 revision 49955 | ||||
| Fixed in Version | 7.0.0 | ||||
| Summary | 0004942: Changing Module ID will move old module(id) to aDiabledModules and let them stay there until the module directory is deleted | ||||
| Description | If 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 Information | In my cases the module(with new id) works fine. Its just a little confusing if you find old entries in $aDisabledModules. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
| related to | 0005270 | resolved | mantas.vaitkunas | after deactivation still data in db |
| parent of | 0004129 | resolved | Linas Kukulskis | metadata.php changes are not committed right to aModules |
| parent of | 0004025 | resolved | Linas Kukulskis | no update of tbl:oxtplblocks by changing module/metadata.php 'blocks' => array() |
| has duplicate | 0004017 | resolved | saulius.stasiukaitis | If is renamed module directory, in the shop is displayed cache |
| related to | 0004866 | resolved | Linas Kukulskis | Start page header element (including CSS) disappear after ruining installed PayPal module. |
| related to | 0006037 | resolved | florian.auer | deleted plugins remain in "aDisabledModules" which might cause problems later |
|
|
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). |
|
|
Something like this should no longer happen with OXID 7 since there is no longer an aDisabledModules in the database and module directories are no longer copied to the shop |
