l10n_ro_vat_on_payment

Odoo 20.0 dev — linha de desenvolvimento

Uma afirmação diferente da tabela acima. Lá: o módulo como publicado, sobre uma plataforma já lançada. Aqui: o código do módulo com a versão do manifesto elevada mecanicamente, sobre uma plataforma que não foi lançada e que muda todos os dias.

Trecho do log, 20.0 dev

2026-09-10 23:57:16,541 1 INFO job_05b5952ed9f5 odoo.modules.loading: Loading module l10n_ro_vat_on_payment (54/54)
2026-09-10 23:57:16,847 1 INFO job_05b5952ed9f5 odoo.registry: module l10n_ro_vat_on_payment: creating or updating database tables
2026-09-10 23:57:17,400 1 INFO job_05b5952ed9f5 odoo.modules.loading: loading l10n_ro_vat_on_payment/views/res_partner_view.xml
2026-09-10 23:57:17,854 1 WARNING job_05b5952ed9f5 odoo.modules.loading: Transient module states were reset
2026-09-10 23:57:17,855 1 ERROR job_05b5952ed9f5 odoo.registry: Failed to load registry
2026-09-10 23:57:17,856 1 CRITICAL job_05b5952ed9f5 odoo.service.server: Failed to initialize database `job_05b5952ed9f5`.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/odoo/service/server.py", line 1559, in preload_registries
    registry = Registry.new(dbname, update_module=update_module, install_modules=config['init'], upgrade_modules=config['update'], reinit_modules=config['reinit'])
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/tools/func.py", line 67, in locked
    return func(inst, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/odoo/orm/registry.py", line 222, in new
    contextvars.Context().run(
  File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 446, in load_modules
    load_module_graph(
  File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 211, in load_module_graph
    load_data(env, idref, 'init', kind='data', package=package)
  File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 56, in load_data
    convert_file(env, package.name, filename, idref, mode, noupdate=kind == 'demo')
  File "/usr/lib/python3/dist-packages/odoo/tools/convert.py", line 716, in convert_file
    convert_xml_import(env, module, fp, idref, mode, noupdate)
  File "/usr/lib/python3/dist-packages/odoo/tools/convert.py", line 815, in convert_xml_import
    obj.parse(doc.getroot())
  File "/usr/lib/python3/dist-packages/odoo/tools/convert.py", line 686, in parse
    self._tag_root(de)
  File "/usr/lib/python3/dist-packages/odoo/tools/convert.py", line 639, in _tag_root
    raise ParseError(msg) from None  # Restart with "--log-handler odoo.tools.convert:DEBUG" for complete traceback
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
odoo.tools.convert.ParseError: while parsing /mnt/pool/l10n_ro_vat_on_payment/views/res_partner_view.xml:26
Error while validating view near:

<form string="Partners">
                <div class="alert alert-warning oe_edit_only" role="alert" name="warning_tax" invisible="not same_vat_partner_id">
                    Potential duplicates:

<b>Access Rights Inconsistency</b><br/>This view may not work for all users: some users may have a combination of groups where the elements <b><tt>&lt;button&gt;</tt></b> are displayed, but they depend on the field <b><tt>company_type</tt></b> that is not accessible. You might fix this by modifying user groups to make sure that all users who have access to those elements also have access to the field, typically via group implications. Alternatively, you could adjust the “<i>groups</i>” or “<i>invisible</i>” attributes for these fields, to make sure they are always available together.<br/>Debugging information:<br/>- field “company_type” does not exist in model “res.partner”.<br/>- element “&lt;button name=&#34;check_vat_on_payment&#34; invisible=&#34;vat == False or company_type != &#39;company&#39;&#34; string=&#34;Update VAT on Payment&#34; type=&#34;object&#34; class=&#34;oe_highlight&#34;/&gt;” is shown in the view for groups: &#39;base.group_everyone&#39;

View error context:
{'file': '/mnt/pool/l10n_ro_vat_on_payment/views/res_partner_view.xml',
 'line': 1,
 'name': 'partners_form_add_vat_payment',
 'view': ir.ui.view(969,),
 'view.model': 'res.partner',
 'view.parent': ir.ui.view(955,),
 'xmlid': ''}

2026-09-10 23:57:17,861 1 INFO job_05b5952ed9f5 odoo.service.server.ThreadedServer: Initiating shutdown
2026-09-10 23:57:17,861 1 INFO job_05b5952ed9f5 odoo.service.server.ThreadedServer: Hit CTRL-C again or send a second signal to force the shutdown.
2026-09-10 23:57:17,861 1 INFO job_05b5952ed9f5 odoo.addons.bus.websocket: Disconnecting 0 websockets
2026-09-10 23:57:17,964 1 INFO job_05b5952ed9f5 odoo.sql_db: ConnectionPool(read/write;used=0/count=0/max=64): Closed 1 connections

Procedência: __manifest__.py sha256 9d690bfbaee8cefa… · árvore de 93 arquivos sem o manifesto, sha256 83a5749d51ca01f8…

Isto não diz que o módulo é compatível com o Odoo 20.0, e não diz que ele instala no Odoo 20.0 — em uma plataforma padrão não vai instalar, até que o mantenedor eleve a versão. Por que elevamos a versão