Odoo Changelog — 2026-01-07

Wednesday, January 7, 2026

45 changes · saas-18.3

Improvements(1)

Enhancements to existing features

[IMP] hw_drivers: normalise logs around actions

Coresaas-18.3hw_driversMEDIUM

This update enhances the longpolling controller by adding detailed logging and performance monitoring. These changes improve system stability and allow our team to quickly identify and address any performance issues related to this critical component. This proactive approach ensures a smoother user experience and more reliable service.

Original PR description

This PR adds logging and performance check for the longpolling controller

Related PR for >= saas-18.3: https://github.com/odoo/odoo/pull/241467

Forward-Port-Of: odoo/odoo#241469

#performance#logging#stability

Bug Fixes(43)

Resolved issues and error corrections

[FIX] l10n_vn_edi_viettel: wrong exchange rate when issue foreign currency invoice

PR #242310

Coresaas-18.3l10n_vn_edi_viettel

This update corrects a bug in the l10n_vn_edi_viettel module that prevented the creation of invoices with very high exchange rates (like those involving USD). The fix rounds exchange rates to two decimal places, aligning with documentation requirements and ensuring invoices can be properly processed. This resolves an issue that could have caused invoice creation failures.

Original PR description

* STEP TO REPRODUCE: create USD invoice to issue sinvoice, have currency
rate like 26337.9186666777 , when issue we will get error because too
many decimal

* SOLUTION: round exchange rate up to 2 decimal because documentation
said that is maximum

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

Forward-Port-Of: odoo/odoo#241061

#currency#invoice#vietnam

[FIX] sign: make search in sign templates work again

PR #102749

Enterprisesaas-18.3signMEDIUM

A bug preventing users from searching within sign templates has been fixed. The issue stemmed from a technical setting that was blocking input into the PDF search box. This update ensures users can now effectively search for content within sign templates, improving workflow efficiency.

Original PR description

Currently when the user is viewing sign templates, they are unable to search within a PDF.

**Steps to replicate:**
* Install `sign` with demo data
* Sign > Templates > Open a template
* Try searching using the magnifying glass button

**Observed Behavior:**
* User is unable to type anything in the PDF search box.

**Root cause:**
* This error happens because `preventDefault()` is called during a `keydown` event. At [1], calling `event.preventDefault()` stops the key’s normal behavior, so the typed character is not added to the input field.

**Solution:**
* Remove the `preventDefault` call which allows the search to work again.

[1]:
https://github.com/odoo/enterprise/blob/3df585779e6ede664279331c4531043688dadf17/sign/static/src/backend_components/editable_pdf_iframe_mixin.js#L623

opw-5366074

#sign templates#search#PDF

[FIX] mail: Fix truncate all related table data

PR #242194

Coresaas-18.3mailMEDIUM

This update resolves an issue where database neutralization unintentionally wiped out user records due to a broad database truncation. The fix now only deletes the 'mail.partner.device' records, preventing data loss during testing and upgrades. This ensures a more stable and predictable database environment.

Original PR description

### Step to reproduce: 1. Create db in version 17.0 and create a many2one field with ``mail.partner.device`` 2. neturalize the db. All records of res.users will be vanish due to ``TRUNCATE…

### Step to reproduce:
1. Create db in version 17.0 and create a many2one field
   with ``mail.partner.device``
2. neturalize the db. All records of res.users will be vanish due to  ``TRUNCATE mail_partner_device CASCADE;``

### Issue: 
during neutralize if there is any custom/studio field many2one with ``mail.partner.device`` even if the mail partner device
record won't used it in particular model still it will wipe out all the records of that model on neutrilizing
which can issue during testing on neutrlized db 

