Odoo Changelog — 2024-11-27

Wednesday, November 27, 2024

3 changes · 18.0

Bug Fixes(3)

Resolved issues and error corrections

[FIX] web_tour: move setupEventActions

Core18.0web_editorweb_tourwebsite

This fixes an issue in automated website editor walkthroughs where actions could lose track of earlier input changes between steps. Keeping the action context consistent from the start makes these tours more reliable and helps prevent false test failures around link editing.

Original PR description

The setupEventActions defines an element (environment) in which the
history of actions is retained. If this element changes at each step
of the tour, then it is for example not possible to "blur" a previously
altered input. This environment must be defined at the beginning of
the tour.

#automated tours#website editor#testing reliability

[FIX] portal: no need to raise when init chatter

PR #188664

Core18.0portal

The portal chatter setup no longer shows an error just because a user cannot access a related discussion at initialization. Access is still checked when messages are actually loaded, reducing false failures while preserving the normal permission checks.

Original PR description

Since the `chatter_init` route is only responsible for checking the valid partner in the case of a public user, there is no need to raise `NotFound` if there is no access to the thread. Checking for access to the thread and raise if
 it's needed is done when fetching the messages.

reported on [this build error](https://runbot.odoo.com/web/#id=99087&menu_id=405&cids=1&model=runbot.build.error&view_type=form)

#portal#chatter#access

[DRAFT][FIX] web_gantt: rangeId not in scales

PR #74677

Enterprise18.0web_gantt

The Gantt view now handles cases where certain time scales, such as month or year, are not available but still selected. This prevents users from seeing a crash and keeps planning views usable with customized configurations.

Original PR description

The attribute scales of the gantt view specifies which scales are available in the view. This means that for instance "year" or "month" can be absent from scales. If that happens and that "year" or "month" is the selected range, a crash occurs when rendering the GanttRendererControls component:
    TypeError: Cannot read properties of undefined (reading 'groupHeaderFormatter')

Here we assign to each range a function groupHeaderFormatter so that we can call it independently from the available scales.

#gantt#planning#stability

The setupEventActions defines an element (environment) in which the history of actions is retained. If this element changes at each step of the tour, then it is for example not possible to "blur" a previously altered input. This environment must be defined at the beginning of the tour.

Since the `chatter_init` route is only responsible for checking the valid partner in the case of a public user, there is no need to raise `NotFound` if there is no access to the thread. Checking for access to the thread and raise if it's needed is done when fetching the messages. reported on [this build error](https://runbot.odoo.com/web/#id=99087&menu_id=405&cids=1&model=runbot.build.error&view_type=form)

The attribute scales of the gantt view specifies which scales are available in the view. This means that for instance "year" or "month" can be absent from scales. If that happens and that "year" or "month" is the selected range, a crash occurs when rendering the GanttRendererControls component: TypeError: Cannot read properties of undefined (reading 'groupHeaderFormatter') Here we assign to each range a function groupHeaderFormatter so that we can call it independently from the available scales.