I recently bought multiple third party apps we needed for our migration to 18. We come from 17.
Currently we are in the test phase of our migreation (testing our own custom modules etc.)
When I saw the error about still using tree in some of the code, I tought this was in our code, but no, when I checked I saw the shopify_ept and shipping_backbone_ns still use tree in some places.
Is this supposed to work? Can I change them myself or do I have to ask for permission to do so? How can they forget to change certain code to list instead of tree. Because most of their code is using list instead of tree.
Note: I already contacted the authors of the modules, but if I have to wait for an answer this could take some time.
Thanks!
La domanda è stata contrassegnata
3
Risposte
418
Visualizzazioni
Hi,
In Odoo 18, the <tree> tag has been replaced by <list> for list views. If third-party modules still contain <tree> definitions, they may generate warnings or errors depending on the Odoo version and context. If the vendors advertise their modules as compatible with Odoo 18, these view definitions should already have been updated, so the presence of <tree> tags may indicate an incomplete migration.
While you wait for a response from the module authors, you can temporarily update the code in your test environment by replacing <tree> with <list>. In most cases, third-party module licenses allow modifications for your own use, but you should review the license terms before making changes. Keep in mind that simply replacing the tags may not be sufficient, as Odoo 18 includes other view and JavaScript changes that could require additional adjustments.
The recommended approach is to contact the module vendors and request an official Odoo 18-compatible update. This ensures long-term maintainability and prevents your local changes from being overwritten by future module updates.
Hope it helps
Hello,
You can generally update it yourself for your own implementation. In Odoo 18, some view definitions changed from tree to list, so if a third-party module still contains older references, it may trigger errors during migration.
Since most of the module already uses list, this is likely an incomplete Odoo 18 adaptation rather than a major issue. While waiting for the authors to respond, you can review and replace the remaining occurrences carefully and test them in your staging environment before moving to production.
It’s still a good idea to inform the module authors so they can provide an official update and keep future upgrades cleaner.
Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion.
Regards,
Zehntech Technologies Inc.
Hello
Legally and technically: Yes, you can change them right now.
Under OPL-1, you are explicitly allowed to modify the software for your own internal use or for your client's use.
Que: "Have you found <tree> tag in this module, right?"
Hope this helps
Thanks
Ti stai godendo la conversazione? Non leggere soltanto, partecipa anche tu!
Crea un account oggi per scoprire funzionalità esclusive ed entrare a far parte della nostra fantastica community!
Registrati