Wednesday, December 31, 2025
5 changes · 18.0
Resolved issues and error corrections
A bug in the TPAR report test was resolved by updating the test to use dynamic dates based on the current user's date. This prevents failures caused by hardcoded dates, ensuring the test runs correctly regardless of the current year and future deployments. This improves test reliability.
Original PR description
Behavior before:
The TPAR report test used hardcoded dates ('2025-01-01' to '2025-12-31'). When running tests with Faketime or on future deployments, this caused failures because the test did not adapt to the current date.
Behavior after:
The test now uses dynamic dates based on `fields.Date.context_today(self.env.user)`. This ensures the test runs correctly regardless of the current year and avoids issues with hardcoded dates.
Root Cause:
Hardcoded dates in the test conflicted with Faketime, causing the test environment to simulate a future year and fail.
Runbot issue: https://runbot.odoo.com/odoo/runbot.build.error/237547
Forward-Port-Of: odoo/enterprise#102960This update resolves an issue where images in image galleries with links were left-aligned instead of centered. The fix ensures images remain correctly centered within gallery links, particularly with smaller images. A CSS adjustment was implemented to address this alignment problem, providing a reliable solution.
Original PR description
Problem: When adding a link to an image in an image gallery, the image becomes left-aligned instead of centered. This issue is most noticeable with images that have a small width. Cause: The image is…
Problem: When adding a link to an image in an image gallery, the image becomes left-aligned instead of centered. This issue is most noticeable with images that have a small width. Cause: The image is centered using the `mx-auto` class. However, when the image is wrapped in an anchor (`<a>`), the anchor does not take up the full width of the container. As a result, the image is no longer centered and shifts to the left. Before: <img width="836" height="586" alt="image" src="https://github.com/user-attachments/assets/f51fed85-727d-4391-a186-8a966f71657a" /> After: <img width="747" height="583" alt="image" src="https://github.com/user-attachments/assets/6a3bd724-5b9c-4160-b0a4-73e8d7fdd1ec" /> Steps to reproduce: - Add an image gallery block. - Replace an image with one that has a small width. - Add a link to the image. - The image is no longer centered and aligns to the left. The issue occurs because the direct parent of the link-image uses `display: flex`. In this commit, a CSS rule was added so that links wrapping an image with Bootstrap margin classes (`mx-auto`, etc.) applied by the image alignment option also get the same margins. This is only done when the direct parent of the link uses `display: flex` which is the case for elements like `carousel-item`. We also targeted parents with the `d-flex` class to fix a similar issue in the `Blockquote` snippet, where the "avatar" image has a `d-flex` parent and becomes misaligned when wrapped in a link. A JavaScript fix was initially considered, by detecting in the image alignment or link application options whether the link’s parent used `display: flex`. That approach would have been more precise to detect a `display: flex` parent, but it wouldn’t cover manually added/moved images. The CSS solution covers all known cases, can still be improved, and has the advantage of working reliably in all situations. opw-4985504 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where refund alerts were triggered incorrectly due to rounding differences between order totals and line item sums. The change ensures accurate comparisons, preventing false alerts and improving the reliability of the Point of Sale (POS) system. This update focuses on a technical fix related to financial reporting accuracy.
Original PR description
Before this commit, if the total amount of the order had rounding differences compared to the sum of its lines, the system could incorrectly trigger an alert stating that the refund amount exceeds the original order amount. This was due to a direct comparison between the two amounts without considering potential rounding issues. opw-5402240
This update corrects a previous issue where warnings from the IoT were incorrectly treated as errors. Now, warnings are displayed as notifications, providing clearer feedback to users about the status of transactions. This improves the user experience and ensures accurate reporting.
Original PR description
Before this commit, all errors returned by the iot after a call to the blackbox were considered as errors. Actually, the errors are only the ones that do not start with 0 (no error) or 1 (warning). This commit changes the behaviour when handling warning. We now show a notification. task-id: 5062178 Forward-Port-Of: odoo/enterprise#93896
This update resolves an error that prevented users from opening the employee form within the Point of Sale (POS) frontend. The fix disables the employee selection field on the frontend only, allowing the form to function correctly in the backend where all necessary data is available. This ensures a smoother user experience for POS operations.
Original PR description
Opening employee form in the frontend was throwing an error, since not all thre required assets were available on the PoS frontend. So in this commit 57aba149b6e6927f9055124e58bed03f842329d5, we disabled openening the employee form by making the employee_id field unclikcable, both in forntend and backend!! It was enough however to only macking it unclikcable on the frontend, since it was working fine on the backend where all the required assets were loaded anyway. This commit restores the functionality on the backend, but overriding the `Many2OneField` used by the `employee_id`, and making it unclickable only on the frontned. opw-5252486