View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006037 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2015-02-04 16:32 | 2024-01-17 12:49 |
| Reporter | GhostGambler | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 7.0.0 | ||||
| Summary | 0006037: deleted plugins remain in "aDisabledModules" which might cause problems later | ||||
| Description | Deleted plugins remain as disabled modules in "aDisabledModules" and are never removed from there. This might cause bugs, if one installs a plugin with the same name. We were not able to install a plugin correctly, since even on activation the plugin name was not correctly removed from the aDisabledModules array, although (AFAIK) this should happen on activation to circumvent this issues. In our case it did not (I cannot reproduce this issue right now). Since there is no way to clear the list of disabled modules from the backend, we had to dig really deep into the shop software to find and resolve this issue. I propose two solutions: 1. On opening the extension tab in the backend, clean up all extension related config variables for directories which simply do not exist anymore. This is already done (like the message "There are broken components, should we delete them?"), but obviously this is not enough. 2. For simplicity, please add a button "reset module integration", which executes DELETE FROM oxconfig WHERE OXVARNAME LIKE "a%Module%" and rm -Rf tmp/* This provides an easy way for all others to hardly remove all encoded information concerning module installation. We encountered really a lot of issues with your extensions in the past few days, and both solutions would have helped a lot. You might want to read this blog post too: http://felicitus.org/2014/02/26/rants-for-today/ Someone else encountered at least as much headache as we did. | ||||
| Additional Information | The only way to delete Module entries from oxconfig.aModules, if a module is disabled or deleted, is to delete oxconfig.aModules and aktivate all other modules again | ||||
| Tags | No tags attached. | ||||
| Theme | Azure | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
| related to | 0004942 | closed | Sven Brunk | Changing Module ID will move old module(id) to aDiabledModules and let them stay there until the module directory is deleted |
|
|
or let the module active and delete the files in module folder so you will be asked: Es wurden ungültige Module erkannt. Möchten Sie alle registrierten Modulinformationen und gespeicherten Konfigurationseinstellungen löschen? |
|
|
Since the module chain is now in a file, it is relatively easy to remove it. |
