Wednesday, August 20, 2025
5 changes · saas-18.4
Enhancements to existing features
The accounting tax helper documentation was improved to make it clearer which capabilities are available in point-of-sale JavaScript code and which are only available on the server side. This helps teams avoid confusion when maintaining tax-related logic across different parts of the system.
Original PR description
Since some of them are copy pasted javascript side, adding such docstring is helping to distinguish what is available directly js-side from point_of_sale from what is only accessible python-side. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#223330 Forward-Port-Of: odoo/odoo#223258
Point of Sale and related payment, loyalty, restaurant, and self-order modules now produce clearer diagnostic logs. This helps support and development teams identify where POS issues occur faster, reducing investigation time without changing the customer-facing checkout flow.
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 Forward-Port-Of: odoo/odoo#222339
Users now receive a clear warning when enabling WhatsApp debug mode. This helps prevent surprises by explaining that media files will stop being received while debug mode is active.
Original PR description
#### Step to reproduce: - go to WhatsApp > Configuration > WhatsApp Buisness Account - enable debug mode #### Previous behavior: - active debug mode #### Expected behavior: - active debug mode - warn user that WhatsApp debug mode will stop medias from being received Other solutions would include the use of: - warning. They are triggered only on `onchange` methods. However, debug_logging is updated through buttons which do not trigger `onchange`. Therefore, to update it through a field it requires some changes in the XML which aren't appropriate for stable. - confirm using a wizard. It would require a new view which is not stable either. opw-4678542 Forward-Port-Of: odoo/enterprise#89995
The website generator now checks whether a provided URL can be reached before starting the scraping step. This helps avoid failed generation attempts and gives users a smoother setup experience when entering website addresses.
Original PR description
This commit checks that the URL is reachable before making the scraper request.
Point of Sale and related localization, IoT, enterprise, and mobile modules now produce clearer console logs with more context. This helps support and development teams diagnose POS issues faster without changing day-to-day user workflows.
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 Forward-Port-Of: odoo/enterprise#92021