Odoo Changelog — 2025-05-20

Tuesday, May 20, 2025

18 changes · 18.0

Improvements(1)

Enhancements to existing features

modify many2many_tag_field to use tooltip when available

Core18.0web

Tag fields now show the available tooltip text when users hover over them, making extra context easier to access without changing the main screen. This helps users understand tag meanings or details more quickly in forms and lists.

Original PR description

https://github.com/odoo/enterprise/pull/85591

#tags#tooltips#usability

Bug Fixes(3)

Resolved issues and error corrections

[FIX] pos_restaurant: improve translatability

PR #210841

Core18.0pos_restaurant

Restaurant receipt wording is now translated as complete phrases instead of separate fragments, making translations more natural across languages. This also avoids confusion between restaurant tables and spreadsheet tables in translated text.

Original PR description

Do not use t-out/t-esc to build human-readable content. This is basically the same as string concatenation.

This commit wraps the entire string in a gettext call to prevent it from being split into several non-reorderable translations. As a lucky side effect, it also creates a separate translation for the word "table" (as in restaurant tables) which won't overlap with the translation for spreadsheet tables.

opw-4754410

#translations#restaurant#receipts

Documentation(1)

Documentation and clarification updates

[CLA] Signature for Ricardo-MC

PR #210625

Core18.0cla

This update records a signed contributor agreement for Ricardo-MC. It supports the project’s legal compliance by documenting permission for contributions to be included in Odoo.

#contributor agreement#legal#compliance

Other(13)

Miscellaneous changes

[FW][REV] account: make accounting fields not required

PR #210452

Core18.0account

Original PR description

This reverts commit d413a9895742594d064084cd6dafbf1f2ec97221. This fix was decided after https://github.com/odoo/enterprise/pull/74127 that was trying to prevent invoicing users to see accounting…

This reverts commit d413a9895742594d064084cd6dafbf1f2ec97221.

This fix was decided after https://github.com/odoo/enterprise/pull/74127
that was trying to prevent invoicing users to see accounting features,
when it seemed to be unwanted to have the two property accounts fields
required while having no CoA installed.

