Friday, November 28, 2025
6 changes · 19.0
Enhancements to existing features
This update enables the IoT box to function correctly by allowing HTTP requests instead of HTTPS, simplifying setup and avoiding certificate requirements. Additionally, a warning message is displayed when HTTP requests to the Blackbox fail, providing better visibility into potential issues. This enhances the reliability of IoT integrations within the POS system.
Original PR description
Community PR: https://github.com/odoo/odoo/pull/237147 Since odoo/odoo#235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. In addition, we now show a warning message when a request to the Blackbox via HTTP fails and has to fallback to the websocket. task-5353672 Forward-Port-Of: odoo/enterprise#100469 Forward-Port-Of: odoo/enterprise#100331
This update enables the IoT box to function correctly by allowing it to use HTTP requests over the local network (LNA) instead of requiring a secure HTTPS connection. This change simplifies the setup process and ensures consistent performance for our IoT devices.
Original PR description
Enterprise PR: https://github.com/odoo/enterprise/pull/100331 **This PR contains 2 commits:** - **[IMP] iot_base: allow use of LNA for IoT requests** Chromium 142 added support for HTTPS -> HTTP…
Enterprise PR: https://github.com/odoo/enterprise/pull/100331 **This PR contains 2 commits:** - **[IMP] iot_base: allow use of LNA for IoT requests** Chromium 142 added support for HTTPS -> HTTP requests on the local network (Local Network Access). This commit adds a flag to the IoT longpolling class to enable LNA support. The flag forces all requests to use HTTP even in an HTTPS environment. It also sets the `targetAddressSpace` option to `local` in the `fetch` request. - **[IMP] point_of_sale: use_lna support for IoT requests** Since https://github.com/odoo/odoo/pull/235702, there is a `point_of_sale.use_lna` system parameter. When it is set, ePOS requests will use HTTP instead of HTTPS, and the `targetAddressSpace: "local"` option is used in the `fetch` request. This bypasses the need for a HTTPS certificate. This commit adds the same functionality to all IoT requests from the POS. This should allow the IoT box to function correctly without a HTTPS certificate. task-5353672 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#237340 Forward-Port-Of: odoo/odoo#237147
This pull request enhances the Odoo website builder with several UI improvements, including clearer controls for background images and videos, fixes for dark mode compatibility, and refinements to the page editor experience. These changes improve usability and ensure a consistent look and feel across different themes and device settings.
Original PR description
This pull request adds remove buttons for background images and videos, fixes several dark mode issues in the editor, and includes a few small UI improvements throughout the website builder. task-5104004 Forward-Port-Of: odoo/odoo#236201
This update enhances the accuracy of follow-up reporting across key Odoo modules (Client Portal, PoS, and Follow-up Report) by ensuring invoices and related entries are correctly filtered. This prevents irrelevant invoices from appearing in follow-up reports and creates a more consistent user experience.
Original PR description
This commit implements multiple improvements around the `no_followup` functionality to ensure misc entries and invoice-related moves behave consistently across Follow-up Report, Client Portal, and PoS. Main changes: -Removed default journal filters from the Follow-up Report for a cleaner view. -Display the “No Follow-up” field on miscellaneous entries whenever at least one line impacts a receivable account. -Client Portal only shows invoices that are meant for follow-up. -PoS balance includes entries that should be followed up. -“Settle Invoices” lists only invoices that require follow-up. Impact: -Avoids showing invoices that should not appear in follow-up flows. -Makes the experience more consistent across Follow-up report, Client Portal, and PoS. Related enterprise PR: https://github.com/odoo/enterprise/pull/100685 task-5149502
This update focuses on refining the user experience within the Odoo Sign app. The changes include UI adjustments and functional enhancements designed to improve usability and streamline the signing process. These improvements aim to make the sign app more intuitive and efficient for users.
Original PR description
This task aims to enhance the user experience by refining both the UI and functionality of the sign app. task-5169331
This update prepares Odoo to efficiently store and access sales commission achievement data, which was previously generated on-the-fly. For large systems, this change allows for 'materializing' the achievement data to significantly speed up report generation times, improving overall performance.
Original PR description
This commits aims to ease the possibility to materialize the achievements. The achievement table was a report built on the fly. Several commits were introduced to speed up the performances but on big systems with thousands of invoices, reading the achievements takes a few seconds. On big databases, it may be needed to materialized the achievement view to speed up reads. This commit reorganize the code to ease the materialization in a simple override commit. task-5170644