Odoo Changelog — 2025-02-26

Wednesday, February 26, 2025

42 changes · saas-18.1

Improvements(2)

Enhancements to existing features

[IMP] pos_restaurant: remove tax and total summary from split screen

PR #197282

Coresaas-18.1pos_restaurant

The restaurant point-of-sale split bill screen has been simplified by removing the tax and total summary. This makes the split bill view cleaner and reduces unnecessary information for staff during bill splitting.

Original PR description

In this commit:
==========
- We are removing the tax and total summary from the split screen.

task-4551695

#point-of-sale#restaurant#split-bill

[IMP] point of sale : simplify text on the reload data popup

PR #190392

Coresaas-18.1point_of_sale

The Point of Sale reload data popup now uses simpler, more user-friendly wording. This helps store staff better understand what is happening when data needs to be refreshed, reducing confusion during sales operations.

Original PR description

Description of the issue/feature this PR addresses:

I improved the information displayed to the user.

Current behavior before PR:
Explanation not user friendly

Desired behavior after PR is merged:

tqt 


---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#point of sale#popup#wording#usability

Bug Fixes(6)

Resolved issues and error corrections

[FIX] base: fix faulty logic in tests

PR #199448

Coresaas-18.1base

This update fixes a faulty automated test in the base module so it checks the intended record behavior correctly. It helps keep the test suite reliable and reduces false failures in development checks, with no expected impact on end users.

Original PR description

`test_15_o2m` was trying to check the result of an `in` query with False and False/id, however the id provided was the parent of a leaf, which should not return the parent itself, while the assertion right after checks that the parent is present in the result.
The test was passing as with demo data the first record in `leaves` didn't have a parent_id.

Runbot Error 135019

#tests#reliability#runbot

Other(34)

Miscellaneous changes

[FW][FIX] base: embedded action default domain

PR #197904

Coresaas-18.1base

Steps: - Set domain of an embedded action to false - this override the default value - Try to use the embedded action Actual result: - Error due to invalid domain Expected result: - Embedded action work and use empty domain as default opw-4529210 opw-4563505 Forward-Port-Of: odoo/odoo#196919

Original PR description

Steps:
- Set domain of an embedded action to false
    - this override the default value
- Try to use the embedded action

Actual result:
- Error due to invalid domain

Expected result:
- Embedded action work and use empty domain as default

opw-4529210
opw-4563505

Forward-Port-Of: odoo/odoo#196919

[FW][IMP] l10n_tr_nilvera: improve exception handling for connectivity issues

PR #198232

Description of the issue/feature this PR addresses: I improved the information displayed to the user. Current behavior before PR: Explanation not user friendly Desired behavior after PR is merged: tqt --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

`test_15_o2m` was trying to check the result of an `in` query with False and False/id, however the id provided was the parent of a leaf, which should not return the parent itself, while the assertion right after checks that the parent is present in the result. The test was passing as with demo data the first record in `leaves` didn't have a parent_id. Runbot Error 135019

