56dbd6078e
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.) bzr revid: odo@openerp.com-20130429105458-r89mnkx8okdxsdld |
||
|---|---|---|
| .. | ||
| edi | ||
| i18n | ||
| process | ||
| report | ||
| security | ||
| static/src/img | ||
| test | ||
| wizard | ||
| __init__.py | ||
| __openerp__.py | ||
| board_sale_view.xml | ||
| res_config.py | ||
| res_config_view.xml | ||
| res_partner.py | ||
| res_partner_view.xml | ||
| sale.py | ||
| sale_data.xml | ||
| sale_demo.xml | ||
| sale_report.xml | ||
| sale_sequence.xml | ||
| sale_unit_test.xml | ||
| sale_view.xml | ||
| sale_workflow.xml | ||