Odoo Changelog — 2025-10-25

Saturday, October 25, 2025

2 changes · 18.0

Bug Fixes(2)

Resolved issues and error corrections

[FIX] industry_fsm_sale: check project is accessible before checking project sharing

Enterprise18.0industry_fsm_sale

Portal users can now open field service task forms they are allowed to see without being blocked by missing access to the related project. The quotations button is shown more safely based on whether the task has linked quotations and whether project access is actually relevant.

Original PR description

Before this commit, the portal user who has access to a fsm task and not the project related could get an access error when he tries to access to the form view of that task inside his portal. The reason is because a check is made to know if the user has access to project sharing to display the quotations button in the portal form view of the task.

This commit makes sure the project is in the parameter of the method in which we did that check to make sure the user comes from a project instead of `/my/tasks` route.

Forward-Port-Of: odoo/enterprise#98023

#portal#field-service#tasks#quotations#access

[FIX] bus: websocket worker incorrectly detects user changes

PR #233052

Core18.0busmailMEDIUM

Fixes an issue where some pages could accidentally make Odoo think the user had changed, causing real-time notification channels to be cleared. Users should now continue receiving their own presence updates reliably across browser tabs and sessions, improving accuracy for online/offline status.

Original PR description

The websocket worker holds a single WebSocket connection per browser. Clients pass the current user ID and DB name, which the worker uses to detect login/logout. Some pages omit the DB name, causing the worker to incorrectly mark the user as changed. This clears previous channels, which may never be added back.

This is particularly noticeable with presence channels: the user's own channel can be lost, preventing them from receiving their own presence updates (e.g. when another browser closes, the user cannot see they are disconnected and cannot correct the value).

The user's own presence channel should be added server-side, so the first subscription immediately returns the user presence and the DB should not be taken into account if ommited.

task-5096212

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#232984

#websocket#presence#notifications

Before this commit, the portal user who has access to a fsm task and not the project related could get an access error when he tries to access to the form view of that task inside his portal. The reason is because a check is made to know if the user has access to project sharing to display the quotations button in the portal form view of the task. This commit makes sure the project is in the parameter of the method in which we did that check to make sure the user comes from a project instead of `/my/tasks` route. Forward-Port-Of: odoo/enterprise#98023

The websocket worker holds a single WebSocket connection per browser. Clients pass the current user ID and DB name, which the worker uses to detect login/logout. Some pages omit the DB name, causing the worker to incorrectly mark the user as changed. This clears previous channels, which may never be added back. This is particularly noticeable with presence channels: the user's own channel can be lost, preventing them from receiving their own presence updates (e.g. when another browser closes, the user cannot see they are disconnected and cannot correct the value). The user's own presence channel should be added server-side, so the first subscription immediately returns the user presence and the DB should not be taken into account if ommited. task-5096212 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#232984