Before this commit, when there's a call in a discuss conversation with many participants and the participants in sidebar are folded as an avatar stack, their short status (e.g. mute, deafen) were shown below avatar too. This is a problem because the avatar stack is so compact that there's no room to show the short status. This looks quite off. This commit fixes the issue by removing the short status in the avatar stack. To see the call status of participant, we can easily see it by expanding the call participants. When the discuss sidebar is compact, however, it always show a single call participant (= most recently active participant). There's room to show the short status, so it's shown there to help see whether the most recent participant starts screen-sharing or becomes mute/deaf. Before / After <img width="294" alt="Screenshot 2025-02-19 at 17 41 15" src="https://github.com/user-attachments/assets/a23938ba-0cb8-4bb9-ae38-8f7638ebe5d5" /> <img width="297" alt="Screenshot 2025-02-19 at 17 40 24" src="https://github.com/user-attachments/assets/ee545083-dbde-44f3-ba64-95c4d6a8a536" /> ------- This commit also fixes a small issue with the position of "+X" in the avatar stack when sidebar is compact: the "+X" being at the very top and overlapping avatars make sense when the avatar stack is a preview of avatars and the number is more important in this view than the avatars. This is the case in non-compact sidebar mode, as we can easily expand the call participants. In compact mode, however, the active participant is as important if not more than/as the counter. Overlapping the visibility of the single avatar is a problem. Putting the counter at the bottom, while better, hides the counter value so it has some drawbacks. This commit fixes the issue by putting the counter next to avatar in this specific configuration of compact sidebar with call participants. Before / After <img width="67" alt="Screenshot 2025-02-19 at 17 41 09" src="https://github.com/user-attachments/assets/f596e896-6b37-4bc8-b4bd-e92539ebaa67" /> <img width="51" alt="Screenshot 2025-02-20 at 11 08 43" src="https://github.com/user-attachments/assets/88f34855-b02c-4653-8621-63563f0731ed" />

Versions -------- - saas-17.4+ Steps ----- 1. Create a new product with a lot of variants; 2. publish it to the website; 3. edit the website home page to add a product carousel; 4. set it to display newest products & hide variants. Issue ----- Fewer than 16 products are displayed in the carousel. Cause ----- Unlike the other product filters handled in https://github.com/odoo/odoo/pull/189040, the "Newest Products" filter is defined in `data/data.xml`, and stored as a record. This means it doesn't use the `_get_products` method to perform the search, instead using the `_prepare_values` method from the `website` module. For obvious reasons, the method defined in `website` doesn't take the `hide_variants` parameter into account to get the correct amount of search results: https://github.com/odoo/odoo/blob/0f64298c871ffea088a4fe6255d19852c8348159/addons/website/models/website_snippet_filter.py#L102-L108 Instead it passes 16 `product.product` records to the `_filter_records_to_values` override in `website_sale`, where duplicate templates are filtered out, resulting in fewer than 16 product templates: https://github.com/odoo/odoo/blob/0f64298c871ffea088a4fe6255d19852c8348159/addons/website_sale/models/website_snippet_filter.py#L73-L76 Solution -------- When calling `super()._prepare_values` for stored `product.product` filters, temporarily square the usual limit for the search, and filter reduce to size later. This may still be inadequate when working with products with dozens of variants, but should cover most normal use cases without requiring drastic changes to filter templates or search domain in stable. On master, we could add a new filter specifically for `product.template`. opw-4302856 Forward-Port-Of: odoo/odoo#195857

Issue: ------ Case: User Settings menu is basically used to handle created users but when clicking on the `New` button within the User Settings the form view corresponding to that model i.e; `res.users.settings` will be opened which is an inappropriate behavior. Whenever a User is created that user will be reflected within that menu. There's no meaning of having `New` button when no user is created to handle. Solution: ----------- Some users do not have a user settings yet, so it is a perfectly valid use case to create one. We should not artificially prevent acceptable behavior in technical/admin menus. Steps to reproduce: ------------------------ 1. Create a database in version 16.0. 2. Go to `User Settings`. 3. Click On `New` button. Try making changes and save. 4. An Invalid Field `User` error will Occur. This is because there's a many2One field i.e; `user_id` within the tree and form views which is basically an existing user. The `New` button will open a form view with no User which is a must. And will cause the Invalid field error when trying to save any change. Ref: https://github.com/odoo/odoo/blob/16.0/addons/mail/views/res_users_settings_views.xml#L24 Ref Screenshot: ![image](https://github.com/user-attachments/assets/24373b6e-2d67-42f7-9506-24faa3021e41) Co-Authored By - @seb-odoo Forward-Port-Of: odoo/odoo#196844 Forward-Port-Of: odoo/odoo#193400

