Odoo 20 Website Release Notes

For users

New pages and redirects can use accented URLs that match the page title in languages like French or Spanish.

For developers

The slug and URL helpers in ir_http and website keep non-ASCII letters and apply Unicode normalization instead of stripping accents.

Upgrading from Odoo 19

Existing URLs are not rewritten. Only pages created or renamed after the upgrade get accented URLs.

For users

Shops selling alcohol, tobacco or other age-restricted goods can add an age gate without custom code.

For developers

New snippet s_age_verification_popup built on s_popup, with data-min-age and data-blur-background attributes read by the age_verification_popup interaction.

Upgrading from Odoo 19

Nothing to migrate. Custom age-gate modules can be replaced by this block.

For users

Pages, forms and menus can be built or changed by chatting with the AI Website Assistant inside the editor.

For developers

The assistant is an ai.agent (Website Builder) with ai.skill records whose tools are ir.actions.server records (Create Page, Edit Website Menus, Scrape Website Pages, Set Form Action and others). Custom tools can be added the same way.

Upgrading from Odoo 19

Enterprise only, installed automatically with ai and website. Using it consumes AI credits.

For users

Editors can tell at a glance which blocks were written by the AI assistant.

For developers

AI edits set data-contains-ai-content="true" on the edited block; ir.ui.view allows this root attribute and the OptionsContainer template shows the badge when the element matches it.

Upgrading from Odoo 19

Nothing to migrate.

For users

Key figures such as sales, customers or projects can be shown with a counting animation, anywhere inside a section.

For developers

New snippet s_animated_number with data-start-value and data-end-value, animated by the animated_number interaction.

Upgrading from Odoo 19

Nothing to migrate.

For users

Pick how appointment types are presented to visitors without custom templates.

For developers

The layout is stored as two optional views, website_appointment.opt_appointments_index_cards and opt_appointments_index_pictures; the index template reads them with is_view_active().

Upgrading from Odoo 19

Custom inherits of the appointment index template should be checked against the new card and picture markup.

For users

A site-wide announcement bar can be switched on from the header options without adding a block to every page.

For developers

The banner is the optional view website.option_header_disclaimer (an s_headline block inserted through the website.placeholder_header_disclaimer hook in the layout) toggled by the websiteConfig action.

Upgrading from Odoo 19

Nothing to migrate. Custom header templates should keep the placeholder_header_disclaimer call if they want the option.

For users

Headers placed over the page content can now look like frosted glass instead of a plain semi transparent bar.

For developers

The blur amount is stored as a background-filter style applied through the header template option plugin; it only has a visible effect once the header background color has some transparency and the header overlays content.

Upgrading from Odoo 19

Nothing to migrate. Existing headers keep their current background settings; the Blur control simply appears alongside them.

For users

Visitors browsing a static page automatically get a clickable trail back to its parent pages, with no extra work from the page's own designer.

For developers

page_breadcrumb.js builds the trail from the page's place in the menu tree; a Show Breadcrumb option (breadcrumb_option.xml) toggles the breadcrumb_visible field added to the page record, letting it be hidden per page.

Upgrading from Odoo 19

Nothing to migrate. Existing static pages simply start showing the trail; it can be switched off page by page if it is not wanted.

For users

Individual cards and columns can be given their own shareable in page link, which is useful for long pages and for jumping straight to one card on mobile.

For developers

The button is added by AnchorPlugin.getOptionsContainerTopButtons() for any element matching the anchor_allowed_selectors resource, which addons/website/static/src/builder/plugins/options/card_option_plugin.js extends with ".s_card"; clicking it calls createOrEditAnchorLink(), which sets the element id and copies the link, then shows a confirmation notification with an Edit action.

Upgrading from Odoo 19

Nothing to migrate. This only adds a button; it does not change existing ids or links.

For users

Whole cards can be made clickable without wrapping them in a link, and a card's own image can still get a hover animation the same way any image can.

For developers

