View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005688 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2014-03-08 12:42 | 2023-12-20 15:35 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Product Version | 4.8.4 / 5.1.4 | ||||
| Summary | 0005688: Module order change does nothing | ||||
| Description | In Backend, module order can be changed and saved, but appearently this does not change inheritance order. | ||||
| Steps To Reproduce | Test modules attached, activate all, try changing module order, changes should be reflected on startpage, but order of execution is always the same. | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Theme | Not defined | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
I suppose that this is because the "module chain" is cached in the tmp folder in the file config.*.amodules.txt. Once you delete that file the correct order is displayed. |
|
|
Thank you for the workaround, then i suggest this file should be deleted automatically when module order is changed. |
|
|
So Module_SortList::save() should at least call oxUtilsObject::getInstance()->resetModuleVars() or oxModule::buildModuleChains() could call oxModule::_resetCache()? |
|
|
Yes something like this, i have not checked in detail. Correct module order is shown right away in backend, so this should be the same with inheritance. |