revert the commit as when we fetch archived warehouse's pos type it will raise error for other source or destination loction for newly created stock operation type like even functinally also there is no need to fetch archived warehouse's operation type. ``` quality Control cross Dock, Storage type ``` we got this error during upgrade : ``` File "/home/odoo/src/odoo/saas-17.4/odoo/sql_db.py", line 347, in execute res = self._obj.execute(query, params) psycopg2.errors.NotNullViolation: null value in column "default_location_src_id" of relation "stock_picking_type" violates not-null constraint DETAIL: Failing row contains (33, 0, 28, 56, null, null, null, 4, null, null, 1, 1, 1, QC, internal, at_confirm, FBAQC, ask, {"en_US": "Quality Control"}, null, f, f, t, null, f, null, 2024-10-16 05:14:53.18448, 2024-10-16 05:14:53.18448, optional, optional, no, optional, null, null, t, null, null, 2x7xprice, 4x12_lots, pdf, null, null, null, null, null, null, null, null, null, t, null). ``` due to this two fix: https://github.com/odoo/odoo/pull/151719/commits https://github.com/odoo/odoo/pull/175838/files so we need to avoid to fetch archived warehouse's picking type. ref: odoo/upgrade#6631 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#185244

**To replicate:** 1. Install a localization reports module (e.g. l10n_lu_reports) 2. Create two branches for the company in the localization: one with a different VAT, and another without VAT (it takes the same VAT as the closest parent with VAT) 3. In Accounting > Reporting > Tax Report 4. Select only the company with a different VAT. The button to export an XML is not enabled. 5. Select the parent company and the company without VAT. The button to export an XML is not enabled. **Issue:** In some Tax Reports and EC Sales Reports with branch companies, the additional buttons are not enabled properly, even when all companies with the same VAT are selected. **Expected behavior:** If all branches with the same VAT are selected, export buttons should be available. **Cause of the problem:** In the tax report handler and EC sales report handler, `_custom_options_initializer()` calls the function `_enable_export_buttons_for_common_vat_groups_in_branches()`, which should enable the buttons if branches with the same VAT are selected. When extending `_custom_options_initializer()`, the call to super happens before extra buttons are added. These additional buttons are not included in the call to `_enable_export_buttons_for_common_vat_groups_in_branches()`. **Fix:** Instead of calling the function in _custom_options_initializer, add an option key to check and enable export buttons. This check is now done in `get_options()`, using the same logic previously applied in `_enable_export_buttons_for_common_vat_groups_in_branches`. As `get_options()` is called after the custom options initializer, all buttons are enabled if all branches with the same VAT are selected. task-4061157 Forward-Port-Of: odoo/enterprise#79227

[FIX] documents: fix documents creation on documents 1. Fix reply with an attachment on message from existing document How to reproduce: - Go to the chatter of a document - Add yourself as a follower - Send a message from the chatter: you should receive an email - Reply to this email with an attachment You receive a delivery error message ("Address not found") and your reply doesn't appear in the chatter, nor your attachment. With this fix, the message with its attachment appears in the chatter and there is no delivery error message. 2. Fix sending a message with an attachment on a request How to reproduce: - Go to the chatter of a request - Send a message with an attachment from its chatter You get the error "The operation cannot be completed: This attachment is already a document." while the message with its attachment should be added in the chatter. With this fix, the message with its attachment appears in the chatter and the request remains to be fulfilled. 3. Error while uploading a requested document through activity popover How to reproduce: - As user A, create a requested document for User B - As user B, click on the activity of that request and upload a document You get the error "The operation cannot be completed: This attachment is already a document." while the uploaded file should be linked to the request. With this fix, the request is fulfilled, and you get no error. We solve those problems by not creating document by default when messages with attachments are posted on a document and delegate the creation of the documents to the _message_post_after_hook method for the case of a post on a folder alias. We have chosen that default behavior as in all uses case except the alias, we expect the attachment to be added to the chatter and not as a new document. TestMailGateway already tests that incoming mail with attachment on an alias create the related documents, and we introduce a test for each case described above in other commits. [IMP] documents: add a test on replying with an attachment on a document post We add a test that check that when answering a mail posted on a document with an attachment, that the attachment is added to the document and the message is posted on the document. We also modify slightly an existing test because a parameter given to _message_post_after_hook was incorrect. [IMP] documents: add a test on document type change when sending a message We add a test that check that when sending a message on a URL or a request document, it is not turned into a binary document. [IMP] documents: add a test that upload a document in the activity popover We add a test that upload requested document through activity popover. Task-3707821 Forward-Port-Of: odoo/enterprise#79271 Forward-Port-Of: odoo/enterprise#56779

