x2_many_image

A product in Odoo can carry a gallery: extra photos, and video links that play on the shop page. Those extra media items are child records of the product, and each one shows up as a tile in a kanban subview. x2_many_image is the widget that draws that tile.

It is a thin subclass of the standard image widget. The picture, the sizing options and the zoom behavior are all inherited. What changes is the editing path. Instead of opening your computer's file picker, the pencil button opens Odoo's media dialog, the same one the website editor uses, so an image can be picked from what is already uploaded, and a video can be pasted as a link rather than uploaded as a file.

The second change is the trash button. On the plain image widget it clears the picture and leaves the record. Here it deletes the child record from the parent relation entirely, which is why the widget belongs inside an x2many subview and nowhere else.

The commercial point is the video path. Product galleries that mix photos with a YouTube or Vimeo clip convert better than photos alone, and this widget is what lets a catalog manager add that clip without leaving the product form and without asking anyone to upload a video file. The URL is stored, the platform is recognized, and the shop template does the embedding.

The operational point is reuse. Because the media dialog lists attachments that already exist in the database, the same lifestyle shot can be attached to twenty products without twenty uploads. That keeps the database smaller and keeps a product catalog visually consistent, which matters more than it sounds when several people maintain the same catalog.

The trap to brief your team on is the trash button. On a media tile it does not blank the image, it removes the media record. Users who expect the familiar clear behavior lose the whole gallery entry, including its video URL and its position in the sequence.

The core product media kanban

<field name="product_template_image_ids" mode="kanban">
  <kanban>
    <field name="video_url" invisible="1"/>
    <field name="sequence" widget="handle"/>
    <templates>
      <t t-name="card">
        <field name="image_1920" widget="x2_many_image"/>
      </t>
    </templates>
  </kanban>
</field>

This is the shape core uses. Note video_url loaded invisibly: the widget writes to it by name, so it has to be in the subview.

Sizing the tile

<field name="image_1920" widget="x2_many_image"
       options="{'size': [0, 180], 'img_class': 'w-100'}"/>

size and the undocumented img_class both survive, because they act on the image element the widget does not replace.

A media model that works with it

<!-- the child model needs these field names -->
<field name="name"/>          <!-- overwritten on image save -->
<field name="video_url"/>     <!-- written on video save -->
<field name="image_1920" widget="x2_many_image"/>

Both names are hardcoded in the widget. A custom media model that calls them title and url will render fine and then fail silently on save.

The most useful thing in this file is what the template removes. html_editor.ImageField inherits web.ImageField in primary mode and replaces the first inner div, which in the base template is the container holding the FileUploader component and both control buttons. Three consequences follow, and none of them is documented.

First, there is no file uploader left, so the two options that feed it are inert: accepted_file_extensions, which sets the accept attribute on the hidden input, and convert_to_webp, which is only read inside the uploader's callback.

Second, the base container carries t-if="not props.readonly". The replacement carries no such guard, so the pencil and trash buttons render on a read-only record. They will still open the dialog and still delete the child row.

Third, both buttons are gated on the field having a value. An empty media row therefore shows no controls at all, which is why the core kanban always creates rows through the subview's create action rather than expecting users to click an empty tile.

On the write side, both save paths touch fields the widget names literally. An image save runs a search_read on ir.attachment for datas and name, refuses attachments of URL type with a warning because they carry no datas, then writes the binary into your field and the attachment name into name. A video save builds the platform URL and writes video_url plus a name such as YouTube - [Video].

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and anything below can still change before release; we re-verify this page once Odoo 20 ships.

Two new options appear, and like the rest of this widget's knobs they are read in extractProps without being declared, so tooling will not surface them: set_attachment_id, which stores the chosen attachment's id instead of only its binary, and only_image, which drops the Videos tab and leaves the dialog on Images.

Two behavior changes. The image save path moves to a shared saveSingleAttachment helper, which retires the current refusal of URL-type attachments. And video saves now fetch the platform thumbnail and store it into image_1920, so a video tile stops being a blank card.