qsm-odoo
1d49b5112b
Unfortunatly needed while another "complex" bug fix is done: xpath validation during module install seems to be done after each view creation. With the upcoming header template refactoring, by mischance, the configurator template validation will not work at install anymore while it is perfectly valid (and the only way to define it) after install: Before future refactoring: 1) install view which adds nav inside X 2) install configurator view, primary view which removes the first nav inside X 3) install view which adds another nav inside X... the nav the configurator wants to remove ! -> Validation of (2) works thanks to (1) during install while (2) wants to remove something that is not installed yet. But (2) is valid it should simply not have been evaluated yet. After future refactoring: We remove step (1) -> (2) has to be done after (3) to pass validation at install while the system is not bug fixed. Part of https://github.com/odoo/odoo/pull/68149 task-2368576 Part-of: odoo/odoo#68149
16 lines
630 B
XML
16 lines
630 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
|
|
<template id="website_configurator" name="Website Configurator" inherit_id="web.frontend_layout" primary="True">
|
|
<xpath expr="//head/t[@t-call-assets][last()]" position="after">
|
|
<t t-call-assets="website.website_configurator_assets_js" lazy_load="True"/>
|
|
</xpath>
|
|
<xpath expr="//t[@t-call-assets='web.assets_frontend']" position="replace">
|
|
<t t-call-assets="website.website_configurator_assets_scss" t-js="false"/>
|
|
</xpath>
|
|
<xpath expr="//nav" position="replace"/>
|
|
<xpath expr="//div[@id='wrapwrap']" position="replace"/>
|
|
</template>
|
|
|
|
</odoo>
|