Daily updates from Odoo
Tuesday, April 8, 2025
15 changes
4 changes
Resolved issues and error corrections
A small issue in the Brazilian electronic invoicing point-of-sale receipt logic was corrected. This prevents an automated testing error and helps ensure receipts continue to display reliably for Brazilian POS users.
Original PR description
In receipt override in l10n_br_edi_pos module we were trying to access config_id from order but the access need to be done through config. runbot error: 162185
This fixes an issue in the Swedish Point of Sale module where receipts checked the wrong source for fiscal device settings. It helps prevent receipt display or validation errors for Swedish POS configurations using fiscal data modules.
Original PR description
Module l10n_se_pos was trying to access to `useBlackBoxSweden` method from the order in the receipt. But since the receipt do not have the order instance, we need to use config.iface_sweden_fiscal_data_module Which is done in the commit. runbot error: 161626
A small typo was corrected in the manufacturing planning code that checks replenishment status. This helps ensure planning information is interpreted consistently and avoids minor errors in the master production schedule.
Original PR description
Typo from 94586ddbf05befe0b202d1efa971a225344f9ef5.
The employee search popup in appraisals no longer shows the Launch Campaign button, preventing users from starting appraisal campaigns from the wrong place. The appraisal employee list now uses the intended view so search results behave consistently.
Original PR description
After this commit, the `Launch Campaign` button is removed from the employee search modal. The newly inherited `view_employee_tree` mode is modified to be `primary` to create a separate list view. Then, the `open_view_employee_list_my` action view is updated with the newly created list view. By default, `Search more...` selects the first available list view if none has a priority, so it now uses the original `view_employee_tree` list view." task-4675979
11 changes
Resolved issues and error corrections
This fix prevents an error when users quickly click a breadcrumb after returning with the browser Back button from a form view. Navigation now remains smooth and reliable, reducing interruptions during everyday work.
Original PR description
Before this commit: When a user opened a form view and clicked browser's Back button, then immediately clicked on the breadcrumb, a traceback occurred. After this commit: Navigation works smoothly without crashes. Task-4667911
This fix prevents an error when a user clears the date while creating a journal entry. Odoo now checks for a date before preparing the placeholder entry name, helping users continue their workflow with clearer handling of missing information.
Original PR description
Description of the issue/feature this PR addresses: When creating a new journal entry, clearing the date field causes an error because the system tries to compute the placeholder name field using the date, which is missing. Current behavior before PR: An error is raised when the date field is cleared while creating a journal entry, as the computation of the name field relies on the date field being present. Desired behavior after PR is merged: The system will check if the date field is present before computing the name field. If the date field is missing, a default value will be used, or a clear validation error will be displayed to the user. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Tax Return screen no longer shows the Print button for journal entries that cannot be printed as PDFs. This prevents users from hitting an error during document layout configuration and makes the reporting workflow clearer.
Original PR description
This error occurs when `o.tax_totals` returns `False`, causing an AttributeError when accessed in the QWeb template. Steps to Reproduce : - Install the module `accountant.` - Go to Reporting and open…
This error occurs when `o.tax_totals` returns `False`, causing an AttributeError when accessed in the QWeb template. Steps to Reproduce : - Install the module `accountant.` - Go to Reporting and open Tax Return. - Open Closing Entry and Print. `AttributeError: 'bool' object has no attribute 'get'` The error occurs when printing the tax report for the first time. The system first attempts to display the document configuration popup for the user based on the account move. However, since `o.tax_totals is not available` in the tax report `(as it is a journal entry)`, and when the user`Configure Document Layout`, it raises a validation error. At [1] we cannot print pdf when `move_type == entry` so it is better to hide `Print` button in this condition. This error is resolved by hiding the `Print` button in the `Tax Return` `Journal Entries`, as it only contains journal items. Link [1] : https://github.com/odoo/odoo/blob/63fc0d1cefaf8f59acd0743a225d1002425ff156/addons/account/models/ir_actions_report.py#L72 sentry-6115648026 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Opening the Set Default Values popup no longer crashes when a record includes hidden fields. This keeps debug tools usable for administrators and support teams without interrupting their workflow.
Original PR description
Problem: When trying to open the "Set Default Values" modal, a traceback occurs if the record contains an invisible field, due to `displayed` being `undefined`. Solution: Safely check the length of `displayed` before using it. Steps to reproduce: 1. Open CRM. 2. Open any record. 3. Enable Debug Mode. 4. Click "Set Default Values". 5. Observe the traceback. opw-4707774 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Printed documents using the Bubble layout now keep long customer names and document titles properly aligned. This prevents invoice titles from being cropped or misplaced, improving the reliability of customer-facing PDFs.
Original PR description
### Steps to reproduce: - Create a contact with a very very long name - Change the layout of documents to "Bubble" - Create an invoice with the new contact - Confirm and Print - The invoice title is unaligned or cropped ### Cause: The layout is using a flexbox to display the contact and the title on the same level. But flex boxes are not supported by whtmltopdf so the result is random. ### Solution: Use a `table` mimicking the flex display. Before:  After:  opw-4653504
When a manager refuses an employee's overtime, the validated extra hours are now reset to zero. This prevents refused overtime from incorrectly appearing as approved time in attendance records and related reporting.
Original PR description
### Steps to reproduce: - Go to settings, set the overtime of an attendance to be validated by a manager - Go to attendance, create an attendance with an overtime - Worked Extra Hours and Extra Hours are the same - Refuse the overtime - Extra Hours is not 0 ### Cause: This is happening because when computing the overtime validated hours we are just setting it equals to the worked extra hours value when the status of the attendance is to_approve but when it got refused we don't re-compute the value. https://github.com/odoo/odoo/blob/0d0c1bc7c075f49a461c66a433e20b431276ff12/addons/hr_attendance/models/hr_attendance.py#L164-L166 ### Fix: We are overriding the value for the validated overtime hours now when it got refused and set it equals to 0 opw-4675268
Chilean PDF invoices using the boxed layout now display total amounts with the same styling as standard invoices. This prevents totals from appearing in hard-to-read black text on colored backgrounds, making invoices clearer for customers and staff.
Original PR description
## Version:
18.0+
## Issue:
PDF invoices in boxed document layout always display a black font for total amount value only for Chile. This black font is not easily readable for most background colors (incl. standard background).
## Steps to reproduce:
- Navigate to the Settings app:
- Under the `Companies` section, configure the document layout: - Ensure the `Boxed` layout is selected;
- Navigate to the Invoicing app:
- Open any invoice record from `Customers / Invoices`;
- Via the `Actions` gear button, print the `PDF without Payment`.
## Cause:
Template inconsistency compared to standard report template: https://github.com/odoo/odoo/blob/3ebd200a76d490ed97bc164e80ed2837fb2f650f/addons/account/views/report_invoice.xml#L443-L450.
opw-4698105
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fixes an issue where some customer invoice pages could fail to display when payment installment information was missing. The invoice template now handles missing installment status safely, improving reliability for portal users viewing invoices.
Original PR description
Previously, when installment_state was None,
the template raised an error because None in ('next', 'overdue') is not a valid operation.
This change ensures safe access to installment_state using .get(), preventing potential errors when
the key is missing or its value is None.
**Description of the issue/feature this PR addresses:**
The invoice template was raising an error when installment_state was None, as the condition None in ('next', 'overdue') is invalid.
**Current behavior before PR:**
If installment_state is None, the template crashes due to an invalid comparison.
**Desired behavior after PR is merged:**
The template now safely retrieves installment_state using .get(), preventing errors when the key is missing or its value is None.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis fixes an issue where some images in emails could appear incorrectly because a common image sizing style was being removed. Emails that rely on fitted images should now render more consistently for recipients.
Original PR description
The 'object-fit' CSS property is currently not whitelisted in the sanitizer, leading to images not being displayed correctly in mails. opw-4655989
Small typo in .po file 'YVotre' => 'Votre' Steps to reproduce: ------------------- * Create an RFQ * Add a vendor with french contact language * Add a vendor reference * Print the pruchase order > Observation: Why the fix: ------------ Typo opw-4677629 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Original PR description
Small typo in .po file 'YVotre' => 'Votre' Steps to reproduce: ------------------- * Create an RFQ * Add a vendor with french contact language * Add a vendor reference * Print the pruchase order > Observation: Why the fix: ------------ Typo opw-4677629 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes the German Intrastat XML report generation by adding a missing supplementary unit code. It helps ensure the report can be generated correctly and reduces the risk of failed compliance reporting exports.
Original PR description
account_intrastat_report.xml: missing SUCode for xml report generation in l10n_de_intrastat build_error-160011