1d91378ce2
When a new inheriting view is imported during a module installation, it is validated thanks to the _constraints on the ir.ui.view model. However the validation uses a rather convoluted system for validating the whole view tree at once (root view + all inherited changes) while only taking into account the views that belong to modules that are currently loaded. This complicated system is necessary to be able to operate on-the-fly at any point during the registry loading/initialization. Now because _constraints are checked during create() this particular validation happens *before* the external ID (ir.model.data entry) of that new view can be created (it obviously needs to wait until the view record is inserted). As a consequence the view validation cannot determine the module to which that new view belongs, and was erroneously ignoring it. Changing the view filtering to also include views that have triggered this check. Manually created views are not check during registry update. bzr revid: chs@openerp.com-20130912141018-qmcyase8zqov9d01 |
||
---|---|---|
.. | ||
__init__.py | ||
expression.py | ||
fields.py | ||
orm.py | ||
osv.py | ||
query.py |