1. Mailing Lists
  2. Contributors
  3. Re: New module derived from Odoo CE licensing/credits question

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: New module derived from Odoo CE licensing/credits question

Re: New module derived from Odoo CE licensing/credits question

Avatar

Re: New module derived from Odoo CE licensing/credits question

by
Holger Brunn
- 30/07/2021 18:14:46 
> The code and templates I removed are for product.attribute.category for

> product.attribute to group them. I think I cannot (can I?) disable the code

> so the additional object/table/column will be there. However I would like

> to disable the templates relating to these so they do not confuse the user.

> According to a Google search it can be done in this way:

you can rewrite any qweb template with inheritance before it's evaluated, so 
probably you can have some xpath and change the t-attributes, but


> <record id="full_external_id_of_the_template" model="ir.ui.view">

> <field name="active" eval="False"/>

> </record>

this seems much cleaner to me if it's the intention of this module to undo 
something the other module does entirely.


> If I uninstall my module will the active statu return to its previous state?

> Should I use anything like that or just document in the readme that the

> product.attribute.category is useless while using custom.info?

it doesn't, but you can add an uninstall_hook to your module that sets the 
active flag again.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

Reference