Tuesday, May 13, 2025
7 changes · saas-18.3
Resolved issues and error corrections
Creating a new manufacturing operation could fail when no capacity value was available. The fix uses a safe default so users can open and create operations without encountering an error.
Original PR description
Go to the menu Manufacturin / Configuration / Operations (need to enable Work order option), click on new, got a traceback:
...
File "/home/odoo/Documents/dev/odoo/addons/mail/models/mail_thread.py", line 464, in _compute_field_value
return super()._compute_field_value(field)
File "/home/odoo/Documents/dev/odoo/odoo/orm/models.py", line 4623, in _compute_field_value
determine(field.compute, self)
File "/home/odoo/Documents/dev/odoo/odoo/orm/fields.py", line 73, in determine
return needle(*args)
File "/home/odoo/Documents/dev/odoo/addons/mrp/models/mrp_routing.py", line 110, in _compute_time_cycle
operation.cycle_number = float_round(quantity / capacity, precision_digits=0, rounding_method="UP")
ZeroDivisionError: float division by zero
Fix it by adding a fallback with 1 as capacity.
Bug found by adding a test on all form view in https://github.com/odoo/odoo/pull/209587 PR. But need to backport this part.Live chat session screens no longer show the agent's company information. This keeps session views focused on the conversation and avoids displaying unnecessary company details to users.
Original PR description
The agent company should be hidden in every live chat session view. This commit fixes the issue. task-4775840 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
Creating a new manufacturing operation could fail before users entered any details because the system tried to calculate timing with a zero capacity value. The fix uses a safe default capacity so the form opens normally and teams can configure operations without interruption.
Original PR description
Go to the menu Manufacturin / Configuration / Operations (need to enable Work order option), click on new, got a traceback:
...
File "/home/odoo/Documents/dev/odoo/addons/mail/models/mail_thread.py", line 464, in _compute_field_value
return super()._compute_field_value(field)
File "/home/odoo/Documents/dev/odoo/odoo/orm/models.py", line 4623, in _compute_field_value
determine(field.compute, self)
File "/home/odoo/Documents/dev/odoo/odoo/orm/fields.py", line 73, in determine
return needle(*args)
File "/home/odoo/Documents/dev/odoo/addons/mrp/models/mrp_routing.py", line 110, in _compute_time_cycle
operation.cycle_number = float_round(quantity / capacity, precision_digits=0, rounding_method="UP")
ZeroDivisionError: float division by zero
Fix it by adding a fallback with 1 as capacity.
Bug found by adding a test on all form view in https://github.com/odoo/odoo/pull/209587 PR. But need to backport this part.Users can now navigate the custom color picker with the keyboard without triggering an error. If navigation reaches an unavailable color option, the current selection stays focused, keeping text editing uninterrupted.
Original PR description
**Current behaviour before PR:** Steps to reproduce: - Select some text. - Open colorpicker from toolbar, switch to custom colorpicker. - Press tab 3 times to focus a color button. - Pressing ArrowDown twice leads to traceback. The issue happens because in `colorPickerNavigation` method, targetBtn assigns `false` value when row doesn't match the selector. As a result, accessing `targetBtn?.classList.contains` because `false` is not a valid value for optional chaining. **Desired behaviour after PR is merged:** Now, If no valid target button is found, focus remains on the current button and no error occurs. task-4743633 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change removes an unnecessary database index on user settings because an existing uniqueness rule already provides the same database support. It reduces redundant database structures with no expected change for users, helping keep the system cleaner and slightly easier to maintain.
Original PR description
There is already a unique constraint `_unique_user_id` which is implicitly creating an index in the database, no need to index the field. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue that could crash the rental product page when opening products in a new database. This ensures business users can access rental products reliably while default pricing information is prepared.
Original PR description
… for On a virgin DB Go to renting => product Enter studio The kanban of product.template triggers an onchange to get default values Before this commit there was a crash due to a bug in the ORM: the compute of the display_price field did not compute the currency_id id correctly. task to solve the ORM bug: 4264573 solving PR: https://github.com/odoo/odoo/pull/165930 runbot-error-161799
Bank synchronization now uses the correct journal reference when calculating the global summary. This prevents incorrect amounts from appearing after selecting an account, giving users more reliable reconciliation information.
Original PR description
Before this commit, when doing a bank synchronization the active id was the id of the wizard for selecting an account. So the amount on the global summary were wrong no task id