modules stay to be installed without user warning
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Server (MOVED TO GITHUB) |
Confirmed
|
Low
|
OpenERP's Framework R&D | ||
Bug Description
If there is an error, after you try installing a module (let's say an XML error), the module stays on state "to be installed", so after that if you set any check to install additional modules on any app, system shows the XML error and all modules you try to install stay on state "to be installed" without any additional warning but the checks stay clicked on configuration.
The only way to avoid the problem is going to modules list and manually cancel the installation of the module giving the error.
I think this should be improved and if a module can not be installed for any reason, that module could stay "to be installed" as it is now but the others going right, should be installed anyway.
If a module can not be installed the check on configuration should be set to False to allow user knowing really what configuration options has really correctly been set or not.
Thank you very much:
Ana
| Andrew (aes) wrote | #1 |
| Changed in openobject-server: | |
| assignee: | nobody → OpenERP's Framework R&D (openerp-dev-framework) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| summary: |
- 7.0 modules stay to be installed without user warning + modules stay to be installed without user warning |
yes, when a module fails to install it is still listed in the "modules to update list".
The behavior should be - If a module fails during installation, all changes should be rolled back and it should be removed from the "modules to update" list.
It makes development of custom modules much more difficult.