Thursday, March 27, 2025
6 changes · saas-18.2
Resolved issues and error corrections
Changing a password from My Account no longer briefly shows an error before completing. This prevents confusion for logged-in users while keeping the password update flow working as expected.
Original PR description
Scenario: log in > My Account > Connection & Security > change your password Result: The page is reloaded and the password is changed, but before that, there is a traceback with: TypeError: Cannot read properties of null (reading 'disabled') at Signup.onSubmit (/auth_signup/static/src/interactions/signup.js:14) Issue: the signup interaction is also being run on the logged-in password change form (portal.portal_my_security) when it should only be run on login (web.login) or logged-out password reset (auth_signup.reset_password). opw-4671226 **PR note:** with this commit, there is no spinning wheel for the logged in password change. Another possibility could be to also have it (but before 22e777c046521f3f89b62caa5876680beb7f5aba it seems that the SignUpForm was just on the signup form).
This fixes a website editor issue where carousel sections could stay excessively tall after the browser window was narrowed and then restored. Website builders will see more reliable carousel sizing, preventing awkward page layouts during editing.
Original PR description
Steps to reproduce the bug: - Enter website edit mode. -Drag and drop a "Carousel" snippet onto the page. -Strongly reduce the window width to make the carousel's min-height exceed 1000px. - Resize the window back to its original size. - Bug: The carousel height remains too large. Since commit [1], which introduced the bug, the "min-height" of the carousel items was no longer removed before checking their height in the "computeMaxHeight" function. [1]: https://github.com/odoo/odoo/commit/b9b3a605e0f4c5da3a258c980107d6162da7f44f task-4662034
This change restores a missing dependency needed by the IoT display driver after recent display support updates. It helps prevent failures when using connected display hardware in affected Odoo versions.
Original PR description
The PR to add wayland support (#202722) relied on `subprocess` being imported in `DisplayInterface_L`, however in saas-18.2 onwards this was not the case. This commit adds the missing import. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an issue where the link editor could close immediately when adding a link from the full email composer. Users can now select text and add links in modal email windows without the popover disappearing.
Original PR description
**Problem**: When inside a modal (Full Composer), the autofocus hook in the setup of `LinkPopover` does not work as expected. - The active element is set to the modal `<div role="dialog" ...>`, while the input inside the `LinkPopover` is not within the dialog. - As a result, `uiService.activeElement.contains(el)` in `hooks.js:51` returns `false`. - Without a modal, it returns `true` since `activeElement` is `document`. **Solution**: To bypass this issue, manually focus the input without relying on the autofocus hook. **Steps to Reproduce**: 1. Open a **Sale Order**. 2. Click on **Send by Email** to open the **Full Composer**. 3. Add some text. 4. Select the text and click **Link** in the toolbar. - **Issue**: The `LinkPopover` opens and closes immediately because the input was not focused. **opw-4656387** --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an error that appeared when an administrator selected the webhook notification option before choosing a model for a server action. This prevents a disruptive traceback and makes configuration smoother in technical settings.
Original PR description
before this commit, a traceback would be displayed when trying to select 'send webhook notification' before actually selecting a model. Steps to reproduce: 1. enable debug mode 2. go into setting>technical>server action 3. click on 'send webhook notification' 4. traceback
The update fixes an error that prevented users from trying a sample receipt in the Expenses app when demo data was not installed. This restores a smoother first-use experience for expense receipt scanning and avoids a crash from the sample action.
Original PR description
This error occurs when we click on `try a sample receipt` in the Expense module. Steps to reproduce: --- - Install `hr_expense_extract` module(without demo) - Expenses > `try a sample receipt` Traceback: --- ``AttributeError: 'hr.expense' object has no attribute '_default_journal_id'`` At [1], we are encountering this error because the `_default_journal_id` method is defined in `hr.expense.post.wizard`, but we are attempting to access it from `hr.expense`. https://github.com/odoo/enterprise/blob/e10f9aa43ebc4368050c4cb904e81253fc324bdc/hr_expense_extract/wizard/expense_sample_receipt.py#L51 sentry-6362357345