Daily updates from Odoo
Monday, December 1, 2025
9 changes · 17.0
Resolved issues and error corrections
This update resolves a problem that prevented the Odoo shell from starting correctly, specifically when certain addons with a 'cli' directory were involved. The issue stemmed from incorrectly removing files during git updates, leading to errors. Now, the Odoo shell should start reliably.
Original PR description
Description of the issue/feature this PR addresses: Not all tools imported in addons that have a `cli` directory may be installed on the system when that module is not used. Importing it will result in errors such as missing modules. In case of `hw_drivers`, there are hardcoded paths for the iot box. Current behavior before PR: Failing to start `odoo-bin shell` because of hw_drivers code. Desired behavior after PR is merged: Start commands. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an issue where short feedback messages were incorrectly wrapping the last word, creating a messy layout. The change resolves a conflict between floating rating images and block-level elements, ensuring feedback messages display cleanly and professionally. This improves the overall user experience for rating interactions.
Original PR description
**Current behavior before PR:** - Short feedback wraps the last word unnecessary.  **Desired behavior after PR is merged:** - Short messages wrapped unnecessarily due to block-level element conflicting with floated rating image. This fix ensures cleaner inline layout.  Backport of this: [Commit](https://github.com/odoo/odoo/commit/52a1913ea7082655009c9eca1201c8c42e4e4037) task-[4788428](https://www.odoo.com/odoo/project/1519/tasks/4788428) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where administrators without HR permissions could inadvertently trigger an access error when attempting to create a new employee. The fix hides the 'Create Employee' button for users lacking HR rights, preventing this error and improving system stability. This ensures that only authorized personnel can create employee records.
Original PR description
**Version:** - 17.0 **Steps to reproduce:** - Make sure Marc Demo is an Administrator but has no Employees (HR) access rights. - Log in as Marc Demo. - Go to Settings → Users → Create a new user. - Enter a name and email, then Save. - You’ll see the "Create Employee" button it appears even though the user has no HR rights. - Click it → an Access Error occurs. **Isuue:** - The "Create Employee" button is visible for users who don’t have HR permissions, causing an access error when clicked. **Solution:** - Hide the "Create Employee" button for users without HR access by adding the correct group restriction. task-5212464 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
This update resolves a visual issue within the Odoo Enterprise portal where a badge was incorrectly styled, appearing as a clickable link. This change ensures the badge displays correctly, maintaining a consistent and professional user experience. It's a minor fix addressing a cosmetic problem.
Original PR description
This PR aims to fix issues introduced after the portal redesign. task-3714408 part of task-3703251 - Requires https://github.com/odoo/odoo/pull/152039 ----------- Prior to this PR, there was a badge that was not using the right classes and would then look like a link, misleading the user that could try to click on it. This commit fixes this issue by replicating the design of the other badges
This update resolves an issue where a warning banner appeared during SEPA batch payments when a linked employee had an address. The change ensures the system correctly uses the employee's address instead, preventing the misleading warning. This improves the user experience and data accuracy.
Original PR description
…oyee has an address Doing batch payment for sepa payment would generate a warning banner if the partner has no address ( city and country ) However in reality ( already working ) the xml report will be generated with the linked employee address in the case of absence of the partner address thus it should not show a warning. The change removes the warning in this case. task: 5266346
This update resolves a problem where invoice counters submitted to the Jordanian tax authority (ISTD) were not consistently sequential. The fix utilizes a new calculation to ensure counters are always in order, meeting ISTD requirements and preventing potential export delays. This improves the accuracy and reliability of our Jordan-specific accounting processes.
Original PR description
Before this commit, the invoice counter in the XML submitted to JoFotara was set to the move id. The problem with the move id is that it's not guaranteed that submitted counters would be sequential; they may contain gaps or even be out of order. The ISTD expects counters to be sequential. This commit solves this issue by relying on a computed field in assigning invoice counter in the EDI XML. task-4632768 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where test emails using 'view_online' would fail if the associated mailing contact was deleted. The fix ensures the system retrieves the first available mailing contact ID, preventing errors and improving the reliability of test email generation. This ensures test emails always function correctly.
Original PR description
In the email marketing, when you add "view_online" and dynamic placeholder "object.name", and try doing a test email, it creates a url token for the "view online" with the res_id as the user's id which grabs the record from the mailing_contact with that res_id. So, in case the mailing_contact with the res_id is deleted, the "view_online" gives you error saying record with id "res_id" cannot be find. Our fix is to search the mailing_contact and grab the id of the first record. This fix updates the code from this commit: [8a9981e](https://github.com/odoo/odoo/commit/8a9981e78a438ceb53a4fdc0445ebed2170c6624) opw-5049654
This update fixes a bug where error messages weren't being properly handled during retry attempts, leading to build failures. The change ensures that traceback errors are also caught and processed, resolving a potential instability issue and preventing errors related to websocket connections.
Original PR description
The auto-retry is supposed to catch error logs as well as tracebacks. In some cases a traceback is logged as a message, and not as a logger arg, bypassing the replace already in place. This pr simply replaces the traceback string in the message as well. Build error [234619](https://runbot.odoo.com/odoo/runbot.build.error/234619) Also fixes OSError while handling request paused Build error [229906](https://runbot.odoo.com/odoo/runbot.build.error/229906)
This update resolves an issue where the PEPPOL neutralization script wouldn't process data if the required key was missing. The change ensures the script now correctly inserts the key when it's not initially present, guaranteeing proper data processing for PEPPOL transactions. This improves the reliability of the account integration with PEPPOL.
Original PR description
There can be some siutations where you can not have the key account_peppol.edi.mode while having a connection. But the neutralize only updates and so, if the key is not present, it does nothing. So change it to insert the key if no present --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr