Wednesday, February 18, 2026
7 changes · 17.0
Resolved issues and error corrections
This update ensures that the Studio XML editor only translates views for the currently selected website, preventing unintended translations from other websites in the database. This improves the user experience by focusing translations on the relevant website content, resolving a previous issue where the default website's language was always used.
Original PR description
Problem: When opening the Studio XML editor when Website is installed, the translation terms corresponding to the Default Language of the first website in the database are used. This behavior should only be applied to the HTML/CSS Editor in Website. Purpose: Modify Website's override of get_related_views to only return translated views when called with a specific website in context. This is done here by adding a context flag, as to not interfere with customizations made in stable versions. This will be changed for master. Steps to Reproduce in Runbot: 1. Activate a non-English (US) language. 2. Add this language to the Website with the lowest ID in the database, then set it to the Default Language of the Website. 3. Enter Studio and navigate to a view that has translation terms in its view (ex. Invoice PDF Report), then open the XML editor. opw-5136124
This update resolves a problem preventing Virtual IoT boxes from downloading handlers due to a limitation in Python's SSL verification process on Windows. The change ensures secure certificate validation by explicitly using a trusted certificate package, maintaining security while restoring functionality.
Original PR description
In PR #233423, we rightfully removed `cert_reqs='CERT_NONE'` to enforce secure certificate validation during IoT handler downloads. However, this exposed a blind spot in Python's `urllib3` library on Windows. Because `urllib3` defaults to the host's underlying certificate list (which is limited on Windows) instead of the installed `certifi` package, Virtual IoT boxes get the following error during handler downloads: `certificate verify failed: unable to get local issuer certificate` This commit restores the broken flow while maintaining security by explicitly passing `certifi.where()` to the `urllib3.PoolManager` via the `ca_certs` parameter. opw-5902549 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A recent test failure related to the eWallet checkout process has been fixed. The update ensures the system correctly applies the eWallet discount and updates the total amount before proceeding to the final payment step, preventing checkout errors.
Original PR description
In the `shop_sale_ewallet` tour, a Runbot error was triggered because the test would add a $50 product to the cart and immediately click the checkout button after selecting eWallet. This sometimes caused the eWallet to not be applied in time, leaving the total amount not updated to $0, and later the pay button could not be found. Solution: Ensure that after clicking on eWallet, the tour waits for the total amount to be $0 and for a success message confirming the code has been applied before proceeding to checkout. runbot-145574
This update resolves an issue where the ZATCA XML generation process would fail when an order had no payment due to full discounts. Now, the system correctly handles orders with zero payment, ensuring accurate ZATCA reporting. This prevents potential reporting errors and maintains data integrity.
Original PR description
Before this commit, when an order was fully discounted and therefore had no payment, the generation of the XML file for ZATCA would fail. opw-5928185 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves a technical issue where `Image` and `Binary` objects were incorrectly linked. The fix ensures these object types maintain distinct type values, preventing potential data inconsistencies. This improves the stability and reliability of Odoo's image and binary management.
Original PR description
This fixes an oversight of 4840a6639deb171c28ae14b0269d420aa1503860 that `Image` and `Binary` objects have the same `self.type` value and thus an `Image` can relate to a `Binary`, after all. Forward-Port-Of: odoo/odoo#249260
This update ensures that Website Studio's translation terms are correctly applied only to views associated with the active website, resolving an issue where the default website's language was being used. This improves the accuracy and relevance of translations within the Studio interface, enhancing the user experience for website customization.
Original PR description
Problem: When opening the Studio XML editor when Website is installed, the translation terms corresponding to the Default Language of the first website in the database are used. This behavior should only be applied to the HTML/CSS Editor in Website. Purpose: Modify Website's override of get_related_views to only return translated views when called with a specific website in context. Steps to Reproduce in Runbot: 1. Activate a non-English (US) language. 2. Add this language to the Website with the lowest ID in the database, then set it to the Default Language of the Website. 3. Enter Studio and navigate to a view that has translation terms in its view (ex. Invoice PDF Report), then open the XML editor. opw-5136124
This update resolves an issue where Ecuadorian EDI reports generated duplicate headers, causing wasted space and inconsistent formatting. The fix ensures that only the required Ecuadorian header is displayed, aligning with legal requirements and improving report clarity. This change impacts reports for Ecuadorian companies.
Original PR description
**Steps to reproduce:** * Install the **l10n_ec_edi** module. * Use an **Ecuadorian company**. * Create and confirm a customer invoice, vendor bill, or delivery guide. * Print any Ecuadorian PDF…
**Steps to reproduce:** * Install the **l10n_ec_edi** module. * Use an **Ecuadorian company**. * Create and confirm a customer invoice, vendor bill, or delivery guide. * Print any Ecuadorian PDF report (invoice/credit note, purchase liquidation, withholding, or delivery guide). **Observed behavior:** * Generated PDFs display **two headers**: * The standard Odoo company header. * The legally required Ecuadorian EDI header. * This results in duplicated information and wasted space. **Cause:** * Ecuadorian report templates relied on `web.external_layout`, which automatically renders the Odoo company header. * A custom Ecuadorian header was added on top, instead of replacing the standard one. * Both headers were therefore rendered together. **Fix:** * Hide the standard Odoo header for **Ecuadorian companies** in `external_layout_standard`. * Use the Ecuadorian header as the document title for local EDI reports. **Before:** <img width="549" height="379" alt="image" src="https://github.com/user-attachments/assets/0352ddad-f4b5-4764-aed1-291f6f514f8d" /> **After:** <img width="606" height="516" alt="image" src="https://github.com/user-attachments/assets/2b491ffc-9430-4858-a25e-0423da59cfe5" /> opw-5414882