Tuesday, January 28, 2025
8 changes · 17.0
Resolved issues and error corrections
This fixes an issue where forum moderators could encounter an error when searching flagged posts if multiple posts matched the search. Moderation filtering now works reliably, helping admins review reported content without interruption.
Original PR description
Since render.qweb was replaced by renderToElement, the spam input search crashes if more than one post meets the search. This commit renders a fragment instead of an element to bypass this limitation.
Steps to reproduce:
- Connect as Admin
- Flag 2 posts on the forum ("..." at the bottom of a post > Flag)
- Go to the flagged posts in the moderation tools (left bar)
- Click on "Filter Tool"
- Select the "Text" tab
- Type "e" (to select both posts) => Traceback.
(No linked task)Customers who choose payment methods that are not confirmed immediately, such as wire transfer, will now still see their order reference on the thank-you page. This makes it easier for customers and support teams to identify and follow up on orders right after checkout.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Enable Wire Transfer as a payment provider; 2. in eCommerce, add an item to cart; 3. go to checkout; 4. pay via wire transfer. Issue ----- The order reference isn't shown below the "Thank you for your order" message because the payment transaction hasn't been approved yet. Solution -------- Show the order reference regardless of transaction status. opw-3844583
Sales order discount descriptions now show rounded percentages instead of long, confusing decimal values. This makes discount lines easier for users and customers to read without changing the actual discount calculation.
Original PR description
## Versions: 17.0+ No fix needed in 16.0 as the discount was not displayed this way. ## Issue: Discount descriptions contain long string floats while it should be truncated for human reading. ## Steps to reproduce: - Activate `Discounts` through settings; - Create a new sale order for any client with at least 1 product; - Click the `Discount` button on the form; - Apply a 7% `Global Discount`; - Read the `Discount` product's description. ## Cause: Some numbers cannot be represented correctly in Python (including 7, 3.3 etc.). opw-4485316
This fixes an issue where the Peppol invoicing integration could show the wrong error behavior because of a missing internal value. Users should now see the intended error message instead of encountering a system error.
Original PR description
Fix the error displayed error. The current code causes a key error. task-no
The point of sale receipt printing fallback now handles unexpected printing errors more cleanly. Users no longer see an confusing "undefined" message, while support teams get console details needed to troubleshoot the issue.
Original PR description
__Current behavior before commit:__ If an unexpected error that has no body is thrown inside `printHtml`, the popup shows "undefinedDo you want to print using the web printer?" and nothing is written in the console, making it impossible to troubleshoot. __Description of the fix:__ Don't print "undefined" in the popup if the error has no body but write the error in the console. opw-4322339
This fixes an error that could occur when merging contacts if custom add-ons added certain reference-style fields to partners. Businesses using customizations can now merge duplicate contacts more reliably without unexpected interruptions.
Original PR description
Description of the issue/feature this PR addresses: Fix a traceback with the partner merging wizard. Current behavior before PR: Currently, the partner merging wizard doesn't support fields of type `reference`, because this type of field is never used by Odoo on model `res.partner`. This will never happend in native Odoo, but some external addons can trigger this traceback. Desired behavior after PR is merged: The traceback is fixed and reference fields are treated like any others field types. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The MRR Evolution dashboard filter has been corrected so it points to the proper subscription plan information. This prevents errors when users edit the dashboard filter in databases where the outdated referenced model is not available.
Original PR description
The `MRR Evolution` dashboard contained a relation filter that would wrongly refer to the model `sale.temporal.recurrence` even tough its field matching pointed towards `sale.subscription.plan`. From a setup POV, the filter was invalid but the only part we use is the field matching, which was correct in itself. The issue came when we wanted to edit the filter in a database which did not have the model `sale.temporal.recurrence`. task-4467133 opw-4432567
This fix corrects dark mode color choices so badges and related interface elements keep the same intended color identity as in light mode. Users get a more consistent visual experience, reducing confusion caused by unexpected color shifts.
Original PR description
This PR fixes an issue about the `$o-color-original` color map values sometimes not matching the light mode one. | //////// | saas-16.3 and above | This PR | |--------|--------|--------| | Light mode…
This PR fixes an issue about the `$o-color-original` color map values sometimes not matching the light mode one. | //////// | saas-16.3 and above | This PR | |--------|--------|--------| | Light mode |  |  | | Dark mode |  |  | When we introduced the redesign of the dark mode with Milk (`saas-16.3`), we fine-tuned the badges design in dark mode by slightly tweaking some colors from the `$o-color-original` map, which contains the colors that will be used on badges (as well as other UI elements). While most of the colors were normally tweaked, some colors received a new hue value, meaning the color would not match the light mode one. As this is inconsistent and unexpected, we review the colors to match the light mode ones. task-4522539