Daily updates from Odoo
Friday, March 15, 2024
19 changes · saas-17.1
Enhancements to existing features
This update enhances the Odoo system by adding a log message to confirm when a data module has successfully been imported into the database. Previously, no log notification was provided upon completion, making it harder to track import successes. This improved logging provides greater visibility and confidence in the data import process.
Original PR description
Before this commit, there was no message in the logs when the import of a data module is finished. This commit adds a log info to state that the module is now in the db. Forward-Port-Of: odoo/odoo#157687
Resolved issues and error corrections
This update corrects a previous issue where users could set time off types directly on accrual plans within the system's list views. We've removed this option to simplify the accrual plan configuration process. This change ensures a cleaner and more straightforward experience for managing accrual plans.
Original PR description
In rework of accruals plan, we removed the possibility to set a time off type on the accrual plan directly. The field has been removed from the form view, but not from the list view. 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#157366
This update optimizes the process of reconciling accounts by adding a database index. This change speeds up the deletion of records during reconciliation, leading to faster and more efficient account reconciliation operations. The change was driven by a performance issue identified in a previous request.
Original PR description
## Description Add missing index on FKey `tax_cash_basis_rec_id` to speed up deletion of `account.partial.reconcile` records during reconciliation. It's `btree_not_null` as the relationship is sparse. ## Reference opw-3649801 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157415
This update fixes an issue where currency fields weren't correctly displayed within spreadsheets when linked to a list view. The problem stemmed from a previous change and has been resolved, ensuring accurate currency formatting and names are now consistently shown. This improves the reliability of financial data within spreadsheets.
Original PR description
Get to a list view where there's a monetary field AND the related currency field in the same list. Then insert the list in a spreadsheet. => Either the currency format is not fetched or the currency name, depending on the order in the list. bug introduced by 8777973e opw-3770057 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157623
This update fixes a potential issue where reports could be generated in a random order. Previously, the system didn't guarantee a consistent order, which could lead to confusion for users. This change ensures reports are always generated in the same order, improving predictability and reliability.
Original PR description
Before this commit, ir.actions.report can be randomed orderer. @rco-odoo --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157031
This update ensures that when processing online payments for POS orders, the system now prioritizes the customer associated with the order over the logged-in user or a general public user. This change improves the accuracy of payment tracking and reporting for POS transactions, particularly when customers are purchasing through the online portal.
Original PR description
Before this commit: POS online payments uses the logged-in user or the public user, even when a POS order customer might also be present. After this commit: We check the partner_id for POS orders and give it precedence over both the logged-in user and the public user. task-3805695 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157562
This update resolves an issue where font styles differed depending on whether users selected Google fonts or served them locally. The fix adds a necessary parameter during font download, ensuring consistent font rendering across all website styles. This improves the user experience and visual consistency.
Original PR description
[This other commit] introduced a method to serve Google fonts from the local server. Then it has been back-ported to previous versions with [this commit]. Unfortunately, the font was not identical…
[This other commit] introduced a method to serve Google fonts from the local server. Then it has been back-ported to previous versions with [this commit]. Unfortunately, the font was not identical when the user chose to load the font from Google servers versus from the local server. This discrepancy was due to a missing parameter when downloading the font file to serve it from the local server. This commit fixes the issue by adding the missing parameter. Steps to reproduce the issue fixed by this commit: - Drop a text block onto a website page. - Make the text bold. - Go to the theme tab. - Change the font to https://fonts.google.com/specimen/Poppins => The text style changes depending on whether you checked the "Serve font from Google servers" option or not. [This other commit]: https://github.com/odoo/odoo/commit/b06ce21eba6388ce34bbffffadcb489f0e8557dd [this commit]: https://github.com/odoo/odoo/commit/04ab4e255b7fef1608ee2c70a3a005f3064bc4f3 opw-3775683 Forward-Port-Of: odoo/odoo#157734
The website's search snippets were appearing invisible due to a color mismatch. This update introduces a new setting to ensure the snippets have a visible border and distinct background color, aligning with other search bars within Odoo apps. This improves the user experience when adding search snippets to webpages.
Original PR description
Since this commit [1], the two searchbar snippets are broken. The search bar input seems invisible because it shares the same color as the default snippet background and has no border. This style…
Since this commit [1], the two searchbar snippets are broken. The search bar input seems invisible because it shares the same color as the default snippet background and has no border. This style matches the search inputs used in apps (like the "/shop" search bar), which isn't affected by the "Input fields" settings in the "Theme" tab. To resolve this issue, this commit introduces a new option to choose between the "light" style (similar to "/shop" search bars) and the "default input style" for the 2 "Search" snippets. The "default input style" is automatically applied when the "Search" snippet (excluding saved snippets) is dropped to address the issue caused by the light-on-light color scheme. Steps to Reproduce the Issue: - While in Website edit mode, drag and drop a "Search" snippet onto the page. - Bug: The input appears invisible due to the lack of a border and a background color identical to the snippet's section color. [1]: https://github.com/odoo/odoo/commit/6b1d11a60d8e70b33c63da860bb81b015ce5ea20 task-3662985 Forward-Port-Of: odoo/odoo#154435
This update fixes an issue where the 'My' filters weren't appearing at the top of the timesheet search view. The change reordered the filter placement to ensure users can quickly find timesheets related to themselves. This improves usability and efficiency for managing timesheets.
Original PR description
Steps to reproduce: - Install timesheets - click on all timesheets - open search view Issue: - in search view 'my' filters block should be at the top of the list Cause: - misplacing of the name month filter causes the issue. Solution: - if we replace that filter below the group then the issue will be solved. task-3772684 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#155714
This update resolves an issue where creating a new provider with a specified journal would lead to errors when changing the provider's company. The fix prevents the creation of unnecessary related accounts, streamlining the process and improving data consistency.
Original PR description
During the copy of provider if the journal is set, it create a new account.payment.method.line, and if you change the company of the new provider you have an error when you try to create a new journal. https://www.odoo.com/web#model=project.task&id=3778226 opw-3778226 Forward-Port-Of: odoo/odoo#157715 Forward-Port-Of: odoo/odoo#149423
This update resolves an issue where the reconciliation widget incorrectly selected a partner when multiple partners shared the same name. Previously, the last created partner was always used, even if the payment originated from a different partner. Now, the system avoids selecting a partner when names are identical, ensuring accurate reconciliation reporting.
Original PR description
In a single database, you could have two partners who are called John Doe. Before this commit, any statement line where the partner_name was set with 'John Doe' would return the last one being…
In a single database, you could have two partners who are called John Doe. Before this commit, any statement line where the partner_name was set with 'John Doe' would return the last one being created, due to the _order attribute on res.partner model, even if the statement line was generated from a payment of the other 'John Doe' (ie first one created). With this commit, we ensure that the wrong partner is not selected, in case we cannot differentiate one from the other. Description of the issue/feature this PR addresses: In case you have two partners with the same name in your DB, and you import a bank statement having a payment from the first created partner, the reconciliation widget will display a filter matching invoices of the last created partn. Current behavior before PR: Last partner created is selected for the filter. Desired behavior after PR is merged: No partner is selected for the filter if we have multiple ones sharing the same name. Enterprise test PR: odoo/enterprise#57846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157470 Forward-Port-Of: odoo/odoo#155986
This update allows users to register payments against multiple invoices using the payment wizard. Previously, the wizard was limited to single invoices and specific payment types. Now, users can select any bank journal, even when processing payments for multiple invoices, improving payment flexibility.
Original PR description
Create an invoice to partner A, confirm Create an invoice to partner B, confirm From Invoice list view, select just one invoice and hit register payment It will be possible to only select journals having inbound payment method Now select both invoices and hit register payment It will be possible to select any Bank journal, even if both invoice payment should be incoming opw-3757686 Forward-Port-Of: odoo/odoo#157665 Forward-Port-Of: odoo/odoo#156578
This update corrects a visual issue where new product templates initially displayed 'Odoo - False' in the tab title instead of the expected 'Odoo - New'. The fix ensures that new product records correctly show 'Odoo - New' until a product name is entered, improving the user experience.
Original PR description
**Current behavior:** When creating a new product template record, the tab title will be *Odoo - False* until a new name is saved rather than *Odoo - New*. **Expected behavior:** When creating a new record in a form view, the tab title will be *Odoo - New* until the `name` field is filled out and the record gets saved (at which point it will be *Odoo - <name>*). **Steps to reproduce:** 1. Install `sale_management` and go to the product list view 2. Create a new product, observe the misnamed tab title **Cause of the issue:** In `product.template`'s _compute_display_name() method, some of the default values can have a 'False' (str) value which will evaluate to True (bool), setting the name to 'False'. **Fix:** Set the display_name field to a False (bool) value if the current record does not have a name field set. opw-3793588 Forward-Port-Of: odoo/odoo#157258
This update resolves an issue where product image reordering caused unexpected swapping or jumping of images. Now, images are correctly inserted and maintained in their relative order, and the main product image always remains in the first position, providing a more stable and intuitive experience for users browsing product listings.
Original PR description
This change fixes the unexpected behavior of product image reordering: 1. Previously, when moving an image to the first or last postion, it was swapped with the first or last image. Now, it is inserted in the first or last postion, while keeping the relative ordering of the other images unchanged. 2. Previously, the main image could be in any position, but as soon as it was reordered, it would jump to the first position. Now, the main image is always in first position. task-3581895 Forward-Port-Of: odoo/odoo#150207
This update addresses several critical issues within the Odoo spreadsheet component, ensuring smoother operation and data integrity. Specifically, it resolves problems with chart resizing, sheet deletion, and renaming sheets in read-only mode. This improves the overall user experience and stability of the spreadsheet functionality.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/bd0c9e005 [REL] 17.1.8 https://github.com/odoo/o-spreadsheet/commit/66c66a61d [FIX] figures: deleting a sheet will remove all figures https://github.com/odoo/o-spreadsheet/commit/3ceba1d93 [FIX] sheet_interactive: rename sheet in readonly mode https://github.com/odoo/o-spreadsheet/commit/c1bd3c971 [FIX] FiguresContainer: chart resizing broken
This update ensures that UTM tracking codes are correctly saved in cookies after a user accepts the website cookie bar. Previously, the cookie bar deactivated cookies, preventing UTM data from being captured. This fix resolves issues with tracking website traffic and accurately attributing sales through UTM links, especially when users navigate from marketing campaigns.
Original PR description
Current behavior: --- When the cookie bar is activated, the cookies are deactivated by default, unless you click on I agree. This prevents UTMs from being set in the cookies Steps to reproduce: ---…
Current behavior: --- When the cookie bar is activated, the cookies are deactivated by default, unless you click on I agree. This prevents UTMs from being set in the cookies Steps to reproduce: --- 1. Install website_sale and sale_management 2. Go to Settings/Website 3. Activate Cookies Bar 4. Go to Link Tracker 5. Create a new link 6. Set the url as .../shop and Medium as LinkedIn 7. Open a private tab 8. Go to the tracked URL 9. Click on I agree on the cookie bar 10. Buy a product 11. Go back to Sales 12. Find the last public user quotation 13. Go to other info 14. Medium is empty Cause of the issue: --- UTMs are read from the cookies. When you activate the cookie bar, the cookies are deactivated by default. So when you go to the tracked url, and it redirects you to the page, it doesn't put the info from the url in the cookies. Clicking on I agree doesn't resolve the issue because it doesn't reload the page. Fix: --- When closing the cookie bar, forcing the info in the URL to be stored in the cookies if the key is a UTM. opw-3681927 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157711 Forward-Port-Of: odoo/odoo#154924
This update improves the Spanish language support within Odoo by correcting and expanding translations. Specifically, the `l10n_es` module has been updated with new translations, ensuring that Odoo's Spanish-speaking users have accurate and comprehensive support. This enhances the overall user experience for our Spanish-speaking customers.
Original PR description
Enterprise: https://github.com/odoo/enterprise/pull/58700 Forward-Port-Of: odoo/odoo#157759
This update fixes a potential issue where discounts on subscription sales were being recalculated unnecessarily after the order was confirmed. This change ensures that discounts are calculated correctly and efficiently, improving the accuracy of subscription sales figures. The update includes a new test to verify this fix.
Original PR description
Add test to cover a problem fixed in `sale_subscription` opw-3740645 See also: https://github.com/odoo/enterprise/pull/58673 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157699
Code cleanup and technical improvements
This update refactors the stock account module to make it easier to manage inventory ownership checks. Previously, changes to ownership required extensive modifications; now, it's simpler to add new features and customizations related to inventory valuation based on owner. This improves the system's adaptability and future development.
Original PR description
This PR adds a refactoring of the owner_id check within the stock_account module. The purpose of this refactoring is to prepare for a custom module that will value inventory based on specific ownership. This refactoring allows for extending to the functions as needed. @qrtl Forward-Port-Of: odoo/odoo#157614 Forward-Port-Of: odoo/odoo#155694