Improvements(2)

[IMP] pos_restaurant: remove tax and total summary from split screen

[IMP] point of sale : simplify text on the reload data popup

Bug Fixes(6)

[FIX] base: fix faulty logic in tests

Other(34)

[FW][FIX] base: embedded action default domain

[FW][IMP] l10n_tr_nilvera: improve exception handling for connectivity issues

Improvements(2)

[IMP] pos_restaurant: remove tax and total summary from split screen

[IMP] point of sale : simplify text on the reload data popup

Bug Fixes(6)

[FIX] base: fix faulty logic in tests

Other(34)

[FW][FIX] base: embedded action default domain

[FW][IMP] l10n_tr_nilvera: improve exception handling for connectivity issues

[FIX] pos_loyalty: properly exclude special products

[FIX] pos_{, restaurant}: navbar in mobile view

[FIX] hr: prevent error while getting default departure date

[FIX] mail: only avatar stack on folded call participant in sidebar

[FIX] mail: discuss command palette image no stretch

[FW] PRHOOT 28

[FW][FIX] website_sale: use correct limit when filtering newest products

[FW][IMP] test_mail: add variable in test mail template to reuse them

[FW][FIX] point_of_sale: floating order dialog title translation

[FW][FIX] web_editor: adjust cursor behavior for links at line end

[FW][FIX] account: ignore missing tag

[FW][FIX] mail : Correct Usability Of User Settings

[FW][FIX] hr_timesheet : Recompute allocated hour for task

[FW][IMP] point_of_sale: customer display configuration

[FW][FIX] account: change JOIN to LEFT JOIN in account.placeholder_code SQL

[FW][FIX] pos_self_order: fix slow connection error when printing order

[FW][FIX] html_editor: properly position toolbar in `rtl`

[FW][IMP] point_of_sale: change amount fields to monetary

[FW][FIX] point_of_sale: apply pricelist in self-ordering process

[FW][FIX] point_of_sale: fetch active warehouse pos type only

[FW][IMP] hw_drivers: add logs for printing

[FW][FIX] pos_loyalty: multiple reward quantity

[FW][FIX] pos_restaurant: prevent unsyncing of split orders in tests

[FW][FIX] delivery_usps_rest: fix new API endpoints

[FW] PRHOOT 28

[FW][FIX] {account,l10n_be}_reports: enable export report buttons with branches

[FW][FIX] documents: fix reply with an attachment on message from existing document

[FW][FIX] sign: modal error on tour

[FW][FIX] mrp_workorder: clean workorder when updating picking type in QP

[FW][FIX] social_twitter: prevent an error when fetch account metrics

[FW][17.0][IMP] hr_appraisal, hr_appraisal_survey: record should be passed in t…

[FW][FIX] web_studio: display empty fields in (new) kanban editor

[FW][FIX] sale_stock_renting: Make rental_loc_id visible in res_company view

[FW][FIX] project_enterprise : Recompute allocated hour for task

[FW][FIX] l10n_mx_edi: correct the equivalenciaDR in multicurrency payment CFDIs

[FW][FIX] documents: fix multiple things in list view.

[FW][FIX] mrp_mps: cell display when overflow