Make it clickable is implemented by clickable_card_option_plugin.js adding a .o_card_clickable-ish behavior via the clickable_card.js interaction, separate from AnimateOptionPlugin/ImageHoverPlugin which gate On Hover to <img> elements only.

Upgrading from Odoo 19

Nothing to migrate. Both are opt in controls on top of the existing s_card structure.

For users

Carousel slide transitions can be sped up or slowed down instead of always using the fixed default.

For developers

Duration is a BuilderRange bound to the setCarouselDuration action, saved in milliseconds on the carousel element, and only shown when Transition is Slide or Fade (it has no effect when Transition is None).

Upgrading from Odoo 19

Nothing to migrate. Existing carousels keep their previous fixed transition speed until this is changed.

For users

Color presets can be compared side by side on realistic demo content before picking one for the whole website.

For developers

The eye button lives in the Colors BuilderSlidingPanel's sliding_panel_top_options slot and toggles a Dialog whose body is an iframe of the new /website/theme_colors_preview route.

Upgrading from Odoo 19

Nothing to migrate. This adds a preview only; it does not change how color presets are stored or applied.

For users

Selecting an entire column's text (to copy it, delete it or apply formatting to all of it at once) is now one shortcut instead of a manual click and drag.

For developers

BuilderSelectionRestrictionPlugin listens for control+a on the editable document and stops it from crossing elements matched by its uncrossable_element_selector resource (blockquote, form, div, section, .row by default), which website's own plugin extends for website specific structures.

Upgrading from Odoo 19

Nothing to migrate. This is a new editor only interaction; it does not change stored content.

For users

Connections style shape dividers blend into the page automatically instead of needing their colors adjusted by hand after being added.

For developers

WebsiteBackgroundShapeOptionPlugin calls backgroundShapeOption.handleBgColorUpdated() whenever the element's background changes, which recomputes the shape's color variables from the current background and text colors.

Upgrading from Odoo 19

Nothing to migrate. Shapes already placed are recolored the same way the next time their background is touched; this does not change the shape files themselves.

For users

Visitors can close the cookie notice directly, and the policy link it shows can point at whichever page the company actually uses for its cookie policy.

For developers

The close button is a shared website.cookies_bar.close_button template included by all three bar layouts; the new cookie_policy_id many2one on Website settings is domain restricted to that website's own pages.

Upgrading from Odoo 19

Nothing to migrate. A site that never sets a cookie policy page keeps its previous behaviour.

For users

The countdown timer's title can be repositioned or hidden, and the same countdown options now apply whether it is used as a full block or dropped in as inner content.

For developers

countdown_option.xml now exposes a Title Position row alongside the merged layout and template options that used to be split between the block and inner-content versions.

Upgrading from Odoo 19

Nothing to migrate. Existing countdown blocks keep their current title and layout until these options are changed.

For users

The portal homepage's account cards can be given the site's own colours and spacing instead of always looking like the default theme.

For developers

portal_option.xml registers builder options on .o_portal_index_card > a, which did not exist as an editable target in odoo19; the portal page itself still comes from the portal module's own templates.

Upgrading from Odoo 19

Nothing to migrate. Cards keep their current look until these new options are used.

For users

No direct visual change; pages simply carry extra, predictable classes that a custom stylesheet or script can target.

For developers

portal.frontend_layout now sets classname_from_template from the response_template xmlid (dots replaced with underscores, "o_" prefix) and website.layout adds a second classname_from_mainobject from the page's own URL, both appended to the existing body_classname chain that individual templates used to set entirely by hand.

Upgrading from Odoo 19

Nothing to migrate, but a custom theme that already adds its own body classes with the same names as an auto generated one should check for clashes.

For users

Making a donation now goes through the same checkout steps as buying a product, including whatever billing details the shop already asks for.

For developers

s_donation now posts into website_sale's own cart and checkout controllers (controllers/donation.py) instead of a standalone endpoint; DonationOptionPlugin still manages the block's pre-filled amounts and descriptions from the Style panel.

Upgrading from Odoo 19

