calendar_event_notes_html

Odoo's rich text editor is assembled from plugins. Formatting, lists, links, tables, the slash command menu and the drag handles that let you move a whole block around are each a separate piece, and the field widget decides which ones are loaded.

Meeting notes are written in narrow places: the right hand panel of the calendar, a popover, a form column beside the attendee list. The block move plugin adds a hover affordance to the left of every paragraph, which in a wide document is helpful and in a narrow one is clutter competing with the text.

So this widget is the rich text field with that one plugin filtered out of the configuration. Nothing else is changed, nothing is added, and every other editing feature behaves exactly as it does elsewhere in Odoo.

Meeting notes are one of the few genuinely free-form fields in an ERP, and the temptation is to either lock them down to plain text or leave the full editor in place. Neither is right: people want a bullet list and a link, and they do not want a document editor in a sidebar.

What makes this worth reading is the mechanism rather than the decision. Odoo's editor is trimmable per field, in a supported way, by filtering the plugin list. If a client complains that an editor somewhere is too heavy, the answer is usually a five line widget like this one rather than replacing the field with plain text.

The core usage

<field name="notes" nolabel="1" class="w-100"
       placeholder="Notes"
       widget="calendar_event_notes_html"/>

The placeholder is inherited from the rich text field and works normally, since this widget does not touch the extractor.

Reusing it elsewhere

<field name="internal_notes"
       widget="calendar_event_notes_html"/>

Nothing in it is calendar-specific beyond the name, so any narrow notes field benefits, as long as the calendar module is installed.

The full editor instead

<field name="notes" widget="html"/>

Same editor with the block move handles restored, which is the right choice on a full width form.

The implementation is five meaningful lines. The class extends the rich text field, overrides the method that builds the editor configuration, takes the plugin list the parent returned and filters out one entry by identity, then returns the configuration.

Filtering by identity rather than by name matters: the plugin is imported and compared directly, so a rename in the editor would break the import rather than silently failing to filter. That is the safer of the two failure modes.

Because the override is on the configuration getter, everything else in the parent's configuration survives: the other plugins, the toolbar setup, the collaboration hooks and whatever the base widget derives from the field's own options. A future Odoo version adding a plugin will add it here too, unless it is the one being removed.

Worth being clear about what the removed plugin does, since it is easy to confuse with the slash menu. It is the affordance that appears beside a block on hover and lets you drag that block to a new position. Removing it does not stop users reordering content; it removes the mouse shortcut for doing so.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify the page after release.

Byte-identical. The file on the development branch matches Odoo 19 exactly. Since the widget only filters the parent's plugin list, any change to the editor in Odoo 20 flows through automatically, minus the one removed plugin.