Daily updates from Odoo
Wednesday, February 4, 2026
9 changes · master
Enhancements to existing features
This update makes the top bar with embedded actions visible by default when a new audit file is created and opened for the first time. While user preferences can still control visibility later, this change provides a more intuitive starting experience for users working with audit files. This improves usability and efficiency.
Original PR description
Currently, the top bar (embedded actions) in Working Files in audit is not visible by default when the user creates and opens it for the first time. This commit makes it visible when the Audit is created and opened for the first time, later on the visibility is decided as per the user preferences set in the `res.users.settings.embedded.action` model. task-5388717 Forward-Port-Of: odoo/enterprise#101924
Resolved issues and error corrections
This update resolves an issue where opening reports would cause a crash if a report action was triggered before the report data was fully loaded. The fix ensures that report actions can be reliably used during the report loading process, improving user experience and preventing unexpected errors.
Original PR description
When a report was loading if a reportAction was used and no report already was loaded before, it would crash. This happened because we tried to get the context from the data which were not yet loaded. To reproduce: - switch to debug mode (?debug=1) - add a 5s delay in _get_lines - when a report is opening, try to click on the settings cog that appear in debug mode Forward-Port-Of: odoo/enterprise#103636
This update prevents documents from automatically opening in a form view when accessed through various channels like direct links or systray notifications. Previously, users were unexpectedly directed to the document's form view, which has now been corrected to provide a smoother and more intuitive experience. This change improves usability and aligns with user expectations.
Original PR description
Users do not want to access the form view of the document by default. This PR solves three cases for accessing documents.document records that were not covered before: * From the basic path pattern `odoo/x/documents.document/<id>` * From a systray notification "Open Form View" * when we are not yet in Documents * when we already are in Documents * From the Discuss app, on the record's thread Tests for most of these are included. Additionally, make sure the document is selected on accessing from `_get_access_action`. Task-5386466 Forward-Port-Of: odoo/enterprise#106214 Forward-Port-Of: odoo/enterprise#104622
This update corrects an issue where uploading a new signature PDF would fail if the 'signature' item type (ID 1) was deleted. The problem stemmed from a recent change that created a dummy item for role recognition, leading to an error when no item type matched. This fix ensures smooth PDF uploads for signature creation.
Original PR description
steps to reproduce :
- delete the sign.item.type with id 1 ("signature")
- try to upload a new pdf to sign
The issue appears since PR 91189 that creates a dummy item to recognize roles that can be vacuumed.
Since the item type of the dummy item is irrelevant, we now just try to find the first one we can to fill in the dummy item with an Error if none is exists.
Forward-Port-Of: odoo/enterprise#106219
Forward-Port-Of: odoo/enterprise#106138This update resolves an issue where IoT reports generated from Point of Sale (PoS) were failing due to PoS using incorrect identifiers. The fix filters out reports that don't use integer IDs, specifically those using string UUIDs, as these are not needed for PDF report generation. This ensures reliable report printing.
Original PR description
Rendering IoT reports from PoS is failing because of PoS using string uuids as `res_ids`. As they are not required to render pdf reports, we filter them out. Forward-Port-Of: odoo/enterprise#106277
This update fixes issues with how Odoo websites extract content, specifically addressing problems with robots.txt checks and content cleaning. The changes ensure accurate data collection from Odoo websites by refining noise removal and preventing errors in content extraction logic.
Original PR description
## Fix Summary - Include the instance's base URL in internal domains to allow bypassing robots.txt checks for sites that have no domain. - Fix the scraper's cleaning logic to prevent content containers deletion edge cases on Odoo websites. - Refine noise removal for Odoo websites (popups, cookie bars, etc.). Forward-Port-Of: odoo/enterprise#106237
This update fixes an issue where malformed PDFs caused errors during the signature process. The system now attempts a more lenient PDF parsing method if the initial attempt fails, ensuring signatures can be processed more reliably. This improves the overall stability and functionality of the signature workflow.
Original PR description
Before this commit, opening some malformed PDFs failed during flattening because PyPDF2 strict parsing and form-field reads raised errors. After this commit, we try first parsing the PDF in the usual way and if we fail, we try again with strict=False. See https://pypdf.readthedocs.io/en/stable/user/robustness.html. task-5902859
The Odoo portal payment screen now displays a warning message when no payment providers are available, preventing the screen from scrolling to the bottom. This ensures users receive clear guidance and avoids a confusing user experience when payment options are unavailable. This resolves a previous issue where users didn't see any payment methods or warnings.
Original PR description
The portal payment screen incorrectly scrolls to the bottom when the Pay button is clicked, but no payment methods or warning message are shown. This happens when no payment provider is published. This PR fixes the issue by ensuring the "no provider" warning message appears in all cases. task-5388313 Forward-Port-Of: odoo/enterprise#101632
Features or functions removed from Odoo
This update simplifies Odoo's activity flow by removing outdated code related to automatically creating follow-up tasks. The changes primarily affect the Documents, Sign, and VoIP modules, streamlining workflows and improving performance. This aligns with a new, simplified activity system.
Original PR description
Purpose: Align modules with the new simplified activity flow by cleaning up the logic related to the 'Trigger Next Activity' feature. Specifications: - documents: remove next activity preparation, frontend refresh logic, and related tests - l10n_in_reports: Removed obsolete chaining type field from activity type data. - sign: remove chaining type handling from activity buttons and hide Suggested Next Activity field since no follow-up is created - voip: update call activity handling since follow-up activities are no longer created on call completion Task-4863143