A donation page built for the old standalone form should be reviewed after upgrading, since submissions now flow through the shop's checkout instead.

For users

Dragging blocks around the page feels less clunky, with a lighter, striped drop zone instead of a heavy solid highlight.

For developers

The visual styling lives in drop_zone_plugin.edit.scss and builder_overlay.scss; no dropzone_selectors logic changed, only how a drop target and the current selection are drawn.

Upgrading from Odoo 19

Nothing to migrate. This only changes the editor's own visuals, not saved page content.

For users

A form requirement like "must be after today" keeps working correctly however long the form stays live, instead of silently comparing against whatever fixed date was originally typed in.

For developers

BuilderDateTimePicker adds a "Set today as a relative date" button gated by an allowRelativeDate prop, which form_option.xml only passes to a date field's Requirement/Conditions row, not to its plain Default Value row.

Upgrading from Odoo 19

Nothing to migrate. Existing fixed dates on form requirements are left as they are until this is used.

For users

A rotating carousel of recent blog posts (or events, or appointment types) can be added to any page, such as the homepage, not only the module's own listing page.

For developers

s_blog_posts_carousel.xml is a new snippet template with its own dynamic_snippet_blog_posts_carousel_option.js; Events and Appointments (the appointment app, Enterprise) gained equivalent dynamic carousel snippets in the same effort.

Upgrading from Odoo 19

Nothing to migrate. This only adds a new block to drag onto pages.

For users

The Follow us and Share icons on a blog post now look and behave like the Social Media and Share blocks used anywhere else on the site, and can be edited the same way.

For developers

website_blog_templates.xml adds blog_post_content_footer_share_links, an xpath that calls the shared website.s_share snippet into the post, while the old opt_sidebar_blog_index_follow_us view is switched from active to inactive.

Upgrading from Odoo 19

A theme that customized the old hardcoded Follow us block should reapply that customization to the new Social Media snippet instead.

For users

The overall boldness of headings and body text across the whole site can be tuned from one place, including how light and how bold text look when those styles are used.

For developers

theme_font_weight_option.xml adds a Font Weight BuilderSelect per typography level, with nested Light and Bold rows for the font's specific weight values, stored as theme colour/typography CSS variables.

Upgrading from Odoo 19

Nothing to migrate. Existing sites keep their current font weights until this is changed.

For users

Website forms are noticeably more flexible to build: dropdowns can force a real choice, checkboxes and file uploads get their own relevant options, one Labels Position setting covers the whole form, and extra content can be dropped in between fields.

For developers

