Wednesday, February 28, 2024
9 changes · saas-17.1
Resolved issues and error corrections
This update improves the clarity of tax labels within Odoo's Point of Sale, Sale, and Website Sale modules. The term 'VAT' has been replaced with 'Tax' to align with international standards and improve user understanding. This change ensures consistent and accurate reporting of tax information.
Original PR description
task-3653060 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where non-member users accessing live chat channels didn't receive messages. The previous behavior, which correctly subscribed non-members to channel events, has been restored. This ensures all users, regardless of membership status, receive relevant channel updates.
Original PR description
Since [1], accessing a live chat as a non member does not subscribe the user to the channel events. This results in the user not receiving any messages linked to this channel. This PR restores the previous behavior as removing it was not intentional. [1]: https://github.com/odoo/odoo/pull/154292 Steps to reproduce the issue: - Open a live chat with demo as a visitor - Connect as admin and go to live chat history - Open the chat with demo and the visitor - The thread is displayed in discuss - Send another message as the visitor - Admin does not receive the message Forward-Port-Of: odoo/odoo#154755
This update fixes an issue where the quantity returned in the returns wizard was incorrectly reflecting the full delivery quantity (10) instead of the delivered quantity (6). This change ensures that returns accurately reflect the actual amount of product returned, improving inventory accuracy and reducing discrepancies. The fix was triggered by a reported bug (opw-3726157).
Original PR description
**Steps to reproduce the bug:**
- Create a delivery picking:
- product: P1
- Qty: 10
- Mark as todo
- Set “Quantity” to = 6
- Validate the picking without creating a backorder
- return the picking
**Problem**:
The qty to return is 10 instead of 6
opw-3726157
Forward-Port-Of: odoo/odoo#155508This update fixes an issue where contact images on the Kanban view were cropped awkwardly, leading to a poor visual experience. By limiting the image height and centering it, the card now displays images more effectively, especially with the recent changes in how many-to-many tags are shown. This improves the overall presentation of contact information.
Original PR description
On the contact kanban view, add as much tags as possible. The point is to make the right hand part of the kanban card as tall as possible. Before this commit, the image (on the left hand side) of the…
On the contact kanban view, add as much tags as possible. The point is to make the right hand part of the kanban card as tall as possible. Before this commit, the image (on the left hand side) of the individual partner was taking all the space in the y-axis, which was on purpose, but the cropping of the image made it so that the image lost is sense: a face was too much cropped, or, if the image did not have sufficient pixel density, it was pixelized. What is specific to 17 that is barely applicable in earlier versions, is the changes in the display of many2many tags in the kanban record: they now take more space and at a faster pace. After this commit, we constrain that image to a maximum height and centering it. opw-3748585 opw-3751016 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#155359
This update fixes an issue where the ‘Verify VAT Numbers’ feature incorrectly marked EU VAT numbers as invalid when the VIES service encountered an error. Now, users will receive a notification if the VAT number couldn't be processed, preventing them from incorrectly assuming the number is invalid. This improves data accuracy and user confidence.
Original PR description
Steps to reproduce: - Activate "Verify VAT Numbers" option in the Settings - Go to Contacts and create a new one - Enter a valid EU VAT Number Issue: It happens that VIES service could not process…
Steps to reproduce: - Activate "Verify VAT Numbers" option in the Settings - Go to Contacts and create a new one - Enter a valid EU VAT Number Issue: It happens that VIES service could not process the VAT number for some reason and returns an error. That error is silently caught without notification to user and "Intra-Community Valid" field is set to False. The user will wrongly think that the VAT number is not valid, but it hasn't been processed at all. Here's the list of the potential errors returned by VIES service: - INVALID_INPUT - INVALID_REQUESTER_INFO - SERVICE_UNAVAILABLE - MS_UNAVAILABLE - TIMEOUT - VAT_BLOCKED - IP_BLOCKED - GLOBAL_MAX_CONCURRENT_REQ - GLOBAL_MAX_CONCURRENT_REQ_TIME - MS_MAX_CONCURRENT_REQ - MS_MAX_CONCURRENT_REQ_TIME Solution: Log a note with the error (as it is done for some other error) to warn the user that the VAT number hasn't been processed. opw-3687968 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#153196
This update fixes a limitation in the hr_gamification module where badges couldn't be assigned to users without a linked employee. The change removes a dependency between user and employee IDs, now allowing badges to be granted to any user regardless of their employee association. This expands the usability of the gamification feature.
Original PR description
When hr_gamification is installed, it's not possible to grant badges to users that don't have associated employees. Expected behavior: we should be able to grant badges to any users. This is because user_id was related field with employee_id. We remove that dependency. task - 3593382 Forward-Port-Of: odoo/odoo#155007
This update resolves a bug that prevented sales users from confirming sales orders containing 'expense' products. The fix bypasses access restrictions when generating analytic accounts for these orders, ensuring smooth order confirmation. This improves the usability of the sales order process for users with limited access.
Original PR description
Before this commit, when a salesman user without any access in other apps (just has the `sales_team.group_sale_salesman` group) creates an SO and adds a SOL for a product with…
Before this commit, when a salesman user without any access in other apps (just has the `sales_team.group_sale_salesman` group) creates an SO and adds a SOL for a product with `expense_policy='sales_price'` and then confirm the SO, he will got a traceback because he does not have access to `analytic.account.line` model. The reason is because an analytic account has to be generated for the SO since there is an expense product in its SOLs and so during the generated of analytic account a check is triggered to be sure the company set on that analytic account is correct. This commit adds a sudo before calling the search method in `analytic.account.line` model to do the check without checking the access right since the user does not really want to read the analytic account line. Steps to reproduce ================== 1. Log in as Salesman user (without other access) 2. Create a product and the expense policy to Sales price. 3. Create a SO and add a SOL with that product 4. Confirm the SO Expected Behavior ================= The SO should be confirmed without any issue (and an analytic account should set on that SO) Actual Behavior =============== Traceback is occured because the user cannot access to `analytic.account.line` model. Follow-up task-3256865 Forward-Port-Of: odoo/odoo#155238
This update resolves a crash that occurred when users attempted to create tables within the Odoo editor. Previously, applying the table command through the powerbox would cause errors and display an extra toolbar. Now, the tablepicker opens automatically when text is selected, creating tables smoothly without any issues.
Original PR description
**Current behaviour before commit:** When text is selected, 1. applying table command through powerbox throws error. 2. applying table command through powerbox makes toolbar appear along with tablepicker. **Desired behaviour after commit:** Now when text is selected, 1. applying table command through powerbox creates new table without any traceback. 2. applying table command through powerbox opens tablepicker only. task-3482230 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#155360 Forward-Port-Of: odoo/odoo#133414
This update ensures the translation file (POT) for the core 'base' module is current. Outdated translation files can lead to inconsistencies in localized versions of the software. This fix guarantees accurate translations for this foundational module.
Original PR description
Export pot of base module Entreprise: https://github.com/odoo/enterprise/pull/57503 Forward-Port-Of: odoo/odoo#155375