lp:~openerp-dev/openobject-server/trunk-bug-1109002-Jay
- Get this branch:
- bzr branch lp:~openerp-dev/openobject-server/trunk-bug-1109002-Jay
Branch merges
Related bugs
Related blueprints
Branch information
Recent revisions
- 4832. By Vo Minh Thu
-
[FIX] ir_model_data: create the _inherits parent external ID prior to the child.
This is needed so the uninstall process can simply go through
the installed data by using the ir_model_data entries in reverse
order (when ordered by IDs), so that parents are deleted before
children. - 4831. By Vo Minh Thu
-
[FIX] safe_eval: better exception handling:
- the re-raising of exceptions ignored the "legal" exceptions
(the one used to early abort RPC calls and generate pop-ups)
- re-raising the exception was attempting to re-use the original
exception type but it does not always take only one argument
so it was breaking. - 4830. By Vo Minh Thu
-
[FIX] ir.actions.action: fix the execute wich install/uninstall modules and thus invalidate its own pool.
- 4829. By Thibault Delavallée (OpenERP)
-
[MERGE] 'Invite & Quick Create User' update. The server branch holds in res_users.create() the support of key in context, allowing to put xml_ids of user groups in the context of relational fields linking to res.users. The purpose of this modification is to quick-create users that will have the access rights related to the functional meaning of the field. For example creating an user in the 'Responsible' field of a task should add him in the group related to project management.
Example of use : <field name="user_id" string="Project Manager" context=
"{'default_ groups_ ref': ['base.group_user', 'project. group_project_ manager' ]}"/> will add Employee (base.group_user) and Project Manager (project. group_project_ manager) groups, as well as implied groups. res_users:
- [add] added support of key in context of default_get. It contains a list of xml_ids of user groups; those groups, if found, are added to the newly created user,
- [ref] refactored simplified (quick create) view that is now more like a contact card, with login and email required because of the login email that will be send to the user - 4826. By Xavier (Open ERP)
-
[FIX] __getattr__ implementation on BaseModel
object has no __getattr__, in the usual case super(BaseModel,
self).__getattr__ will blow up with an AttributeError (but the wrong
one).On the other hand, if a BaseModel descendant class is used in MI
alongside a non-BM descendant (e.g. res_partner inheriting from Model
and format_address) and the non-BM descendant also implements
__getattr__, we want to forward the failed attr search to the other
__getattr__ implementation.So check if super() has a __getattr__, call it if it does otherwise
AttributeError right there.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:openobject-server