These are separate rows added across form_option.xml and form_field_option.js (BuilderCheckbox/BuilderSelect/BuilderList entries keyed to the selected field's Type), plus new dropzone_selectors letting .s_website_form_inner_content blocks land inside .s_website_form_field rows.

Upgrading from Odoo 19

Nothing to migrate; existing forms keep their current fields and behave the same until these new options are used on them.

For users

Following an answer someone gave, rather than the whole question, means only getting notified when that specific answer changes or gets a comment.

For developers

forum.post drops the generic mail.thread inheritance it had in odoo19 and gets its own follower_ids/is_follower fields plus a shared website_forum.follow_button template, called on any post with a parent_id (an answer), not only on the question.

Upgrading from Odoo 19

A customization that relied on forum.post being a mail.thread (chatter, generic Followers widget) needs to be checked, since forum posts now use their own lightweight follower model instead.

For users

Any single image on a page can be made to open full size when clicked, not only images placed inside a gallery block.

For developers

image_popup.js is a new interaction bound to img.o_image_popup, added by image_popup_option.xml; the existing Image Gallery lightbox is now also gated by the same class instead of always being active.

Upgrading from Odoo 19

Nothing to migrate. Existing images stay as they are until Pop-up on Click is turned on for them.

For users

The general drop shadow look used by cards and sections across the site can be adjusted site wide instead of being stuck with the theme's fixed default.

For developers

shadow_option.xml exposes the Small/Normal/Large shadow presets as editable Bootstrap shadow classes, with dedicated offset controls, backed by shadow_option_plugin.js.

Upgrading from Odoo 19

Nothing to migrate. Existing shadows keep their current values until these Theme controls are used.

For users

Pasting either a Google Analytics G- id or a Tag Manager GTM- id into the same single Identifier field now loads the correct tracking script automatically.

For developers

website_templates.xml branches on is_google_analytics (key starts with G-) versus is_google_tag_manager (key starts with GTM-) to inject the right snippet, where odoo19 always rendered the gtag.js loader.

Upgrading from Odoo 19

A site already using a GTM- id should confirm Tag Manager now loads correctly, since the injected script changed for that case.

For users

Two more small blocks to drop inside sections: a single icon and an Instagram feed.

For developers

website.s_icon is a new template; website.s_instagram_page is now also registered in the snippet_content (inner content) group, not only as a Social building block.

Upgrading from Odoo 19

No data migration. Existing Instagram sections keep working.

For users

Courses and job offers can be listed with the generic dynamic blocks.

For developers

New website.snippet.filter records and display templates in website_slides and website_hr_recruitment.

Upgrading from Odoo 19

None.

For users

Theme button and link styles are one click away from any button.

For developers

Button style options moved from the link popover to the sidebar (html_builder.ButtonStyleOption) with a goToThemeTab link (.o-hb-theme-tab-link).

Upgrading from Odoo 19

None.

For users

One click gives a QR code image of a tracked link.

For developers

New method link.tracker.action_download_qrcode() returns /report/barcode/QR/<url>?width=500&height=500&download=1; the barcode controller accepts a download flag.

Upgrading from Odoo 19

None.

For users

Site owners can publish an llms.txt file without any code.

For developers

New route /llms.txt in the website controller, new field on website for the content and a transient wizard website.llms (form view_edit_llms) opened by action_open_llms.

Upgrading from Odoo 19

None.

For users

Site owners get a blank mega menu template and can drop any building block, such as Text, Image, Columns or Buttons, inside a mega menu instead of only the old fixed menu-link layouts.

For developers

New Template row in the mega menu Style options (mega_menu_option_plugin.js) lists a new blank template, s_mega_menu_dropzone, next to the existing ones. Picking it drops a plain section that accepts normal blocks.

Upgrading from Odoo 19

Custom code that assumed a mega menu only ever holds the old fixed link snippets should allow for a mega menu section that can contain arbitrary blocks now.

For users

The main search box can be focused on products, events or any other module.

For developers

New website fields header_search_type, header_search_order_by, header_search_limit set by website.set_header_search(); modules declare their scopes through _get_search_scopes(). The searchbar template was refactored (website_search_box_input).

Upgrading from Odoo 19

Custom searchbar templates or overrides of the old header search template must be checked against the refactored template.

For users

Changing the default website no longer needs technical tricks.

For developers

website._ensure_default_website_consistency() keeps the XML id base.default_website pointing at the first website by sequence, id, and copies default-website settings across (_get_settings_to_copy_onto_new_default_website).

Upgrading from Odoo 19

Code that referenced base.default_website expecting a fixed record should read it again after reordering.

For users

Feature lists with icons can be built without custom HTML.

For developers

New template website.s_icon_list (html_editor also got list support for it).

Upgrading from Odoo 19

None.

For users

Install Website Partnership to list partners and members online by level.

For developers

New module website_partnership (depends on partnership, website_partner). Grades use website.published.mixin.

Upgrading from Odoo 19

Code that extended the partner pages in website_crm_partner_assign may have to move to website_partnership.

For users

Customers can change their own avatar without asking you.

For developers

New template portal.profile_picture_card inside portal.portal_my_details and interaction portal_profile_editor.js; the portal controller accepts the uploaded image.

Upgrading from Odoo 19

Custom overrides of portal_my_details should keep the new card or hide it on purpose.

For users

When a form's action creates a res.partner customer or subscribes to a mailing.contact newsletter, a field added to that form can be set to an existing Property defined on that record, not just a plain database field.

For developers

website_form.py resolves properties.field type entries reported by the model so the form builder's Existing Field list mixes real fields with any Properties already defined for that model, and submissions write straight into that property.

Upgrading from Odoo 19

A custom module reading website form submissions should expect a value coming from a property field to land in the record's Properties JSON like any other property, not in a plain column.

For users

Partner pages can be published in bulk instead of one by one.

For developers

New list view partner_pages_tree_view with js_class website_pages_list and action action_partner_pages_list (path partner-pages).

Upgrading from Odoo 19

None.

For users

Fewer useless redirects and less typing.

For developers

website.rewrite: redirect_type default changed from '302' to '301', create() fills name with _generate_name() when empty, new computed is_url_from_exist used by the form alert and a list decoration; widget url_warning_banner_visibility on url_from.

Upgrading from Odoo 19

Scripts that create redirects without a name still work; the name is generated.

For users

Text on a Cover can be moved around like any other column.

For developers

s_cover content is now wrapped in a row/column structure; custom code that targets direct children of .s_cover .container may need an update.

Upgrading from Odoo 19

Existing Cover blocks keep their old markup until they are dropped again.

For users

Typing in the website search bar on a translated page now shows that page's translated name in the results instead of always falling back to the original language's title.

For developers

The search results page groups its results into separate sections per content type (pages, products, blog posts, and so on) with a clearer layout, and the underlying search tolerates small typos or missing words instead of requiring an exact match.

Upgrading from Odoo 19

website_page.py resolves the translated name field for search hits; the searchbar template refactor (search_modal.js, search_more.js, s_searchbar/000.xml) reworks how results render, and mixins.py's fuzzy matching (covered by test_fuzzy.py) widens what counts as a match.

For users

Pages load faster on phones and tablets because the browser picks the right image size on its own, and the SEO dialog can draft its own title, description and keywords.

For developers

image_post_process_plugin.js resizes a saved image into several widths and ir_qweb_fields.py's srcset builder lists them; ai_website's seo_patch.js/xml adds the Update with AI button to the core website SEO dialog, backed by ai_composer.py.

Upgrading from Odoo 19

Filling SEO fields with Update with AI needs the AI app and credits; the dialog's own fields and the image markup are otherwise unchanged, so existing customizations keep working.

For users

Less scrolling in the sidebar: you see the options of what you clicked first.

For developers

OptionsContainer got toggleFold / folded props; the header becomes a button with aria-expanded. Tours or tests that click options of a parent group may need to unfold it first.

Upgrading from Odoo 19

None.

For users

Fewer, clearer settings for Share and Social Media blocks.

For developers

website.SocialMediaOption is registered for the selector '.s_share, .s_social_media'. Icon size is now a range (--oi-icon-size) instead of fa-2x / fa-3x classes.

Upgrading from Odoo 19

Blocks saved with the old fa size classes keep rendering, but custom CSS aimed at fa-* classes should be reviewed.

For users

Adding a social link is just pasting its URL.

For developers

SocialMediaOptionPlugin keeps a socialMediaInfo map (label, icon, extra host regex) and exposes getAssociatedSocialMedia / prefillSocialMediaLinks. Icons use the new oi icon font (data-icon) instead of Font Awesome classes.

Upgrading from Odoo 19

Custom templates that relied on fa-* classes inside s_social_media should be checked.

For users

/sitemap.xml no longer lists pages that would answer with a redirect or an error, only pages that actually return a normal 2XX page, so search engines are not sent to dead links.

For developers

The sitemap-generation code now checks the response status before adding a URL, dropping non-200 entries; the existing per-file limit of 45000 URLs (LOC_PER_SITEMAP in website/controllers/main.py, already present in Odoo 19) still splits large sites into several sitemap files as before.

Upgrading from Odoo 19

Custom controllers that register URLs for the sitemap only need to change something if they were relying on a non-200 URL being listed; the file-splitting behaviour for very large sites is unchanged.

For users

Check how a block looks on phones before dropping it on the page.

For developers

AddSnippetDialog has a new header template with toggleMobilePreview (hotkey M); snippet previews get the o_is_mobile_preview class. Custom snippets may add .preview styles for mobile.

Upgrading from Odoo 19

None.

For users

Every website page now automatically embeds a Schema.org JSON-LD script describing the organization, and pages for blogs, events, forum posts and products add their own structured data (article, event, product, and so on), without any manual setup.

For developers

website/tools.py builds the JSON-LD graph and website/views/website_templates.xml embeds it as a script application/ld+json on every page; models across website_blog, website_event, website_forum and website_sale each contribute their own structured-data fields (for example product SKU).

Upgrading from Odoo 19

Any custom page or theme that overrides the base website layout should keep the structured-data script tag, since removing the base template block would drop SEO markup Google and other search engines can otherwise use for rich results.

For users

Clearer choice of page layout and background.

For developers

theme_tab.xml: Page Layout is a BuilderSelect with image items; Background, Image and Position rows are level-1 rows shown only when the layout is not Full. Themes can also set page options.

Upgrading from Odoo 19

None; existing layout values are kept.

For users

A dropdown field built from Selection options (for example on a contact or newsletter form) shows one small text box per option when translating a page, instead of asking to edit hidden HTML on the option tags.

For developers

The Page URL field on a website page's backend form now has its own EN translate button, the same kind of button other translatable fields use, so a French or Spanish version of a page can live at its own URL.

Upgrading from Odoo 19

An image or video snippet edited on a page can be marked so a different file is shown automatically depending on the visitor's language, instead of everyone seeing the same file regardless of language.

For users

A video block dropped on a page or email can be switched to a tall, portrait shape (like a phone screen) instead of only the classic wide shape, which suits short social-style clips better.

For developers

The video selector dialog (embedded_video_selector.js) that opens when you double-click a video now has a Vertical option alongside Autoplay, Loop and the others; video.js/video.scss apply the matching portrait aspect ratio to the embedded player.

Upgrading from Odoo 19

The video embed is still the same component, just with an extra display option, so existing videos and custom code that reads or writes video embeds keep working.

For users

Nothing to click: pages load with a little less database work when visitors are tracked.

For developers

Page view tracking now goes through a mixin in website/models/mixins.py; models that want their pages tracked can inherit it.

Upgrading from Odoo 19

None.

For users

The website setup wizard now asks for a business type, an industry (matched against a built-in list and its synonyms, with an AI fallback when nothing matches closely) and finally a positioning; the positioning dropdown is filled by an AI request that proposes six options tailored to that exact industry (for example 'artisan' or 'gluten-free' for a bakery) instead of a fixed list.

For developers

After picking a color palette, the wizard shows a grid of visual template previews with real images so the choice feels concrete instead of abstract; on a site with the eCommerce app, this step shows online catalog page styles built the same way.

Upgrading from Odoo 19

configurator.js builds a word-and-synonym dictionary from the industries list and calls /html_editor/generate_text for both the closest-industry match and the six positioning suggestions, falling back to a fixed list of six positionings if that call fails; website_sale's shopPageSelectionScreen.js/xml plugs an extra template-preview step into the same wizard for shop sites.

For users

A cleaner, calmer sidebar while editing pages.

For developers

Builder components in html_builder changed in many places (option containers, color picker, overlay buttons). Custom builder options should be tested against the new layout.

Upgrading from Odoo 19

Retest custom website builder options and tours.

For users

A new building block adds a floating WhatsApp button to a page; visitors click it to open a chat bubble and start a WhatsApp conversation with the configured phone number in one click, similar to a live chat widget.

For developers

The s_whatsapp snippet (000.xml, whatsapp.js) renders the floating button and chat popup, whatsapp_option_plugin.js exposes its settings (phone number, default message, agent name and photo) in the Style tab, and a later commit reworked the popup's visual design.

Upgrading from Odoo 19

The snippet is self-contained and does not touch existing chat or contact-form snippets, so adding it is optional and does not change other blocks.