- Mailing Lists
- Contributors
- Re: New module derived from Odoo CE licensing/credits question
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: New module derived from Odoo CE licensing/credits question
Re: New module derived from Odoo CE licensing/credits question
Re: New module derived from Odoo CE licensing/credits question
> 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
by Holger Brunn - 06:15 - 30 Jul 2021
Reference
-
New module derived from Odoo CE licensing/credits question
Hello, I have modified module website_sale_comparison from Odoo CE into website_sale_custom_info_comparison to work with website_sale_custom_info (based on PR from 9.0 by Jairo Llopis - will create PR for 13.0 soon) which uses product_custom_info. The modifications are really minimal: removed some unneeded code and templates (as these are already present in custom_info), rework of method _prepare_categories_for_display of product.product to work with custom info and slight changes to template displaying the comparison table. So basically it is 90% Odoo code, 10% of modifications. Licensing-vise it should be OK as Odoo is LGPL v3. However my understanding is that original author should be kept there if this was to be included in OCA repository. Any comments on how to do this properly? I mean shoudl I just put Odoo as one of the authors or look up commits to these files in git? Would such module be acceptable for OCA? Any comments are welcome. Best regards Radovan Skolnik
by Radovan Skolnik - 01:21 - 30 Jul 2021