Adrian Torres
02327d8a6b
This commit adds a warning banner near the bottom of the uninstall wizard warning the user of the consequences of module uninstallation and advising him to try it first on a duplicate database so as to avoid borking the database. The Cancel/Confirm buttons were also swapped and the Cancel one was made primary to avoid mindless "next-clicking" closes odoo/odoo#33396 Task-id: 1824392 Signed-off-by: Raphael Collet (rco) <rco@openerp.com>
62 lines
3.2 KiB
XML
62 lines
3.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data>
|
|
|
|
<record id="view_base_module_uninstall" model="ir.ui.view">
|
|
<field name="name">Uninstall module</field>
|
|
<field name="model">base.module.uninstall</field>
|
|
<field name="arch" type="xml">
|
|
<form string="Uninstall module">
|
|
<field name="module_id" groups="base.group_no_one"/>
|
|
<h3>The following apps will be uninstalled</h3>
|
|
<field name="show_all"/> Show technical modules
|
|
<field name="module_ids" mode="kanban">
|
|
<kanban create="false">
|
|
<field name="icon"/>
|
|
<field name="name"/>
|
|
<field name="shortdesc"/>
|
|
<field name="summary"/>
|
|
<templates>
|
|
<t t-name="kanban-box">
|
|
<div class="oe_module_vignette">
|
|
<img t-attf-src="#{record.icon.value}" alt="Icon"
|
|
class="oe_module_icon" style="width: 60px; height: 60px"/>
|
|
<div class="oe_module_desc" style="padding-left: 70px">
|
|
<h4><field name="shortdesc"/></h4>
|
|
<p class="oe_module_name">
|
|
<t t-if="record.summary.raw_value"><field name="summary"/><br/></t>
|
|
<i><field name="name" groups="base.group_no_one"/></i>
|
|
</p>
|
|
</div>
|
|
</div>
|
|
</t>
|
|
</templates>
|
|
</kanban>
|
|
</field>
|
|
<h3>The following documents will be permanently lost</h3>
|
|
<field name="model_ids" string="Models">
|
|
<tree string="Models">
|
|
<field name="name" string="Document"/>
|
|
<field name="count"/>
|
|
</tree>
|
|
</field>
|
|
<div class="alert alert-warning" role="alert">
|
|
<p>
|
|
Module uninstallation is not always consistent and can sometimes lead to issues,
|
|
some data may be deleted, the database could be left in an unstable state,
|
|
the server could crash, etc. While this is rare, we recommend testing
|
|
the uninstallation procedure on a duplicate database to guarantee that
|
|
it works and then doing it on your production database.
|
|
</p>
|
|
</div>
|
|
<footer>
|
|
<button string="Cancel" class="btn-primary" special="cancel"/>
|
|
<button string="Confirm" class="btn-secondary" type="object" name="action_uninstall"/>
|
|
</footer>
|
|
</form>
|
|
</field>
|
|
</record>
|
|
|
|
</data>
|
|
</odoo>
|