View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005925 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2014-10-22 12:40 | 2023-12-20 15:17 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 4.9.0 / 5.2.0 | ||||
| Summary | 0005925: Template Blocks are not cleared when deactivating module | ||||
| Description | If you have a module with template blocks and deactivate the module, template blocks are still active until /tmp is emptied manually. | ||||
| Steps To Reproduce | To reproduce install attached module, activate and deactivate. | ||||
| Additional Information | Reason is in oxmoduleinstaller::deactivate, template blocks are deleted from database. After this module cache is cleared, but because template blocks have already been deleted, no cache files to delete are found. If the order is reversed and template cache is cleared first, the error is gone. | ||||
| Tags | Template Blocks | ||||
| Attached Files | |||||
| Theme | Azure | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Also, when re-activating a module which got deactivated automatically due to module errors, template blocks in database table oxtplblocks gets duplicated (they are inserted again), because they are not removed on auto deactivation or on re-activating via backend. This gets really annoying in module development. |
|
|
Hello dominik_ziegler, there is already another issue entry regarding your described behavior: https://bugs.oxid-esales.com/view.php?id=6261 [sp] |
