Denis Ledoux
6ad3d40172
See the explanation here: https://github.com/odoo/odoo/blob/5069c8fd1cee063827873de0f6c2d9fe938337a9/odoo/addons/base/models/ir_ui_view.py#L1209-L1217 The strategy was to create a temporary <t groups="..."> node which gets deleted after the postprocessing. The deletion counted on the fact `groups` was the only attribute set to delete this temporary technical node. In case someone configured manually in a view architecture directly a t node with a groups and something else. But, studio adds another attribute to nodes with "groups=" in the context of the studio edition (`studio=True` in the context) https://github.com/odoo/enterprise/blob/7e66f89e1c85852908edc45e72706e51838960b0/web_studio/models/ir_ui_view.py#L53 and therefore another attribute was added on this temporary technical node, which therefore didn't get deleted properly before being send to the webclient. So, we change the heuristic, instead of relying no the fact `groups` was the only attribute, set a technical attribute on the node to identify it comes directly from the postprocessing and it must be deleted properly before being sent to the webclient. closes odoo/odoo#103832 X-original-commit: 53c684a69bbe8894f05306631272bcf08c226f96 Related: odoo/enterprise#33096 Signed-off-by: Denis Ledoux (dle) <dle@odoo.com>