View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007614 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2024-03-07 12:49 | 2024-04-10 15:03 |
| Reporter | SimonGassenschmidt | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Summary | 0007614: Module Configuration Deployment not working like in older version anymore. | ||||
| Description | This issue is connected to this feature: https://docs.oxid-esales.com/developer/en/latest/development/modules_components_themes/project/module_configuration/modules_configuration_deployment.html It let you configure the module settings and configuration in var/configration/enviroment/ - folder and corresponding *.yml. In older version, eg. 6.5 you could also configure properties outside the moduleSettings-Block. Now you can only configure those values. So you cannot overwrite the activated status per enviroment-yaml. In 6.5 you could overwrite the corresponding old variable configurated in those enviroment - yaml. | ||||
| Steps To Reproduce | Install Shop, create path yaml according to above documentation, install module deployment-tools as described. first only change moduleSettings in enviroment-yaml of your chosen module, it should work in OXID 7. try to change activated and run module-console command: it doesn't work. | ||||
| Tags | Documentation | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
reproduced. 1. Install EE 6.5 2. goto admin, have a look at the VCMS module 3. Version 3.6.1 and settings -> frontend -> use own grid is deactivated. 4. create /var/www/oxideshop/var/configuration/environment/1.yaml 5. copy paste: modules:
ddoevisualcms:
version: 1.0.0
moduleSettings:
blCustomGridFramework:
group: frontend
type: bool
value: true6. Look again at the module information in the administration area. Version is 1.0.0 now and the setting is activated.7. Install EE 7.0 8. goto admin, have a look at the VCMS module 9. Version 4.0.2 and settings -> frontend -> use own grid is deactivated. 10. create /var/www/oxideshop/var/configuration/environment/shops/1/modules/ddoevisualcms.yaml 11. copy paste: version: 1.0.0
moduleSettings:
blCustomGridFramework:
group: frontend
type: bool
value: true12. Look again at the module information in the administration area. Version hasn't changed, since anything but moduleSettings is ignored now.It's not clear which behaviour is correct. That from 6.5 or 7.0. It's misleading that the module setting overwritting functionality is on the same page as the how-to-deploy-module-configuration aka Deploying module configuration best-practise: https://docs.oxid-esales.com/developer/en/latest/development/modules_components_themes/project/module_configuration/modules_configuration_deployment.html The Deploying module configuration best practise is of course using parameters like "id" and "activated, but can easily get mistaken with the actual module settings (like blDisableBootstrap for VCMS module). Idea. Split the linked page into two pages: Override Module Settings With Environment Files and Deploy Module Configuration -MK |