**To fix it :** 
 [here](https://github.com/odoo/odoo/pull/133560/files#diff-284b40b100919f9b1d4f7bee50740387fea5f11815210baa5f6de9cbf317ca6dR14) want to delete only partner device. So, adjusted query using ``DELETE FROM mail_partner_device`` instead of truncate.  

below traceback will generate due to this during upgrade.
```
Traceback (most recent call last):
  File "/home/odoo/bin/misc/update_module_list.py", line 25, in <module>
    env["ir.module.module"].update_list()
  File "<decorator-gen-87>", line 2, in update_list
  File "/home/odoo/src/odoo/17.0/odoo/addons/base/models/ir_module.py", line 71, in check_and_log
    log_data = (method.__name__, self.sudo().mapped('display_name'), user.login, user.id, origin)
  File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 1188, in __get__
    raise MissingError("\n".join([
odoo.exceptions.MissingError: Record does not exist or has been deleted.
(Record: res.users(1,), User: 1)
[ERROR]::Error during the upgrade:
```


opw-5443072
upg-3712726

Forward-Port-Of: odoo/odoo#242081
Forward-Port-Of: odoo/odoo#241535

#database#neutralize#data loss

[FIX] event{,_booth}_sale: prevent traceback when close the select event option

PR #242298

Coresaas-18.3event_salesaleMEDIUM

This update resolves an issue where closing the event registration modal in a sales order would sometimes leave the event product incorrectly attached. The fix ensures that the product is properly removed from the order line when the event selection is dismissed, preventing data inconsistencies. This improves order accuracy and user experience.

Original PR description

**Steps to produce:** - Install `Events and Sales` modules. - Go to `sale > sale order > Open any SO > Add product > Event registration`. - When the wizard opens, dismiss it by either clicking the X…

**Steps to produce:**
- Install `Events and Sales` modules.
- Go to `sale > sale order > Open any SO > Add product > Event registration`.
- When the wizard opens, dismiss it by either clicking the X button in the
  top-right corner of the modal or by pressing the `Escape` key.

**Traceback:**
`TypeError: Cannot convert undefined or null to object.`

**Root cause:**
- In this [commit], the `{ dismiss: true }` option was added to the `dismiss` call.
- At [1], when `onClose` is triggered, we only check `!closeInfo || closeInfo.special`.
 Since `{ dismiss: true }` does not satisfy either condition, the code falls into the `else` branch,
 where `update` is called with an `undefined` value.

**Solution:**
- Now, we also check the condition `closeInfo.dismiss`.
- So, now that we have closed the selection of the event, our product is also removed from the SO line.

[commit]: https://github.com/odoo/odoo/commit/31c00161fd3a77c9fbd260754cb8c142fcb0d652
[1]https://github.com/odoo/odoo/blob/01a896557ec2bada04db60195926c6fa61375b10/addons/event_sale/static/src/js/sale_product_field.js#L40

**opw-5349732**


I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#238061

#sales#events#order management

[FIX] appointment_account_payment: avoid access error when deleting products

PR #103411

Enterprisesaas-18.3appointment_account_payment

This update resolves an issue where deleting 'Booking Fees' products caused an access error. The fix ensures the system can always access these products, regardless of the currently selected company, preventing disruptions to the appointment scheduling process. This improves stability and usability.

Original PR description

**Steps to produce:**
- Install `appointment_account_payment` and `l10n_be` with demo data.
- Go to product `Booking Fees` and assign company `YourCompany`.
- Switch the current company to `Belgium Company`.
- Try to delete any product.

**Issue:**
- An access error is raised when deleting a product.

**Root cause:**
- During product deletion, method `_unlink_except_booking_fee_product_template` is executed [1].
- If the 'Booking Fees' product is assigned to another company, the current company cannot access its record, which triggers an access error.

**Solution:**
- Use `sudo()` when fetching the "Booking Fees" product template so that the record can be accessed regardless of the current company.

[1]: https://github.com/odoo/enterprise/blob/0ba44def7fd961e1c17aa218e1a86a48f0918371/appointment_account_payment/models/product_template.py#L9-L15

opw-5255991
---

Forward-Port-Of: odoo/enterprise#101582

#appointments#products#booking fees

[IMP] account: avoid creating duplicate bank accounts during reconciliation

PR #242426

Coresaas-18.3account

This update simplifies bank reconciliation by preventing the creation of duplicate bank accounts when using the reconciliation widget. It ensures that existing account numbers are not duplicated, reducing confusion and improving data accuracy within the system. This change is specifically focused on the reconciliation process and does not impact other bank account management features.

Original PR description

When using the bank reconciliation widget, avoid creating a new bank
account on the selected partner if the same account number already
exists on another active partner.

This change is intentionally limited to the reconciliation flow only,
to reduce noise caused by duplicate bank accounts, and does not affect
other partner or bank account creation use cases.

task- 5236503

Forward-Port-Of: odoo/odoo#234531

#bank reconciliation#accounts#duplicate accounts

[FIX] l10n_tw_edi_ecpay: exclude company name in EDI address

PR #242180

Coresaas-18.3l10n_tw_edi_ecpay

This update corrects an issue with how Odoo sends electronic invoices to the Taiwanese tax authority (ECPay). The change removes the company name from the EDI address and formats the address as a comma-separated line, ensuring compliance with tax regulations. This ensures accurate and timely invoice submissions, avoiding potential delays or errors.

Original PR description

In this commit:
---
Update EDI address formatting to remove the company name and send a comma-separated single-line address.


task-5410619

Forward-Port-Of: odoo/odoo#241964
Forward-Port-Of: odoo/odoo#241108

#Taiwan#EDI#Tax#ECpay

[FIX] web: Mock call to Odoo Fin favorite institution

PR #223680

Coresaas-18.3web

This update ensures that the accounting application doesn't automatically contact our external Odoo Fin server when opened. Previously, displaying favorite institutions in the accounting dashboard triggered a call to production.odoofin.com. This fix uses a mock to prevent unnecessary external requests, improving efficiency and reducing potential load on the Odoo Fin service.

Original PR description

The aim of this commit is making sure that the click all won't try to contact our external server odoo fin when the accounting application is opened. Indeed, the accounting application is displaying the favorite institutions for a particular country in the accounting dashboard which is doing a call to production.odoofin.com.

This commit adds a mock using _request_handler to patch the call to odoo fin.

runbot-error-231151


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#223602

#accounting#fin#performance

[FIX] mail: avoid error on service worker push subscription change

PR #242374

Coresaas-18.3mailMEDIUM

This update fixes a bug that occurred when push notifications were re-enabled, preventing errors in the service worker. It also enhances the system's ability to handle invalid push notification endpoints, specifically those using the `.invalid` top-level domain, ensuring notifications continue to function correctly.

Original PR description

[FIX] mail: avoid error on service worker push subscription change Sometimes, the `pushsubscriptionchange` event is called without an `oldSubscription` defined, which can lead to an error occurring…

[FIX] mail: avoid error on service worker push subscription change

Sometimes, the `pushsubscriptionchange` event is called without an
`oldSubscription` defined, which can lead to an error occurring inside
the  service worker.

Steps to reproduce:

1. Enable notification in Odoo.
2. Reset the permission in the Chrome interface
3. Re-enable the permission inside the discuss systray by clicking on
the Odoobot message.
=> The pushsubscriptionchange is called without an oldSubscription


[FIX] mail: ir_cron_web_push_notification are now more robust

With a user having 5 registered devices for push notifications
if a browser registers with an endpoint that has a wrong domain
such as https://permanently-removed.invalid/fcm/send/XXXXXXXXXXXXX
the cron job cannot resolve the invalid domain of the endpoint and ends
up disabling it.


[FIX] mail: push_to_end_point method to support .invalid TLD

if a browser registers with an endpoint that has a TLD `.invalid`
such as https://permanently-removed.invalid/fcm/send/XXXXXXXXXXXXX

The TLD `.invalid`[1] is intended for use in online construction of
domain names that are sure to be invalid and which it is obvious at a
glance are invalid. The cron job cannot resolve the invalid domain of
the endpoint and ends up disabling it.

So we need to unregister a device with an endpoint with a `.invalid`
TLD.

[1]: https://datatracker.ietf.org/doc/html/rfc2606#section-2


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#242013
Forward-Port-Of: odoo/odoo#240502

#push notifications#reliability#mobile

[FIX] point_of_sale: fit longer language in optional button

PR #240698

Coresaas-18.3point_of_sale

This update fixes an issue where the "Add" button in the Point of Sale (PoS) interface was cut off when using the German language due to long translations. The fix increased the button's width to accommodate longer words, ensuring the button remains fully visible and readable for all users.

Original PR description

**Steps to reproduce:**
- Make a product that has some optional products
- Switch the language to German
- Open the PoS and order the product
- The "+ Add" button will be cut and not shown correctly

**Why the fix:**
Whenever the translation for "Add" was too long, it didn't fit in the button anymore and was unreadable. We now changed the width of the button to be flexible as to accept longer words.

opw-5385398

#optional#pos#language

[FIX] l10n_fr_hr_holidays: missing default reference leave type in setting

PR #242390

Coresaas-18.3l10n_fr_hr_holidays

This update resolves a validation error that occurred when creating new leave requests in the l10n_fr_hr_holidays module. The issue stemmed from incorrect default settings in the company's time off configuration, specifically a missing reference to the correct leave type. This change ensures proper validation and functionality for new leave requests.

Original PR description

**Steps to reproduce:**
- Install l10n_fr_hr_holidays module.
- Go to Time Off > Configuration > Settings.
- Company Paid Time Off field should blank.
- Employee `resource_calendar_id` is not same as company's.
- Create new leave > a validation error will occur.

**Cause:**
- The demo data for 'res.company' did not correctly set the `l10n_fr_reference_leave_type` field.
- 'l10n_fr_reference_leave_type' field should be required.

**Fix:**
- Updated demo record to correctly assign `l10n_fr_reference_leave_type` field.
- Set the `l10n_fr_reference_leave_type` field as required.

Task - 5139488

Forward-Port-Of: odoo/odoo#231385

#time off#holidays#configuration

[FIX] l10n_hr_edi: KPD category ID error fix

PR #242353

Coresaas-18.3l10n_hr_edi

This update resolves a problem preventing the correct display of KPD category lists within the HR module. The fix aligns the module's functionality with the latest version (19.0), ensuring accurate reporting and data processing related to KPD categories. This improves the reliability of HR data.

Original PR description

Fixing the loading error for KPD category list, consistent with 19.0 version of the module.
runbot-237639

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#242188

#HR#KPD#Categories

[FIX] html_editor: clear image styles on media replace

PR #240284

Coresaas-18.3html_editor

This update resolves a bug where image styles (like width and transform) were incorrectly applied to new media types after an image was replaced. Now, styles are properly removed when switching between image and other media types, ensuring consistent formatting within the HTML editor.

Original PR description

**Current behavior before PR:**

- When an image had styles applied to it (such as transform or width) and was replaced with another  media type like an icon or document, those styles were incorrectly carried over to the replaced media.

**Desired behavior after PR is merged:**

- Since transform and width styles are meant to apply only to images, they are now removed when an image is replaced with other media types.

task-5373362

Forward-Port-Of: odoo/odoo#238319

#html_editor#image#formatting

[FIX] website: fix appearance issue of carousel with indicators outside

PR #242306

Coresaas-18.3website

This update corrects a visual issue with the carousel's indicators, specifically when using 'Numbers' as the indicator style. The previous design resulted in unreadable numbers and misaligned buttons. This fix ensures the indicators are correctly sized and colored, improving the overall user experience.

Original PR description

The css rules for indicators outside the carousel were not adapted for number indicators, and used the button color intended for dots and bar as background of the numbers, making them unreadable and…

The css rules for indicators outside the carousel were not adapted for number indicators, and used the button color intended for dots and bar as background of the numbers, making them unreadable and ugly.

The height of the indicators when outside influences the margin needed to align the bottom of the prev/next buttons. That caused the bottom of the next/prev buttons to not reach the bottom of the slide with "Numbers" or "Hidden" as indicators.

This commit adds the necessary css rules to correctly size and colors the number indicators (and the hidden one) when positioned outside.

Steps to reproduce
- Add a carousel
- Set "Indicators" to "Numbers"
- Set "Style" to "Indicators outside"
- Bug: The colors are all wrong, we cannot see the numbers
- Bug: The bottom of the previous/next buttons do not reach the bottom of the carousel
- Set "Indicators" to "Hidden"
- Bug: The bottom of the previous/next buttons is even further from the bottom of the carousel

task- 5358507

Forward-Port-Of: odoo/odoo#237397

#UI#Appearance#Carousel

[FIX] {website_,}sale_subscription: hide archived recurring plans on website

PR #103428

Enterprisesaas-18.3website_salesale_subscription

This update corrects a display issue where archived recurring plans continued to show up on the website product pages. The fix ensures that pricing is only displayed for active plans, improving the user experience and preventing outdated information from being shown. This improves the accuracy of product pricing displayed to customers.

Original PR description

**Steps to produce:** - Install `sale_subscription,website_sale` module. - `Subscription > Configuration > Recurring Plans`. - `Archive` the `Monthly` plan. - Go to website > Shop > Open product `Car…

**Steps to produce:**
- Install `sale_subscription,website_sale` module.
- `Subscription > Configuration > Recurring Plans`.
- `Archive` the `Monthly` plan.
- Go to website > Shop > Open product `Car Leasing (SUB)`.

**Issue:**
- Even after archiving the Monthly recurring plan, its pricing still appears on the website product page.

**Root cause:**
- At [1], when searching for a suitable recurring price, the system does not filter out pricing records belonging to archived recurring plans.
- As a result, inactive plans are still considered during pricing selection.

**Solution:**
- In this fix, we ensure that recurring plan pricing is included only if the related plan is active.
- Archived plans are now ignored, preventing them from appearing on the website.

[1]: https://github.com/odoo/enterprise/blob/25edaac85f8fd1699bb78163b01efb966e7fb680/sale_subscription/models/sale_subscription_pricing.py#L78-L79

before
<img width="340" height="184" alt="recurring_plan_before" src="https://github.com/user-attachments/assets/abac39fb-5765-4bc4-aec3-87eef7135a18" />

after
<img width="337" height="168" alt="recurring_plan_after" src="https://github.com/user-attachments/assets/35ee92e8-e66b-4612-add3-58b277560ea5" />

**opw-5266333**

Forward-Port-Of: odoo/enterprise#103223
Forward-Port-Of: odoo/enterprise#100587

#recurring plans#website#pricing

[FIX] social{_crm}: fix double post dropdown

PR #103409

Enterprisesaas-18.3socialsocial_crm

This update resolves a duplication issue in the stream post dropdown menu, ensuring a consistent user experience across the 'social' and 'social_crm' modules. The fix also restores a key functionality related to button visibility for user-owned posts, maintaining proper editing and deletion controls.

Original PR description

Following https://github.com/odoo/enterprise/commit/c9ddf1c a new dropdown has been added to "social"
to allow the edition and deletion of a social stream post.
This new dropdown didn't take into account the one already existing in "social_crm"
resulting in a duplicated dropdown menu.

Fixing the issue by making sure the dropdown from "social_crm" is correctly
extending the one from "social".

As the "Create Lead" action is set above the "Edit" and "Delete" ones, making sure
it's also the case for the stream post comments dropdown menu for consistency.

Re-inserting the "is_author" field (removed here https://github.com/odoo/enterprise/pull/69650) in the kanban view to make sure
the "Edit", "Delete" and "Create Lead" buttons visibility are correctly managed
for your own posts.

Task-5270180

Forward-Port-Of: odoo/enterprise#101679

#UI#stream posts#consistency

[FIX] web: hadle empty data when exporting pivot xlsx

PR #242379

Coresaas-18.3web

This update resolves an issue where the pivot table export feature would fail when no data was provided. The system now returns a standard error message (422) to indicate invalid data, ensuring a smoother user experience and preventing unexpected errors during data exports.

Original PR description

Currently an exception is generated when controlled `/web/pivot/export_xlsx'
tries to export xlsx with empty data.

`KeyError: 'title'`

This PR resolves the issue by raising an `UnprocessableEntity` exception
when empty data is provided. The resulting 422 response indicates that
the server understood the request and its syntax, but cannot process it
because the data is invalid.


sentry-6321555617

Forward-Port-Of: odoo/odoo#241415

#export#data#error handling

[FIX] pos_restaurant: floating order name not good

PR #242359

Coresaas-18.3pos_restaurant

This update fixes an issue where the floating order name in the restaurant POS system was incorrectly showing the POS reference instead of the tracking number. Now, the order name accurately reflects the tracking number, ensuring correct order identification and management for restaurant staff. This improves order clarity and accuracy.

Original PR description

Before this commit, when making a direct sale, the floating order name was the pos reference instead of the tracking number. This is now fixed.

task-id: 5470874

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#POS#Order Management#Restaurant

[FIX] appointment_hr_recruitment: fix traceback when moving applicant

PR #100648

Enterprisesaas-18.3appointment_hr_recruitment

This update resolves an issue where recruitment officers couldn't move applicants to the qualified stage, causing errors in email notifications. The fix utilizes a temporary workaround to bypass access restrictions, ensuring that recruitment staff can correctly update applicant statuses without generating errors.

Original PR description

Problem:
Recruitment officers don't have the rights to create `appointment.type` nor `appointment.interview`, Hence when they move an applicant to the qualified stage an error is raised during the rendering the body of the qweb mail template.

Fix:
Override the controller to use sudo and pybass the access check.

Task-5262936

#recruitment#applicant#qualification#email

[PERF] account_edi_format: Speedup product search

PR #241206

Coresaas-18.3accountMEDIUM

This update significantly speeds up product searches used in EDI processing, particularly for large invoice imports like those from PEPPOL. By restructuring the database query, the system now utilizes indexes more effectively, dramatically reducing processing times from over 8 minutes to just a few seconds.

Original PR description

The \_retrieve \_product() function relies on a query with multiple domains OR'ed together. As the search will require a LEFT JOIN with the product_template table, the use of OR in the query prevents…

The \_retrieve \_product() function relies on a query with multiple domains OR'ed together. As the search will require a LEFT JOIN with the product_template table, the use of OR in the query prevents Postgres from utilizing indexes. This becomes a problem in databases with a large number of products since a seq scan would be very slow.

This commit changes the way this is done by performing separate queries instead of a single query with multiple conditions within an OR statement. Although this might seem a performance degradation, it actually allows these separate queries to utilize indexes and run much faster compared to the original approach. It also simplifies the priority logic and allows for faster early exits compared to the original one.

This function is mainly used with EDI crons (such as PEPPOL where this problem was noticed), which could require hundreds of product searches as it does a search per invoice line.

Benchmarks:

Importing a peppol document of 173 invoice lines.

| Num products | Num invoice lines | Before   | After   |
| ------------ | ----------------- | -------- | ------- |
| 864873       | 173               | 868.18 s | 19.43 s |
| 397005       | 173               | 468.91 s | 20.68 s |
| 8064         | 173               | 125.08 s | 20.1 s  |
| 564          | 173               | 119.9 s  | 20.21 s |

opw-5245007


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#240753
Forward-Port-Of: odoo/odoo#238853

#edi#performance#product search

[FIX] hr_expense_extract: add group restriction to OCR label

PR #103429

Enterprisesaas-18.3hr_expense_extract

This update corrects a visual issue where the OCR label for expense documents was incorrectly displayed alongside the data, causing a misalignment in the expense report grid. The fix ensures that labels and data are properly aligned, improving the user experience when viewing OCR-processed expenses. This was triggered by a change in how OCR data is handled.

Original PR description

Prerequisites
-------------
To test this scenario you need either OCR credits, a free trial or to use the IAP account we have in the spreadsheet.

Steps To Reproduce
------------------
1- Go to Expenses > My Expenses.
2- Upload a receipt to trigger OCR.
3- Open the expense in Normal Mode (It works fine in Debug Mode).

Issue
-----
"Payment Method" field is misaligned - label appears in the value column and field appears in the label column.

Cause
-----
The label for "ID of the request to IAP-OCR" (`extract_document_uuid`) is visible when OCR data exists, but its field is only visible in Debug Mode. This orphan label breaks the grid layout.

opw-5369619

Forward-Port-Of: odoo/enterprise#103189

#ocr#expense#ui#layout

[FIX] analytic: skip update field in the analytic

PR #242423

Coresaas-18.3analytic

This update resolves an issue where the analytic distribution field contained unexpected data types, specifically the '__update__' string, causing errors during account ID retrieval. The fix now safely processes only strings that can be interpreted as numbers, providing a more robust and reliable system for managing analytic accounts.

Original PR description

Issue:
Before this commit, the analytic distribution field contained a mix of integers (account IDs) and strings (such as '__update__'). When attempting to retrieve the account ID, converting the '__update__' string to an integer caused an error.

Fix:
As a generic solution, instead of skipping only the '__update__' key—which may not be the only non-numeric string in the future—we now process only the strings that can be safely interpreted as numbers.

opw-5450293

Forward-Port-Of: odoo/odoo#242021

#analytics#data processing

[FIX] pos_sale: Manage products paid on ecommerce in the POS

PR #242250

Coresaas-18.3pos_saleMEDIUM

This update fixes a previous issue where payments made on the website weren't correctly reflected in the POS. Now, the POS automatically recognizes and accounts for payments made on ecommerce, creating a down payment line for existing orders. Additionally, fully paid orders that aren't yet invoiced will no longer appear in the POS, preventing duplicate payments.

Original PR description

Before, if you paid for something on the website with ecommerce, it would create a sale order with a transaction linked to it, but no invoice. So in the POS the order would show up in the…

Before, if you paid for something on the website with ecommerce, it would create a sale order with a transaction linked to it, but no invoice. So in the POS the order would show up in the Quotation/Order menu, but the POS didn't have any reference on the payment, so you would have to create another duplicate payment.

Now the amount_paid (which is the amount already paid in transactions) is taken into account when calculating what's left to pay in the POS. So anytime you open a sale order in the POS it should create a down payment line for anything already paid on the website (the same as we were already doing for invoices).

Also to avoid double payments, now the sale orders which have been already paid in full, even if they are not invoiced yet, will not show up in the POS. The invoice can still be created normally from the Sale app in Odoo.

Task-5187602
Original Task-5138081

Backport-[#230809](https://github.com/odoo/odoo/pull/230809)

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#233851
Forward-Port-Of: odoo/odoo#232841

#ecommerce#payments#pos#sales

[FIX] pos_sale: Manage products paid on ecommerce in the POS

PR #103350

Enterprisesaas-18.3pos_saleMEDIUM

This update fixes a problem where payments made on the website weren't correctly reflected in the POS. Now, the POS automatically recognizes and accounts for previously paid amounts, creating down payment lines for ecommerce orders. Additionally, fully paid orders that aren't yet invoiced will no longer appear in the POS, preventing duplicate payments.

Original PR description

Before, if you paid for something on the website with ecommerce, it would create a sale order with a transaction linked to it, but no invoice. So in the POS the order would show up in the…

Before, if you paid for something on the website with ecommerce, it would create a sale order with a transaction linked to it, but no invoice. So in the POS the order would show up in the Quotation/Order menu, but the POS didn't have any reference on the payment, so you would have to create another duplicate payment.

Now the amount_paid (which is the amount already paid in transactions) is taken into account when calculating what's left to pay in the POS. So anytime you open a sale order in the POS it should create a down payment line for anything already paid on the website (the same as we were already doing for invoices).

Also to avoid double payments, now the sale orders which have been already paid in full, even if they are not invoiced yet, will not show up in the POS. The invoice can still be created normally from the Sale app in Odoo.

Task-5187602
Community PR-[#232841](https://github.com/odoo/odoo/pull/232841)

Backport-[#96876](#https://github.com/odoo/enterprise/pull/96876) Original Task-5138081

Forward-Port-Of: odoo/enterprise#98498
Forward-Port-Of: odoo/enterprise#98029

#ecommerce#payments#pos

[FIX] hw_drivers: tailscale compatible upgrade

PR #242432

Coresaas-18.3hw_drivers

This update resolves an issue preventing Odoo from working correctly with Tailscale, a secure remote access tool. The change adds a necessary file, fixing a 'file not found' error that was impacting users. This ensures seamless remote access for our team.

Original PR description

This PR adds a compatibility with Tailscale after upgrading 25_06/25_07 images to 19.1.

It fixes the error
```
FileNotFoundError: [Errno 2] No such file or directory: 'tailscale'
```

Forward-Port-Of: odoo/odoo#242292

#remote access#security#Tailscale

[FIX] l10n_be_hr_payroll: Update withholding taxes up to 2026

PR #103389

Enterprisesaas-18.3l10n_be_hr_payroll

This update corrects calculations for Belgian withholding taxes in the HR payroll module, ensuring accurate reporting up to the year 2026. This fix addresses a discrepancy in tax rates, improving the reliability of payroll data for our Belgian clients. It’s a routine maintenance update to maintain compliance.

Original PR description

TaskID: 5403525

Forward-Port-Of: odoo/enterprise#103271
Forward-Port-Of: odoo/enterprise#103215

#payroll#Belgium#taxes

[FIX] hr_contract_salary: Error When Canceling Image Selection

PR #103387

Enterprisesaas-18.3hr_contract_salary

This update resolves a bug in the Salary Configurator that prevented users from successfully canceling the selection of an employee photo. The fix ensures the system correctly handles image uploads and cancellations, improving the user experience. This prevents a potential error message from appearing.

Original PR description

**Version:**
- 17.0

**Steps to reproduce:**
- Install the hr_contract_salary module.
- Go to Employee contract and click the Generate Offer.
- Click on 'Send By Email' button and open Salary Configurator.
- Upload an employee photo the first time. then cancel the image
   selection the second time.

**Issue:**
- Error occurs when canceling the image selection on Salary Configurator page.

**cause:**
- The condition to check whether the file exists properly was missing.

**solution:**
- Added the missing condition to properly check that file exist.

Task-5423390

Forward-Port-Of: odoo/enterprise#102410

#HR#Configuration#User Experience

[FIX] website_links: unused "copy" step in tour

PR #241888

Coresaas-18.3website_links

This update removes an unnecessary step from the website tour process. Previously, a step was present that didn't perform any action, now that the underlying functionality has been adjusted. This change simplifies the tour and avoids potential confusion for users.

Original PR description

Following PR [^1], the step about copying the tracker link doesn't do anything as the only actual "action" made in the custom "run()" function has been removed (sic), leaving only the mocking of the Clipboard API (which isn't called anymore, anyway).

This commit removes this unused step to avoid confusion.

[^1]: https://github.com/odoo/odoo/pull/170548

Forward-Port-Of: odoo/odoo#241358

#tour#website#functionality

[FIX] html_editor: prevent traceback on failed metadata fetch

PR #242369

Coresaas-18.3html_editorMEDIUM

This update resolves an issue where the HTML editor would crash if a URL couldn't be fetched (like due to website restrictions). The change ensures that errors during metadata retrieval are handled gracefully, preventing the editor from freezing and improving the user experience. This improves stability and reliability of the editor.

Original PR description

Problem:
When a fetch request fails (for example due to CORS restrictions), a traceback occurs in the editor.

Solution:
Backport 971d88121968c85a86c805458d5d9dbbb305995c and ensure the error handling check is applied for both internal and external metadata fetching.

Steps to reproduce:
- Create a tracked link.
- Copy the tracked link.
- Create a link in the editor and use the copied URL.
- Apply.
- Traceback occurs.

task-5394908

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#240712

#html_editor#stability#user experience

[FIX] base: the .1s timeout in the SMTPD tests is overly conservative

PR #242441

Coresaas-18.3base

This update adjusts the timeout duration in the SMTPD tests to prevent unnecessary failures. Previously, a short timeout caused frequent test disruptions. Increasing the timeout allows the tests to complete successfully, improving overall system stability and reducing the need for manual intervention.

Original PR description

There are multiple cases where the SMTPD tests fail due to a timeout error. It is much worse to get a red runbot due to a silly timeout than to sometime wait a bit longer than .1 second.

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

Forward-Port-Of: odoo/odoo#242214

#testing#stability

[FIX] core: Prevent crash with hierarchy default filter

PR #242336

Coresaas-18.3base

This update fixes a crash that occurred when deleting an employee within a hierarchical structure (like departments). The change ensures the system correctly handles record existence during filter operations, preventing the 'Missing Record' error. This improves stability and reliability for employee management.

Original PR description

Reproduce the crash:
1- Create departement in Employees.
2- Create a default filter with child_of or parent_of on the previously
created departement.
3- Delete the departement.
4- Go back to Employees
=> Crash 'Missing Record'

This commit adds a check for record exitence in `child_of_domain` and
`parent_of_domain` in the case where `_parent_store` is True. This
change prevents the `Missing Record` Error.

task-5217722

Forward-Port-Of: odoo/odoo#242138
Forward-Port-Of: odoo/odoo#240013

#employee#hierarchy#stability

[FIX] hr_holidays_contract: Recompute duration after changing contracts

PR #242372

Coresaas-18.3hr_holidays_contractMEDIUM

This update fixes an issue where time-off durations weren't accurately calculated after changing an employee's contract. The fix ensures that the employee's working schedule is fully updated before calculating leave durations, preventing incorrect totals. This improves the reliability of time-off tracking for employees.

Original PR description

### Steps to reproduce: - define a time-off type in hours - create working schedules : standard 40h (fixed hours) standard 20h (fixed hours) Flexible 40h (flex hours) Flexible 20h (flex hours) -…

### Steps to reproduce:
	- define a time-off type in hours
	- create working schedules :
		standard 40h (fixed hours)
		standard 20h (fixed hours)
		Flexible 40h (flex hours)
		Flexible 20h (flex hours)
	- create 2 employees: employee 1 with fixed hours ; employee 2 with flexible hours
	- create contract 1 Fix 100% (start in 01/01/2025 - standard 40h) and set it to running
	- create contract 2 Flex 100% (start in 01/01/2025 - Flexible 40h) and set it to running
	- register a 1st week t-o for each employee (ex: 08/03/2025-08/09/2025) ==> 40h and validate
	- register a 2nd week t-o for each employee (09/07/2025-09/13/2025) ==> 40h and validate
	- expire current contract (100%) for each employee and launch a new contract (50%) : 
		- Standard 20h (Fixed hours) for employee 1 ; 
		- Flexible 20h (flex hours) for employee 2 (start on 08/24/2025)
			==> set them to running

### Cause:
While we are recomputing the duration of the overlapping leaves
the resource_calendar for the employee is not yet changed so when
getting the work_intervals we are calculating it using the old hours_per_day.

Also since we are still writing to the contract and it is not yet
in running state so we won't be able to use _get_calendars_validity_within_period


### Fix:
We add the number of days and duration display to the compute queue
so it will be recomputed after we already change the employee's resource_calendar

opw-5010995

Forward-Port-Of: odoo/odoo#227298

#hr#time-off#contracts

[FIX] account: prevent error when opening the tax return

PR #239814

Coresaas-18.3accountMEDIUM

This update fixes an error that occurred when users set a negative value for the fiscal year end day in the Tax Returns view. The fix prevents invalid data from being saved, ensuring the Tax Returns functionality operates correctly. This resolves a potential disruption to financial reporting.

Original PR description

Currently, an error occurs when user tries to open the Tax Return view. **Steps to Reproduce:** - Install the `Accounting` module. - Go to `Tax Returns` and set the `Fiscal Year End Day to negative…

Currently, an error occurs when user tries to open the Tax Return view.

**Steps to Reproduce:**
- Install the `Accounting` module.
- Go to `Tax Returns` and set the `Fiscal Year End Day to negative value`, then click `Apply`.

**Error:**
`ValueError: day is out of range for month.`

**Cause:**

- The field is related to the `company's fiscalyear_last_day` [1].
- When the user enters a `negative value`, that invalid value is written directly to the `company's fiscal year last day`[2] .
- When the user opens the `Tax Returns`, it going to compute the `fiscal year dates` [4]. Since the day value is negative, it raises error [5] because the day is out of range for the month.

**Fix:**
- This commit ensures that a validation error is raised when a user enters zero or negative fiscal year date.
- In 18.3, setting the value to 0 falls back to the previously defined company value [2].
- In 19.0, however, the value 0 is incorrectly saved on the company [3], causing an error.
- This fix restores the correct behavior and resolves the issue in 19.0 as well.

[1]: https://github.com/odoo/odoo/blob/27cd0a3fea1b47a85a4f3d397b052bbec08e182b/addons/account/wizard/setup_wizards.py#L17-L18

[2]: https://github.com/odoo/odoo/blob/45ca03fcb77febf4f373fe35f0242720e88cb85b/addons/account/wizard/setup_wizards.py#L49

[3]: https://github.com/odoo/odoo/blob/27cd0a3fea1b47a85a4f3d397b052bbec08e182b/addons/account/wizard/setup_wizards.py#L54-L56

[4]: https://github.com/odoo/enterprise/blob/99642bdf62f8b1c653dfefdbdcd0e9258cc9e307/account_accountant/models/res_company.py#L174-L175

[5]: https://github.com/odoo/odoo/blob/27cd0a3fea1b47a85a4f3d397b052bbec08e182b/odoo/tools/date_utils.py#L242

sentry-7102968735

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#accounting#tax#fiscal year

[FIX] pos_hr : An TB occurs at opening and closing without any details

PR #234692

Coresaas-18.3point_of_salepos_loyaltyMEDIUM

A technical error occurred when switching between POS configurations with and without employee login. This fix ensures the system correctly updates its data storage (IndexedDB) to account for the 'Log in with employees' option, preventing errors during opening and closing processes. This improves the stability and reliability of the POS functionality.

Original PR description

Before this fix, a traceback occurred on the frontend when switching from a POS configuration without the “Log in with employees” option enabled to one that had it enabled.

Steps to reproduce :
1. Open a PoS without "Log In With Employees" option activated
2. Close Register and go to the backend
3. Enable the "Log in with employees option" for this PoS and set some users
4. Re-open the PoS with a user and close it
5. A TB occured

This traceback occurred because the IndexedDB did not include the "hr.employee" module required by the "Log in with employees" option.

The fix was to upgrade the IndexedDB if a module is missing.

task: 5223393

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#POS#employee login#stability

[FIX] mail: restore paragraph bottom margin in chatter messages

PR #242392

Coresaas-18.3mail

This update corrects a visual inconsistency in the Odoo chatter interface. Previously, paragraphs added in the composer didn't maintain the correct bottom margin when posted to the chat. This change ensures that messages sent via chatter display with consistent spacing, matching the composer and email versions, improving the overall user experience.

Original PR description

Problem:
When adding a paragraph in the composer and sending the message, the paragraph posted in the chatter has a `margin-bottom` of 0.

Cause:
Paragraphs in the chatter rendering override the default bottom margin, resulting in inconsistent spacing compared to the composer and the sent email.

Solution:
Update selector to only target the last `p`.

Steps to reproduce:
- Open the chatter composer.
- Add a paragraph using "/Paragraph".
- Add some text.
- Send the message.
- Observe that the message posted in the chatter has no bottom margin, unlike in the composer.

opw-5378129

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#240082

#UI#Chatter#Spacing

[FIX] sale_pdf_quote_builder: allow extra documents on confirmed orders

PR #242412

Coresaas-18.3sale_pdf_quote_builderMEDIUM

This update fixes an issue where product documents, headers, or footers weren't being added to PDF quotes after they were confirmed. A new configuration setting allows users to ensure these documents are always included in the final PDF, regardless of whether the order is confirmed. This improves the accuracy and completeness of sales quotes.

Original PR description

Versions
--------
- saas-18.2+

Steps
-----
1. Add product documents, headers or footers to a quotation;
2. confirm quotation;
3. print quotation.

Issue
-----
Extra documents aren't added to the PDF, even though they show up as selected in the quotation builder.

Cause
-----
As of commit b02f53d, any quotation documents linked to a sales order are simply ignored for confirmed orders.

Solution
--------
Add a `sale.always_include_selected_documents` config parameter, allowing users to keep including the selected documents on confirmed orders.

opw-5242743

Forward-Port-Of: odoo/odoo#235778

#sales#quotes#pdf#documents

[FIX] account_peppol: fix the acknowledgment

PR #242388

Coresaas-18.3account_peppol

This update fixes a technical problem related to how the system acknowledges PEPPOL messages. Previously, continuous acknowledgments caused issues on the IAP side, leading to serialization errors. Now, acknowledgments are handled after the loop, ensuring smoother processing and preventing these errors.

Original PR description

The acknowledgment should not happen in the loop, but after. In a case a problem happened in the loop, it's acceptable that we end up not acknowledging messages, their status will be retrieved again at the next call.

At the moment those continuous acks cause serialization issues on IAP side.

task-none

Forward-Port-Of: odoo/odoo#242187

#PEPPOL#acknowledgment#IAP

[FIX] web_editor: remove inline code when last character is deleted

PR #240798

Coresaas-18.3web_editorhtml_editorMEDIUM

This update fixes a persistent issue where inline code blocks were difficult to remove, particularly at the end of lists. The changes ensure code styles disappear cleanly when the last character is deleted, enhancing the editor's usability. It also addresses related problems with cursor placement and empty code block removal.

Original PR description

Text formatted as inline `<code>` (between backticks) is very difficult to remove in some situations, typically at the beginning of a list entry.

This commit solves this by removing the code style when its last character is removed.

Steps to reproduce:
- Create a list
- Type some inline code
- Put the cursor in the middle
- Press Enter
- Type some text after the inline code on the second line
- Try to remove the inline code from the second line using backspace

=> The line is removed before the code style disappears

task-5375140

Forward-Port-Of: odoo/odoo#238552

#editor#code#editing#user experience

[FIX] account_edi_ubl_cii: leitweg-id

PR #242376

Coresaas-18.3account_edi_ubl_cii

This update corrects a technical detail in the processing of xRechnung invoices, specifically related to the 'leitweg-id' field within the invoice XML. The change ensures accurate invoice formatting for this important German tax document. The fix was triggered by a test update and addresses a minor inconsistency.

Original PR description

Correction of the forward port for the leitweg-id in the
'cbc:BuyerReference' field for the xRechnung invoice.
The 'export_invoice_vals' function is an old helper that
is not used by default anymore (but used by the tests, that
is why the tests did not catch the error). I added the if statement
in the corresponding new helper: '_add_invoice_header_nodes'  and
changed the test for it to catch the error.

Related: #236333

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#241982

#xRechnung#invoice#UBL#Germany

[IMP] knowledge: fix grouped Kanban card heights

PR #103520

Enterprisesaas-18.3knowledge

This update resolves an issue where grouped Kanban cards were displaying incorrectly due to a change in the Kanban templates. The fix simply removes a no-longer-needed CSS class, ensuring consistent and correct card heights are displayed within the knowledge module.

Original PR description

Since commit https://github.com/odoo/enterprise/pull/70460 and the reworking of the Kanban templates, the h-100 class was no longer correct.

This PR fixes the issue by removing this class.

task-5439265

Forward-Port-Of: odoo/enterprise#102801

#Kanban#UI#Knowledge

[FIX] l10n_dk_nemhandel: PrepaidAmount is not always empty

PR #242479

Coresaas-18.3l10n_dk_nemhandel

This update corrects a problem where invoice XML files generated for Danish Nemhandel transactions were failing validation due to an incorrect assumption about the ‘PrepaidAmount’ field. The fix ensures the ‘PrepaidAmount’ node is only removed when the value is actually zero, resolving the validation issue and allowing invoices to be correctly processed.

Original PR description

To reproduce: create an invoice that is reconciled (typically a credit note) before Send&Print.
Check the validity of the xml with a schematron
=> it fails due to the value of the PrepaidAmount

The node PrepaidAmount gets removed because it was wrongly thought to be always empty.
We now only remove it if the value is at 0.

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

Forward-Port-Of: odoo/odoo#242008

#invoice#xml#danish#nemhandel

[FIX] quality_control: add default name for new spreadsheet template

PR #103408

Enterprisesaas-18.3quality_control

This update resolves an issue where creating a new spreadsheet template within the Quality Control app would trigger a validation error due to a missing default name. The fix provides a default name, ensuring the template creation process functions correctly and avoids the error.

Original PR description

**Issue** A validation error is raised when creating a new spreadsheet template from a Quality Control Point. **Steps to reproduce** 1. Open the Quality app. 2. Go to Quality Control > Control…

**Issue**
A validation error is raised when creating a new spreadsheet template from a Quality Control Point.

**Steps to reproduce**
1. Open the Quality app.
2. Go to Quality Control > Control Points.
3. Click "New".
4. Set the type to "Spreadsheet".
5. Click on Spreadsheet Template > Search More.
6. Click "New".
-> A validation error is raised.

**Cause**
In `quality_view`:
https://github.com/odoo/enterprise/blob/f54585f84b0fa7a73efb3f0e14266972d510f0a6/quality_control/views/quality_views.xml#L840C17-L845C19
the `many2one_spreadsheet` widget (see [`many2one_spreadsheet_field.js`](https://github.com/odoo/enterprise/blob/f54585f84b0fa7a73efb3f0e14266972d510f0a6/spreadsheet_edition/static/src/assets/components/many2one_spreadsheet_field.js#L36)) overrides "Create and Edit" to create a new spreadsheet through `Many2XSpreadsheetAutocomplete`:
https://github.com/odoo/enterprise/blob/f54585f84b0fa7a73efb3f0e14266972d510f0a6/spreadsheet_edition/static/src/assets/components/many2one_spreadsheet_field.js#L11C9-L14C51

This flow does not set a default value for the required `name` field, nor does `action_open_new_spreadsheet`:https://github.com/odoo/enterprise/blob/8365feab396679f0323e89c2f4e0c825a0b2ee7e/spreadsheet_edition/models/spreadsheet_mixin.py#L348 
Since `name` is required:
https://github.com/odoo/enterprise/blob/8365feab396679f0323e89c2f4e0c825a0b2ee7e/quality_control/models/quality_spreadsheet_template.py#L12
validation fails.

**Solution**
Provide a default value for the `name` field, using the same default as in `documents_document.py`:
https://github.com/odoo/enterprise/blob/8365feab396679f0323e89c2f4e0c825a0b2ee7e/documents_spreadsheet/models/documents_document.py#L321

opw-5340710

Forward-Port-Of: odoo/enterprise#101671

#quality#spreadsheet#template

[FIX] stock_barcode: prevent validate multiple times

PR #102465

Enterprisesaas-18.3stockMEDIUM

This update corrects a bug where repeatedly validating a stock transfer in the Barcode app could create duplicate stock entries, particularly with unreserved products. The fix ensures that the validation process is only executed once, preventing data inconsistencies and saving time for users. This improves the reliability of transfer processing.

Original PR description

**Problem:** When processing a picking in Barcode, it's possible to press the validate button or scan the validate barcode multiple times before the transfer validates or raises an error. This is…

**Problem:**
When processing a picking in Barcode, it's possible to press the validate button or scan the validate barcode multiple times before the transfer validates or raises an error. This is especially a problem when unreserved products are added to a transfer, since each additional validate call will duplicate those products (and their lot/SNs).

**Steps to Reproduce:**
- In the Barcode app, create a new internal transfer
- Scan a product, then scan the destination location 'WH/Stock/Shelf 1' ('2601892' is the barcode)
- Click the "Validate" button (or scan 'O-BTN.validate') multiple times as quickly as possible
- See that the "The transfer has been validated" toast appears (and possibly warnings about validating a done transfer) -> On the transfer, see that there are duplicated stock.move and stock.move.line

**Fix:**
Prevents the 'validate' method from executing as usual by checking if a previous call is still executing (tracked by 'isValidate').

opw-4948696

Forward-Port-Of: odoo/enterprise#101868
Forward-Port-Of: odoo/enterprise#95329

#stock#barcode#transfer#validation

Removals(1)

Features or functions removed from Odoo

[FIX] test_mimetypes: remove very situational xlsx 2025 test

PR #242389

Coresaas-18.3test_mimetypes

This update removes a specific test file related to Excel files that was causing issues with our automated testing process. This test was dependent on a recent update to a core library and wasn't compatible with our standard operating systems. Removing it improves the reliability of our automated testing and ensures smoother builds.

Original PR description

This commit removes the xslx-2025 test case. That file contains a `trash` folder and libmagic only started supporting those files with file/file@3660a2ccb77cdea0ce678d9e71fbb7aceca2adbe, this commit is notably absent from Ubuntu Jammy which is a supported OS in this Odoo version. Keeping the test makes the Runbot Distro-build CI red on Jammy which is worse than making sure we always support those (rare, arguably broken) files.

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

Forward-Port-Of: odoo/odoo#242211

#testing#maintenance

Improvements(1)

[IMP] hw_drivers: normalise logs around actions

Bug Fixes(43)

[FIX] l10n_vn_edi_viettel: wrong exchange rate when issue foreign currency invoice

[FIX] sign: make search in sign templates work again

[FIX] mail: Fix truncate all related table data

[FIX] event{,_booth}_sale: prevent traceback when close the select event option

[FIX] appointment_account_payment: avoid access error when deleting products

[IMP] account: avoid creating duplicate bank accounts during reconciliation

[FIX] l10n_tw_edi_ecpay: exclude company name in EDI address

[FIX] web: Mock call to Odoo Fin favorite institution

[FIX] mail: avoid error on service worker push subscription change

[FIX] point_of_sale: fit longer language in optional button

[FIX] l10n_fr_hr_holidays: missing default reference leave type in setting

[FIX] l10n_hr_edi: KPD category ID error fix

[FIX] html_editor: clear image styles on media replace

[FIX] website: fix appearance issue of carousel with indicators outside

[FIX] {website_,}sale_subscription: hide archived recurring plans on website

[FIX] social{_crm}: fix double post dropdown

[FIX] web: hadle empty data when exporting pivot xlsx

[FIX] pos_restaurant: floating order name not good

[FIX] appointment_hr_recruitment: fix traceback when moving applicant

[PERF] account_edi_format: Speedup product search

[FIX] hr_expense_extract: add group restriction to OCR label

[FIX] analytic: skip __update__ field in the analytic

[FIX] pos_sale: Manage products paid on ecommerce in the POS

[FIX] pos_sale: Manage products paid on ecommerce in the POS

[FIX] hw_drivers: tailscale compatible upgrade

[FIX] l10n_be_hr_payroll: Update withholding taxes up to 2026

[FIX] hr_contract_salary: Error When Canceling Image Selection

[FIX] website_links: unused "copy" step in tour

[FIX] html_editor: prevent traceback on failed metadata fetch

[FIX] base: the .1s timeout in the SMTPD tests is overly conservative

[FIX] core: Prevent crash with hierarchy default filter

[FIX] hr_holidays_contract: Recompute duration after changing contracts

[FIX] account: prevent error when opening the tax return

[FIX] pos_hr : An TB occurs at opening and closing without any details

[FIX] mail: restore paragraph bottom margin in chatter messages

[FIX] sale_pdf_quote_builder: allow extra documents on confirmed orders

[FIX] account_peppol: fix the acknowledgment

[FIX] web_editor: remove inline code when last character is deleted

[FIX] account_edi_ubl_cii: leitweg-id

[IMP] knowledge: fix grouped Kanban card heights

[FIX] l10n_dk_nemhandel: PrepaidAmount is not always empty

[FIX] quality_control: add default name for new spreadsheet template

[FIX] stock_barcode: prevent validate multiple times

Removals(1)

[FIX] test_mimetypes: remove very situational xlsx 2025 test

Improvements(1)

[IMP] hw_drivers: normalise logs around actions

Bug Fixes(43)

[FIX] l10n_vn_edi_viettel: wrong exchange rate when issue foreign currency invoice

[FIX] sign: make search in sign templates work again

[FIX] mail: Fix truncate all related table data

[FIX] event{,_booth}_sale: prevent traceback when close the select event option

[FIX] appointment_account_payment: avoid access error when deleting products

[IMP] account: avoid creating duplicate bank accounts during reconciliation

[FIX] l10n_tw_edi_ecpay: exclude company name in EDI address

[FIX] web: Mock call to Odoo Fin favorite institution

[FIX] mail: avoid error on service worker push subscription change

[FIX] point_of_sale: fit longer language in optional button

[FIX] l10n_fr_hr_holidays: missing default reference leave type in setting

[FIX] l10n_hr_edi: KPD category ID error fix

[FIX] html_editor: clear image styles on media replace

[FIX] website: fix appearance issue of carousel with indicators outside

[FIX] {website_,}sale_subscription: hide archived recurring plans on website

[FIX] social{_crm}: fix double post dropdown

[FIX] web: hadle empty data when exporting pivot xlsx

[FIX] pos_restaurant: floating order name not good

[FIX] appointment_hr_recruitment: fix traceback when moving applicant

[PERF] account_edi_format: Speedup product search

[FIX] hr_expense_extract: add group restriction to OCR label

[FIX] analytic: skip __update__ field in the analytic

[FIX] pos_sale: Manage products paid on ecommerce in the POS

[FIX] pos_sale: Manage products paid on ecommerce in the POS

[FIX] hw_drivers: tailscale compatible upgrade

[FIX] l10n_be_hr_payroll: Update withholding taxes up to 2026

[FIX] hr_contract_salary: Error When Canceling Image Selection

[FIX] website_links: unused "copy" step in tour

[FIX] html_editor: prevent traceback on failed metadata fetch

[FIX] analytic: skip update field in the analytic

[FIX] analytic: skip update field in the analytic