View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007130 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2020-04-25 12:14 | 2020-07-17 13:57 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 6.2.0 | ||||
| Fixed in Version | 6.2.2 | ||||
| Summary | 0007130: composer update changes module state in yaml | ||||
| Description | When running composer update and updating module files, module state is changed in yaml to "false" | ||||
| Steps To Reproduce | 1. Activate module gdpr, module state in yaml is "configured: true" 2. run conposer update and choose "yes" when prompted to overwrite files of gdpr module only 3. Module state in yaml is now "configured: false", in Shop backend it is still active and running | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Looks like the state of the module is falling back to "installed" after you have overwritten the files, which does not sound wrong in the first place. Though the module is marked active by the data in the database it leads to a different state of database and configuration yaml. That's not really good. Luckily I did not encounter any negative sideeffects after the reproduction. To get the correct state in the yaml again, you could click the save button in the administration area. If you noticed any sideeffects, please share the information with us. Thanks for your feedback. Issue is acknowledged. [sp] |
|
|
I think the only case where the setting in the yaml is used, is when the command "vendor/bin/oe-console oe:module:apply-configuration" is used to apply the configuration to the shop, for example in a deployment scenario. |
|
|
The administration area reads the data from the configuration files and saves it to it. Data in the database is only stored, when the module is active and then the frontend reads the data from the database. |
|
|
Looks like this is already resolved here: https://github.com/OXID-eSales/oxideshop_ce/commit/7299ef2b79e3d1b649c0247eedf105e69bffd6e6 Will be included in 6.2.2 |
|
|
fixed according to https://bugs.oxid-esales.com/view.php?id=7130#c13268 |
