View Issue Details

IDProjectCategoryView StatusLast Update
0007130OXID eShop (all versions)2.3. Extensions (modules, themes)public2020-07-17 13:57
Reporterleofonic Assigned To 
Status resolvedResolutionfixed 
Product Version6.2.0 
Fixed in Version6.2.2 
Summary0007130: composer update changes module state in yaml
DescriptionWhen running composer update and updating module files, module state is changed in yaml to "false"
Steps To Reproduce1. 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
TagsNo tags attached.
ThemeNot defined
BrowserNot defined
PHP VersionNot defined
Database VersionNot defined



2020-04-28 13:04

administrator   ~0013203

Last edited: 2020-04-28 13:04

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.



2020-04-28 14:14

reporter   ~0013204

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.


2020-04-28 15:05

administrator   ~0013205

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.


2020-07-16 15:23

reporter   ~0013268

Looks like this is already resolved here:

Will be included in 6.2.2


2020-07-17 13:56

reporter   ~0013270

fixed according to