The issue is, now when having Accounting installed, we can create a user
without having CoA as these two fields are not required anymore, but
we end up with a error message when creating an invoice ('no CoA
installed') although we could be have added accounts manually instead
of installing a CoAi (which is not possible for invoicing user).
In this situation, we should be able to create a contact, and having these
fields required will force the user to create them.

Finally, it is ok to revert the full chain, as the original issue is
fixed by this commit https://github.com/odoo/enterprise/commit/68f6c1f9fd3ff6762c98e1a405ade035129efce0

Forward-Port-Of: odoo/odoo#210344
Forward-Port-Of: odoo/odoo#209832

Do not use t-out/t-esc to build human-readable content. This is basically the same as string concatenation. This commit wraps the entire string in a gettext call to prevent it from being split into several non-reorderable translations. As a lucky side effect, it also creates a separate translation for the word "table" (as in restaurant tables) which won't overlap with the translation for spreadsheet tables. opw-4754410

This reverts commit d413a9895742594d064084cd6dafbf1f2ec97221. This fix was decided after https://github.com/odoo/enterprise/pull/74127 that was trying to prevent invoicing users to see accounting features, when it seemed to be unwanted to have the two property accounts fields required while having no CoA installed. The issue is, now when having Accounting installed, we can create a user without having CoA as these two fields are not required anymore, but we end up with a error message when creating an invoice ('no CoA installed') although we could be have added accounts manually instead of installing a CoAi (which is not possible for invoicing user). In this situation, we should be able to create a contact, and having these fields required will force the user to create them. Finally, it is ok to revert the full chain, as the original issue is fixed by this commit https://github.com/odoo/enterprise/commit/68f6c1f9fd3ff6762c98e1a405ade035129efce0 Forward-Port-Of: odoo/odoo#210344 Forward-Port-Of: odoo/odoo#209832

Issue ===== In the test `test_stock_landed_costs_lots`, there is this `assertRecordValues`: ```python self.assertRecordValues(lc.stock_valuation_layer_ids.sorted('product_id'), [ {'lot_id': lot_product_b[0].id, 'product_id': product2.id, 'stock_valuation_layer_id': og_p2_layers[0].id, 'quantity': 0, 'value': 1.5}, {'lot_id': lot_product_b[1].id, 'product_id': product2.id, 'stock_valuation_layer_id': og_p2_layers[1].id, 'quantity': 0, 'value': 1.5}, {'lot_id': lot_product_a[0].id, 'product_id': self.product1.id, 'stock_valuation_layer_id': og_p1_layers[0].id, 'quantity': 0, 'value': 1}, {'lot_id': lot_product_a[1].id, 'product_id': self.product1.id, 'stock_valuation_layer_id': og_p1_layers[1].id, 'quantity': 0, 'value': 1}, {'lot_id': lot_product_a[2].id, 'product_id': self.product1.id, 'stock_valuation_layer_id': og_p1_layers[2].id, 'quantity': 0, 'value': 1}, ]) ``` This issue is sometime the records order is not the expected one. Cause of the issue ================== By doing `recordset.sorted('product_id')`, it will sort the records by compare their `product_id` records, using the python built-in `sorted`. The built-in `sorted` function simply check if record A is lower than record B, using the < operation. But in Odoo, comparing two recordsets is equal than comparing their ids as a `set`: ```python def __lt__(self, other): try: if self._name == other._name: return set(self._ids) < set(other._ids) except AttributeError: pass return NotImplemented ``` In python, the comparaison between two sets compares is a set is a subset of the other one, which means than: ```python {1} < {2} # is false {1} < {2, 1} # is true ``` So, comparing SVLs by their product won't sort them by their product's id. If we want to do that, we have to explicitly do it by passing a function as the `sorted` `key` argument. For more information, see: -https://docs.python.org/3/library/functions.html#sorted -https://docs.python.org/3/reference/expressions.html#comparisons runbot-build-error: 99086

Versions -------- - 17.0+ Steps ----- 1. Create a coupon that grants a discount; 2. add a second reward giving free products; 3. use a product tag to turn it into a multiproduct reward; 4. save program, generate coupons, and copy a code; 5. add the free product tag to two or more products; 6. go to eCommerce; 7. add any product to cart and go to checkout; 8. apply coupon code; 9. claim a reward. Issue ----- - Claiming a free product results in a traceback. - Claiming the discount does not apply the discount. Cause ----- Commit db3ffae3ef5a5 modified the reward claiming logic to allow for multiproduct rewards, but overlooked the possibility of the program having multiple rewards, multiproduct being one of them. It therefore passes all of the coupon's rewards to `_apply_reward`, which only expects a single reward. This is also a consequence of commit 6525d5fba40c, which moved part of the `claim_reward` logic to `pricelist`, without passing which reward was claimed to `pricelist`. Solution -------- Add an optional `reward_id` parameter to `pricelist`, letting it know which reward we intend to claim. opw-4778945 Forward-Port-Of: odoo/odoo#210214 Forward-Port-Of: odoo/odoo#209610

How to reproduce: - Install document in v17.0 with demo data - In the kanban view, upload an image in Marketing folder - The image is displayed as thumbnail in the kanban card - Upgrade to saas-17.4 - Open Document and go to marketing folder There is no thumbnail for the uploaded image. In v17, _compute_thumbnail_status write a False status when the thumbnail is updated because when it is trigerred the attachment is not yet created. So the thumbnail is present but its status is incorrect. It works in v17 because the status is ignored by the view for images but in v17.4, the status is not ignored and the thumbnail is then not displayed. This temporary fix allows already migrated user to see thumbnail (as the view could not be modified in stable without an upgrade). We force the status of the thumbnail to "present" when there is no status for a thumbnail of an image which should cover the case where the status was not updated after the thumbnail creation. We have chosen this solution as the thumbnail will be updated in the upgrade and the URL returns anyway a placeholder image if the image is not present. We modify some tests to check that the patch is applied. As the kanban test data includes an image with a False status, the patch turns automatically the status to "present". So instead of having the generic mime type thumbnail, we get the actual thumbnail of the image. We change the assertions accordingly to test the new behavior and test the generic mime type thumbnail in the pdf case of the test "document inspector: document preview". Task-4642866 Forward-Port-Of: odoo/enterprise#81558

**Steps to reproduce:** - Install Planning app - Set the type of view to Gantt - (Create a shift if there is none) - Click on `Publish` button - The period end date doesn't take the last day into account (time is 00:00) **Issue:** Gantt model default `_buildMetaData` computation behavior was changed multiple times during previous refactoring: Previously used: ``` export function computeRange(scale, date) { let start = date; let end = date; if (scale === "week") { // startOf("week") does not depend on locale and will always give the // "Monday" of the week... (ISO standard) const { weekStart } = localization; const weekday = start.weekday < weekStart ? weekStart - 7 : weekStart; start = start.set({ weekday }).startOf("day"); end = start.plus({ weeks: 1, days: -1 }).endOf("day"); } else { start = start.startOf(scale); end = end.endOf(scale); } return { start, end }; } ``` Which became: ``` export function getRangeFromDate(rangeId, date) { const startDate = localStartOf(date, rangeId); const stopDate = startDate.plus({ [rangeId]: 1 }).minus({ day: 1 }); return { focusDate: date, startDate, stopDate, rangeId }; } ``` **Fix:** Added `localStartOf` function in the context setup of PlanningGanttModel. To avoid overwriting current changes for other modules (which could be intended), this was done instead of : ``` export function getRangeFromDate(rangeId, date) { const startDate = localStartOf(date, rangeId); const stopDate = localEndOf(startDate, rangeId); return { focusDate: date, startDate, stopDate, rangeId }; } ``` related commits: https://github.com/odoo/enterprise/commit/d18639785e622d97102227103d62ddb3a2716be6 https://github.com/odoo/enterprise/commit/c175a848369057cc69596737dcd9d21dd24c9d5c opw-4580458 Forward-Port-Of: odoo/enterprise#85608

Improvements(1)

modify many2many_tag_field to use tooltip when available

Bug Fixes(3)

[FIX] pos_restaurant: improve translatability

Documentation(1)

[CLA] Signature for Ricardo-MC

Other(13)

[FW][REV] account: make accounting fields not required

Improvements(1)

modify many2many_tag_field to use tooltip when available

Bug Fixes(3)

[FIX] pos_restaurant: improve translatability

Documentation(1)

[CLA] Signature for Ricardo-MC

Other(13)

[FW][REV] account: make accounting fields not required

[FIX] stock_landed_cost: runbot error 99086

[FIX] l10_din5008: fix different font size for addresses

[FW][FIX] pos_sale: ignore payment term discount

[FW][PERF] stock: optimize _compute_rules

[FW][FIX] web_editor, website: prevent snippet tabs nav items removal

[FW][FIX] website_sale_loyalty: prevent traceback on multireward coupons

[FW][FIX] website_form_project: make project_id required in website form

[FW][FIX] mail: make partner presence test deterministic

[FW][FIX] industry_fsm_stock: set the price to 0 for under_warranty tasks in SOL

[FW][FIX] sign: prevent signing with whitespace-only name in auto mode

[FW][FIX] l10n_be_reports_prorata: xsd changed, rounding

[FW][FIX] documents: fix missing thumbnail after update

[FW][FIX] planning: ensure publish default_end_datetime covers full period

[FW][FIX] website_sale_renting: change default date calculation for hourly rentals