Daily updates from Odoo
Navigate
Branch
Sunday, December 21, 2025
7 changes
2 changes
Resolved issues and error corrections
This update resolves an issue where the ‘eas’ field was incorrectly focused during Peppol registration. By removing the ability to focus this field, the registration process is now streamlined and ensures users correctly select the pre-selected option, improving the user experience and data accuracy.
Original PR description
During registration on Peppol, the eas field is focused first, which makes no sense as it's supposed to be correctly preselected, and users aren't supposed to touch it So this commit makes it non-focusable 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#240747 Forward-Port-Of: odoo/odoo#240679
A recent update to the ‘Update Tax Tags’ wizard in Odoo v18 was causing it to crash when a company had a tax lock date configured. This fix reintroduces a previously used element to ensure the wizard correctly loads company information and calculates the warning date, resolving the crash and restoring functionality.
Original PR description
Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising: ``` TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` The…
Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising: ``` TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` The error happens because `_compute_display_lock_date_warning` is evaluated while date_from is still False, so the comparison `wizard.date_from < tax_lock_date` ends up comparing a boolean with a date. In v17 the wizard form view included an invisible company_id field, which ensured the company was properly loaded in the cache and allowed `_compute_date_from` to run with the correct company_id and tax_lock_date before the warning compute was triggered. This change reintroduces the invisible company_id field in the wizard form view to restore the v17 behavior. The wizard now loads the company correctly, computes `date_from` based on the tax lock date, and then computes `display_lock_date_warning` without triggering the TypeError. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238005
2 changes
Resolved issues and error corrections
This update resolves a crash in the 'Update Tax Tags' wizard when a company has a tax lock date configured in version 18.3. The fix reintroduces a previously used field to ensure the wizard correctly loads company data and calculates the warning, preventing the error and restoring functionality.
Original PR description
Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising: ``` TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` The…
Opening the `Update Tax Tags` wizard in v18 crashes when the company has a tax lock date configured, raising: ``` TypeError: '<' not supported between instances of 'bool' and 'datetime.date' ``` The error happens because `_compute_display_lock_date_warning` is evaluated while date_from is still False, so the comparison `wizard.date_from < tax_lock_date` ends up comparing a boolean with a date. In v17 the wizard form view included an invisible company_id field, which ensured the company was properly loaded in the cache and allowed `_compute_date_from` to run with the correct company_id and tax_lock_date before the warning compute was triggered. This change reintroduces the invisible company_id field in the wizard form view to restore the v17 behavior. The wizard now loads the company correctly, computes `date_from` based on the tax lock date, and then computes `display_lock_date_warning` without triggering the TypeError. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238005
This update fixes an issue where sharing a document via the list view didn't automatically open the preview. Now, the preview opens in the list view, similar to the kanban view, ensuring a consistent and user-friendly experience when accessing shared documents. This improves usability for users who primarily use the list view.
Original PR description
Bug === If the user has the list view as his default view, if we share him a document, the preview is not opened. After this commit, the preview is opened like in the kanban view, and the document is selected. Task-5361212 Forward-Port-Of: odoo/enterprise#100716
1 change
Resolved issues and error corrections
This update resolves an issue where document previews were not loading correctly when accessed through the 'Activities' icon. The fix ensures the correct custom document view is loaded, guaranteeing that all features, including previews, function as expected regardless of navigation method.
Original PR description
When navigating to documents from the 'Activities' systray icon, the system would load an action that correctly filtered for "My Activities" but lacked the specific view definitions of the main Documents app. This caused the 'List' view-switcher to load the default list view instead of the custom one, breaking features like document preview that depend on the custom view's JavaScript. This patch fixes the issue by ensuring that the correct, custom view definitions from the main Documents app are loaded. This guarantees that the custom list view and all its features work correctly, regardless of how the user navigates to it. This ensures the correct custom list view is loaded while preserving the "My Activities" filter. Task-5187045 Forward-Port-Of: odoo/enterprise#102593 Forward-Port-Of: odoo/enterprise#98979
1 change
Resolved issues and error corrections
This update resolves an issue where document previews weren't loading properly when accessed through the 'Activities' icon. The fix ensures the correct custom document view is loaded, allowing features like document previews to function as intended. This improves the user experience for accessing and viewing documents.
Original PR description
When navigating to documents from the 'Activities' systray icon, the system would load an action that correctly filtered for "My Activities" but lacked the specific view definitions of the main Documents app. This caused the 'List' view-switcher to load the default list view instead of the custom one, breaking features like document preview that depend on the custom view's JavaScript. This patch fixes the issue by ensuring that the correct, custom view definitions from the main Documents app are loaded. This guarantees that the custom list view and all its features work correctly, regardless of how the user navigates to it. This ensures the correct custom list view is loaded while preserving the "My Activities" filter. Task-5187045 Forward-Port-Of: odoo/enterprise#102442 Forward-Port-Of: odoo/enterprise#98979
1 change
Resolved issues and error corrections
This update corrects a bug where the 'convert' option repeatedly appeared in the Todo breadcrumb after a task was created from a Todo. The fix hides the 'convert' cog menu when a project is assigned, preventing this redundant display and improving the user experience. This ensures consistent task management.
Original PR description
Steps to reproduce: - Create a Todo and convert into task using cog Menu option. - Todo is converted to task and is displayed. - Through breadcrumb go back to Todo - Try to convert it again Issue: - The converted todo is again converted (change of project etc) Fix: - Hiding the convert cog menu when a project is set. task-5075327 Forward-Port-Of: odoo/odoo#230031