Friday, May 16, 2025
6 changes · master
Resolved issues and error corrections
This change prevents website menu records from being automatically linked to the only website in a database when no link was intended. It avoids incorrect demo or setup data associations and reduces the need for manual workarounds.
Original PR description
The _default_website_id method was introduced to set website_id by default when only one website exists in the database. However, in demo data: if there is a single website (e.g., with ID 1), website_id would automatically be set to 1 — even in records where no website should be set. As a result, we were forced to explicitly write `<field name="website_id" eval="False"/>` in demo data to prevent incorrect associations, which is not desirable. To avoid this issue, we're removing the default website logic. task-4350420
This fixes Spanish Point of Sale tests to use the updated receivables field names from the follow-up accounting data. The change helps keep the Spanish POS module compatible with recent accounting field naming changes and avoids failures caused by outdated references.
Original PR description
2 fields name has been change in `account_followup.res_partner`: - `total_due`-> `total_receivable_due` - `total_overdue` -> `total_receivable_overdue`
This fixes an issue where the website editor could add hidden formatting markers inside protected or non-editable content. The change helps keep saved page content cleaner and avoids unintended artifacts in areas users are not supposed to edit.
Original PR description
Before this commit: - FeffPlugin adds padding to elements matching the selectors in selectors_for_feff_providers regardless whether their parents are contenteditable or not. The same plugin does not remove on save the FEFFs added to non-contenteditable elements. After this commit: - The FEFF plugin skips non-contenteditable elements. - The normalize handler of ProtectedNodePlugin is called before the normalize handler of FeffPlugin, to ensure that protected elements are marked as non-contenteditable before being processed by FeffPlugin. task-4795471
The HTML editor now handles cancelling link creation correctly. This prevents an error when users discard a newly created link, making the editing experience more reliable.
Original PR description
Since the changes from #206596, the discard button didn't work properly during link creation. On discard, the system tried to call `openLinkTools` on a link not connected to the editable document. We added a check to ensure the link was already present before edition to avoid this problem. task-4800555 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
List date range fields now keep a more consistent layout when users switch between viewing and editing records. This improves visual alignment and reduces distraction when working with date ranges in lists.
Original PR description
This commit fixes a layout issue where the start date in a list date range field had a noticeably different width between read and edit modes. The problem stems from list field inputs using width: 100%, which works for single inputs but causes imbalance when a field consists of two inputs (each taking 50% of the space). To resolve this, the autoresize hook is now applied to the start date input so it only takes up as much space as needed—matching the behavior of the span element in read mode. Additionally, an offset option was added to the autoresize hook to allow fine-tuning of the input width for more precise alignment. task-4751837
The planning interface now keeps the planned date range with allocated hours field at a consistent width. This prevents visual inconsistencies and makes scheduling information easier to read for users.
Original PR description
This commit takes advantage of changes made in https://github.com/odoo/odoo/pull/209075 to fix the same issue for the PlannedDateRangeWithAllocatedHours field as well. task-4751837