Tuesday, May 19, 2026
8 changes · saas-18.4
Resolved issues and error corrections
Leads created from the livechat /lead command now correctly include the contact details of logged-in visitors. This helps sales teams identify and follow up with the right customer without manually filling in missing contact information.
Original PR description
**Current behavior before PR:** When using the `/lead` command in livechat and the visitor was a logged-in user, the contact details on the lead were not set in the lead. **Desired behavior after PR is merged:** When using the `/lead` command in livechat and the visitor is a logged-in user, the contact details on the lead are now properly set. task-4992486 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix stops certain scheduled maintenance and automation tasks from reporting misleading progress when they are not processing a true queue. This helps avoid repeated retries of the same failed work and makes job handling more reliable.
Original PR description
Base automation and autovacuum should not log progress as this is makes the job scheduler think that something progresses and can be retried leading to the same error because we process the same (all) items. In general, progress numbers are only relevant for jobs that act as job queues. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264684
This fix ensures website date fields are handled correctly when pages are translated. It prevents users from accidentally editing date text in blog translation mode, reducing the risk of save errors and broken translated content.
Original PR description
The plugin `DateTimeFieldPlugin` was only added in registry `builder-plugins`. But it should also be included in the lists `CORE_PLUGINS` of `html_builder` and `TRANSLATION_PLUGINS` of `website` (the same as `MonetaryFieldPlugin` and similar plugins) Steps to reproduce: - Open `/blog` in translate mode - Click on a date - Bug: you can edit the text (and it will likely cause an error on save) task-6226376
Renaming a custom field that is inherited now first removes the automatically generated inherited fields from the database. This prevents leftover field records from causing errors or inconsistencies when businesses update customizations.
Original PR description
When renaming a custom field that is inherited, first remove the generated inherited fields from the database. backport of https://github.com/odoo/odoo/pull/240603 opw-6148175 Forward-Port-Of: odoo/odoo#264044
This fix resolves an issue where Knowledge articles appeared narrow when printed or exported due to a CSS rule affecting form views. The change specifically targets the Knowledge editor, ensuring articles are rendered correctly regardless of screen size or zoom level, improving readability and export quality.
Original PR description
Currently, a CSS rule forces the form container width to 1px to ensure that the nested list view can correctly compute its size. See: ```scss .o_form_view.o_xxl_form_view { .o_form_view_container {…
Currently, a CSS rule forces the form container width to 1px to ensure that the nested list view can correctly compute its size.
See:
```scss
.o_form_view.o_xxl_form_view {
.o_form_view_container {
width: 1px; /* List view needs a width value to recompute the size correctly */
}
}
```
However, since the Knowledge editor is implemented as a form view, this rule also affects Knowledge. When zooming out, the `o_xxl_form_view` class is added to the form view container, causing the rule to apply. If an article is printed while this class is present, it is constrained to an extremely narrow column, making it unreadable.
Steps to reproduce:
1. Open an article in Knowledge
2. Zoom out using `Ctrl` + `-`
3. Open the kebab menu and select "Export"
=> The article is rendered in a very narrow column.
To address this issue, we override this rule specifically for Knowledge. With this change, articles are now rendered correctly when printed or exported as PDF.
Task-5999878
Forward-Port-Of: odoo/enterprise#103259This update resolves a discrepancy in how contract type IDs are defined within Odoo's payroll modules. Specifically, the definition was standardized across the base and Belgium-specific versions. This ensures accurate payroll calculations and reporting for Belgian users.
Original PR description
[IMP] hr_contract_salary: fix contract_type_id definition The definitions of the contract_type_id in hr_contract_salary_offer and l10n_be_hr_contract_salary/hr_contract_salary_offer should be same I converted the definition of contract_type_id in the base module to the Belgium one. Also, the contract_type_id was inserted to the view in Belgium one as well, I deleted that part to prevent double appearance. This task is only for v.17, after this version I will open a new PR to handle them. Do not forward the task after v.17 (only for v.17) task - 6101717 Forward-Port-Of: odoo/enterprise#117307 Forward-Port-Of: odoo/enterprise#113244
This update corrects a problem where portal users could inadvertently delete documents they shouldn't have. The fix ensures that portal users can only delete documents they own, preventing unintended data loss during the system's automatic cleanup process. This improvement enhances data integrity and user control.
Original PR description
Reproduce: with rpc call as portal user, you can archive documents you have access to. This is not desired as this may lead to records being deleted when the cron collects the trash, but we only wanted to support portal users deleting only records they own. What we did when calling toggle_active should be done for all calls to `write` with `active`. It also removes the need for `_raise_if_unauthorized_archive` and `_unlink_except_unauthorized`. Task-6205627 Forward-Port-Of: odoo/enterprise#116886
Documentation and clarification updates
This pull request adds QoQa's signed corporate contributor agreement to Odoo's records. It supports legal compliance by documenting that QoQa can contribute code under Odoo's contribution terms.
Original PR description
Description of the issue/feature this PR addresses: This is the corporate CLA for QoQa. I backported #262581 because we need it from 18.0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#262582