Thursday, May 8, 2025
7 changes · saas-18.2
Resolved issues and error corrections
The Expenses app no longer crashes when its default email alias has been removed. Instead, it opens normally and simply treats the missing alias as unavailable, reducing disruption for users and support teams.
Original PR description
This error occurs when the user deletes the email alias expense `hr_expense.mail_alias_expense`. Steps to Reproduce: 1. Install the module `hr_expense`. 2. Go to Setting > Technical > Email > Aliases and delete `Expense`. 3. Open Expenses. `ValueError: External ID not found in the system: hr_expense.mail_alias_expense` This error occurs when the system is unable to fetch hr_expense.mail_alias_expense ID while opening the module `Expenses`. This commit ensures that if the ID does not exist, the function will return None instead of raising an exception. Sentry: 6559233309
This fix ensures restaurant order course data includes the information needed to load correctly in Point of Sale. It helps avoid loading problems for restaurant workflows, improving reliability without changing user-facing features.
Original PR description
Before this commit, the write_date field was not loaded for restaurant.order.course, which caused issues during the loading. opw-4779831 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The unread conversation dot in the Discuss sidebar is now easier to see when using the dark theme. This helps users notice unread chats more reliably without changing the appearance in the light theme.
Original PR description
When a conversation is unread (and no important messages), the conversation in discuss sidebar has a small dot next to the item. In white theme its visibility is good, with `.opacity-50`. In dark theme however this indicator is hard to see. This commit fixes the issue by keeping 50% opacity in white theme but bumping to 75% in dark theme specifically.
This fix ensures that when work orders are managed through Shop Floor, the correct employee is assigned to the work order. This helps production records stay accurate and avoids confusion in employee tracking for manufacturing operations.
Original PR description
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 fixes a visual issue where the messaging menu's “mark as read” button appeared too wide. The button now has a cleaner, properly sized appearance, making the menu look more polished and consistent.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/203142 PR above made several style improvements, one of which is to make the "mark as read" button on messaging menu item look more like a button: it…
Follow-up of https://github.com/odoo/odoo/pull/203142 PR above made several style improvements, one of which is to make the "mark as read" button on messaging menu item look more like a button: it looks like an icon, now this outline and squared like other buttons. To have a similar size as the counter, it had the `.badge` classname. The `.badge` classname has to do some shenanigans to have constant width for 1-digit values, one of which is to set a minimum width of `2.7ch`. When the "mark as read" button was changed, this become a button but the `.badge` classname was mistakenly kept. As a result, it kept `min-width: 2.7ch`, which made the width too large on this button. `min-width: 2.7ch` should not be used on the same node as `.fa`, as the width of font-awesome glyph is bigger than badge numbers. This commit fixes by removing the `.badge` classname altogether, so the button is sized properly. Another fix could have been to put the `.fa.fa-check` in child-node, but that results in the same visual so removing `.badge` results in simpler template. As the "mark as read" is a button with outline, there's also no longer need to have exact width as a badge. Task-4770926 Before <img width="478" alt="Screenshot 2025-05-05 at 16 55 22" src="https://github.com/user-attachments/assets/dc5ca989-be1d-436e-84e4-57b450f66908" /> After <img width="476" alt="Screenshot 2025-05-05 at 16 54 32" src="https://github.com/user-attachments/assets/06f99cb0-4ab4-4090-80ea-48e71970e80a" />
This update prevents errors in the point of sale when product pricing is checked without a specific product variant. It reads category information from the main product record instead, making product info and pricing screens more reliable.
Original PR description
Before this commit, the parentCategories field was read from the product variant, which could be missing in certain calls. For example, in getProductInfo, the getPrice method is called without a variant, leading to errors. opw-4772883 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when the accounting reconciliation process reads currency amounts from transaction details. It improves reliability for users working with bank or transaction matching by handling the stored data format correctly and avoiding crashes when expected data is missing.
Original PR description
The Issue: Prior to this commit, retrieving the amount currency from the transaction details caused a traceback. This occurred because the transaction details are stored as a jsonb object, and the code attempted to access a string within a dictionary, resulting in a TypeError mismatch. The Fix: The jsonb object is now converted to a string before processing. Additionally, an IndexError is caught to handle cases where the expected group is not found in the match. opw-4754518