lp:~tsabi/openobject-addons/7.0-account_invoice_ctx_fix

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

9093. By Csaba TOTH on 2013-05-04

update

9092. By Csaba TOTH on 2013-05-04

fix a context usage in the invoice panel

9091. By Launchpad Translations on behalf of openerp on 2013-05-03

Launchpad automatic translations update.

9090. By Launchpad Translations on behalf of openerp on 2013-05-02

Launchpad automatic translations update.

9089. By Launchpad Translations on behalf of openerp on 2013-05-01

Launchpad automatic translations update.

9088. By Thibault Delavallée (OpenERP) on 2013-04-30

[MERGE] [FIX] mail: fixed a change introduced at revision 9080 that introduced a dependance between a revision in web and in addons: now addons revision is independant of the web revision.

9087. By Launchpad Translations on behalf of openerp on 2013-04-30

Launchpad automatic translations update.

9086. By Denis Ledoux (OpenERP) on 2013-04-29

[FIX]plugin: plugin_handler, push_message, if model is res.partner then we set the type to 'comment' instead of 'email' to avoid the behaviour in mail/res_partner.py message_post

9085. By Olivier Dony (Odoo) on 2013-04-29

[FIX] sale: safer inheritance of res.partner form view + no hiding of use_parent_address field

The use_parent_address field is not directly related to the
address type field and was not really meant to be hidden
along with it.

In addition, the div[@name=div_type] and the corresponding
label[@for=type] were duplicated in the embedded form view
inside the `child_ids` field, but that happened later in
the 7.0 series. As a consequence the inherited view must
not rely on the presence of the latter, since some users
may install sales on top of an older version of the base
views. The XPath expressions were therefore modified to
match the first occurrence of these elements in the original
res.partner view, and to match *only* the second occurrence
in the new version of the view.
This works via a dirty hack relying on the fact that
the `use_parent_address` field is present in the first
occurrence of the div in the original view, but not
in the newer view, so the XPath expression can be made
to match only *one* element in each version of the view.
(Keep in mind that XPath evaluation will always return
results in the order of the document being looked up,
and the ORM only uses the first match. So matching
both nodes was not an option.)

9084. By Launchpad Translations on behalf of openerp on 2013-04-29

Launchpad automatic translations update.