web_m2x_options_manager
in web · source on GitHub
Adds an interface to manage the "Create" and "Create and Edit" options for specific models and fields.
Category: Web · Camptocamp · AGPL-3
| Series | Status | Details | Code |
|---|---|---|---|
| 16.0 | ✓Installs | · run 2026-08-21 · 16.0.1.0.0 | on GitHub |
| 17.0 | ✓Installs | · run 2026-08-20 · 17.0.1.0.1 | on GitHub |
| 18.0 | ✓Installs | · run 2026-08-20 · 18.0.1.0.0 | on GitHub |
| 19.0 | ✓Installs | · run 2026-08-19 · 19.0.1.0.0 | on GitHub |
| 20.0 | —Not tested | no branch |
Odoo 20.0 dev — development line
A different statement from the table above. There: the module as published, on a released platform. Here: the module’s code with its manifest version mechanically raised, on a platform that has not been released and changes daily.
| Status | Details |
|---|---|
| ✗fails | The same code installs on 19.0; on the development line it does not. The difference belongs to the platform. (sql_error) · failed in a file of this module: web_m2x_options_manager/tools.py · version 19.0.1.0.0 → 19.5.1.0.0, code unchanged · run 2026-09-10 · odoo 19.5 · modidx/odoo:master-deps-20260910 |
Log excerpt, 20.0 dev
LINE 1: ...LE "ir_model_fields" ADD COLUMN "can_have_options" "boolean"
^
2026-09-10 14:15:40,932 1 WARNING job_77f3be014102 odoo.modules.loading: Transient module states were reset
2026-09-10 14:15:40,933 1 ERROR job_77f3be014102 odoo.registry: Failed to load registry
2026-09-10 14:15:40,934 1 CRITICAL job_77f3be014102 odoo.service.server: Failed to initialize database `job_77f3be014102`.
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 179, in load_module_graph
getattr(py_module, pre_init)(env)
File "/mnt/pool/web_m2x_options_manager/hooks.py", line 10, in pre_init_hook
prepare_column_can_have_options(env.cr)
File "/mnt/pool/web_m2x_options_manager/tools.py", line 10, in prepare_column_can_have_options
create_column(cr, "ir_model_fields", "can_have_options", "boolean")
File "/usr/lib/python3/dist-packages/odoo/tools/sql.py", line 361, in create_column
cr.execute(sql)
File "/usr/lib/python3/dist-packages/odoo/sql_db.py", line 418, in execute
self._obj.execute(query, params)
psycopg2.errors.UndefinedObject: type "boolean" does not exist
LINE 1: ...LE "ir_model_fields" ADD COLUMN "can_have_options" "boolean"
^
2026-09-10 14:15:40,938 1 INFO job_77f3be014102 odoo.service.server.ThreadedServer: Initiating shutdown
2026-09-10 14:15:40,939 1 INFO job_77f3be014102 odoo.service.server.ThreadedServer: Hit CTRL-C again or send a second signal to force the shutdown.
2026-09-10 14:15:40,939 1 INFO job_77f3be014102 odoo.addons.bus.websocket: Disconnecting 0 websockets
2026-09-10 14:15:41,041 1 INFO job_77f3be014102 odoo.sql_db: ConnectionPool(read/write;used=0/count=0/max=64): Closed 1 connectionsProvenance: __manifest__.py sha256 ea9ec2e380a53c4a… · tree of 25 files without the manifest, sha256 852bf8da365c5061…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
Odoo 20.0 — the branch itself
The same frozen code, run again against the real 20.0 branch. The run above used Odoo’s development line before the branch was cut; this one used the branch, pinned to one commit.
| Status | Details |
|---|---|
| ✗fails | The same code installs on 19.0; on the development line it does not. The difference belongs to the platform. (sql_error) · failed in a file of this module: web_m2x_options_manager/tools.py · version 19.0.1.0.0 → 20.0.1.0.0, code unchanged · run 2026-09-18 · odoo 20.0 · modidx/odoo:20.0-deps-20260918 |
Log excerpt, 20.0 dev
LINE 1: ...LE "ir_model_fields" ADD COLUMN "can_have_options" "boolean"
^
2026-09-18 11:12:53,611 1 WARNING job_35bc9790da62 odoo.modules.loading: Transient module states were reset
2026-09-18 11:12:53,613 1 ERROR job_35bc9790da62 odoo.registry: Failed to load registry
2026-09-18 11:12:53,613 1 CRITICAL job_35bc9790da62 odoo.service.server: Failed to initialize database `job_35bc9790da62`.
Traceback (most recent call last):
File "/opt/odoo/odoo/service/server.py", line 1520, in preload_registries
registry = Registry.new(dbname, update_module=update_module, install_modules=config['init'], upgrade_modules=config['update'], reinit_modules=config['reinit'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/tools/func.py", line 67, in locked
return func(inst, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/orm/registry.py", line 222, in new
contextvars.Context().run(
File "/opt/odoo/odoo/modules/loading.py", line 449, in load_modules
load_module_graph(
File "/opt/odoo/odoo/modules/loading.py", line 179, in load_module_graph
getattr(py_module, pre_init)(env)
File "/mnt/pool/web_m2x_options_manager/hooks.py", line 10, in pre_init_hook
prepare_column_can_have_options(env.cr)
File "/mnt/pool/web_m2x_options_manager/tools.py", line 10, in prepare_column_can_have_options
create_column(cr, "ir_model_fields", "can_have_options", "boolean")
File "/opt/odoo/odoo/tools/sql.py", line 361, in create_column
cr.execute(sql)
File "/opt/odoo/odoo/sql_db.py", line 418, in execute
self._obj.execute(query, params)
psycopg2.errors.UndefinedObject: type "boolean" does not exist
LINE 1: ...LE "ir_model_fields" ADD COLUMN "can_have_options" "boolean"
^
2026-09-18 11:12:53,617 1 INFO job_35bc9790da62 odoo.service.server.ThreadedServer: Initiating shutdown
2026-09-18 11:12:53,617 1 INFO job_35bc9790da62 odoo.service.server.ThreadedServer: Hit CTRL-C again or send a second signal to force the shutdown.
2026-09-18 11:12:53,618 1 INFO job_35bc9790da62 odoo.addons.bus.websocket: Disconnecting 0 websockets
2026-09-18 11:12:53,721 1 INFO job_35bc9790da62 odoo.sql_db: ConnectionPool(read/write;used=0/count=0/max=64): Closed 1 connectionsProvenance: __manifest__.py sha256 ea9ec2e380a53c4a… · tree of 25 files without the manifest, sha256 852bf8da365c5061…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
The module’s code on 19.0
| Lines of code | python 750 · xml 218 |
| Tests | yes: 3 file(s), 220 lines |
| Migration scripts | no |
| Models | 1 new · 3 extensions |
| Raw SQL | 2 × cr.execute |
Lines are physical, blanks and comments included, as wc -l. Tests are test_*.py files under tests/. Models are lines holding _name = and _inherit =. These are facts about the code, not a judgement: more lines is neither better nor worse. Measured 2026-08-28 on tree ab68ee816ee6.
The apps.odoo.com catalogue has a listing under the same technical name on 16.0, 17.0, 18.0, 19.0: apps.odoo.com/apps/modules/19.0/web_m2x_options_manager. A matching name does not prove matching code — how we counted this.
Depends on
| Module | Status | Checked |
|---|---|---|
| base_view_inheritance_extension | ✓Installs | 2026-08-19 |
| web_m2x_options | ✓Installs | 2026-09-13 |
History
| Last change | 2026-04-29 |
| Code commits, 12 months | 8 |
| Most active | SilvioC2C, AlexGarS73, daniel-chionne |
| Files | 26 |
Translation and bot commits are excluded from the commit count.
Result looks wrong? Tell us — we will show the log or run it again. Report a wrong result