Monday, August 18, 2025
4 changes · saas-18.3
Enhancements to existing features
Point of Sale and related payment, loyalty, restaurant, and self-order areas now provide richer behind-the-scenes console information. This helps support and development teams diagnose checkout and payment issues faster without changing the cashier or customer experience.
Original PR description
*: pos_adyen, pos_loyalty, pos_online_payment, pos_restaurant, pos_stripe Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more…
*: pos_adyen, pos_loyalty, pos_online_payment, pos_restaurant, pos_stripe Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more informations are now included in the console logs, such as the module name, function name, and a message. This makes it easier to track down issues and understand the flow of the application. Also when unfolding the console logs, some additional context is provided: - Variable values (if given to the console method) - Call stack trace (if available) Example of a log message: [IndexedDB]: put - Processing 40 items in store pos.order.line ### With its call stack: logPosMessage @ pretty_console_log.js:13 (anonymous) @ indexed_db.js:113 promises @ indexed_db.js:92 create @ indexed_db.js:193 synchronizeLocalDataInIndexedDB @ data_service.js:182 ..... ## Screenshots: <img width="779" height="764" alt="image" src="https://github.com/user-attachments/assets/6be024e4-e849-478b-9cdd-653300fc015a" /> https://github.com/user-attachments/assets/2342ca52-719c-4368-94e6-1e692faf12e0
This change lets other parts of Odoo reuse the existing logic that reads filenames from download responses. It keeps download behavior consistent, reduces duplicated work, and lowers the risk of filename issues in custom download flows without changing current user behavior.
Original PR description
Allow other modules to reuse the existing RFC 6266/5987-compliant parser for the Content-Disposition header. This avoids duplicated parsing logic and prevents subtle bugs when extracting filenames (quoted, escaped, or RFC 5987-encoded) across custom XHR/Blob download flows. This change only exports an already used function in the web download stack. No behavior change, no performance impact, and fully backward compatible. It centralizes fixes and makes testing easier while keeping modules consistent. 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#222273
The Spanish accounting localization now classifies account 411000, used for commercial bills payable, as a current liability instead of a current asset. This improves financial statement accuracy by placing payable obligations in the correct category.
Original PR description
This commit changes the account type for account `411000 Acreedores, efectos comerciales a pagar`. It was previously set as a `Current Asset` and now its account type is `Current Liability`. Task : 4757149 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#221910
Point of Sale and related country-specific POS modules now provide clearer console logs with more context, such as where a message comes from and supporting details. This helps support and development teams diagnose POS issues faster without changing the cashier experience.
Original PR description
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility…
*: l10n_de_pos_cert, l10n_de_pos_res_cert, l10n_it_pos, pos_enterprise, pos_iot, pos_mobile Improve console logging in the Point of Sale and related modules. By using the `logPosMessage` utility function more informations are now included in the console logs, such as the module name, function name, and a message. This makes it easier to track down issues and understand the flow of the application. Also when unfolding the console logs, some additional context is provided: - Variable values (if given to the console method) - Call stack trace (if available) ## Example of a log message: [IndexedDB]: put - Processing 40 items in store pos.order.line ### With its call stack: logPosMessage @ pretty_console_log.js:13 (anonymous) @ indexed_db.js:113 promises @ indexed_db.js:92 create @ indexed_db.js:193 synchronizeLocalDataInIndexedDB @ data_service.js:182 ..... ## Screenshots: <img width="779" height="764" alt="image" src="https://github.com/user-attachments/assets/6be024e4-e849-478b-9cdd-653300fc015a" /> https://github.com/user-attachments/assets/2342ca52-719c-4368-94e6-1e692faf12e0