[FIX] tools: do not overwrite view priority on update

In some cases, users change the sequence of base
views in order to have one applied before the other
e.g. when there is two inherited views doing
```
<tree position="inside">
...
</tree>
```
The priority of the views will have an impact on the
fields order in the tree.

On update, the change of priority done by the users
was overwritten, even if the priority of the view
was not defined in the XML code of the view.

The priority of the views should be overwritten only
in the case were the priority of the view
is specifically set in its definition.

opw-688470
This commit is contained in:
Denis Ledoux
2016-09-14 13:09:02 +02:00
parent 5be40868b1
commit 54968d55c2
+2 -1
View File
@@ -741,7 +741,8 @@ form: module.record_id""" % (xml_id,)
record.append(Field(name, name='name'))
record.append(Field(full_tpl_id, name='key'))
record.append(Field("qweb", name='type'))
record.append(Field(el.get('priority', "16"), name='priority'))
if 'priority' in el.attrib:
record.append(Field(el.get('priority'), name='priority'))
if 'inherit_id' in el.attrib:
record.append(Field(name='inherit_id', ref=el.get('inherit_id')))
if 'website_id' in el.attrib: