Thursday, September 26, 2024
17 changes · 17.0
Enhancements to existing features
This update reorganizes how sales order amounts are calculated so the logic is easier for developers to adapt and maintain. It should not change day-to-day sales workflows, but it helps reduce future customization effort and risk around order total calculations.
Original PR description
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
Resolved issues and error corrections
Tour guidance pointers now appear in the correct place when users need to scroll inside embedded modal content. This prevents confusing visual cues during guided walkthroughs and helps users follow onboarding steps more reliably.
Original PR description
Before this commit, the "tour pointers" that indicated to users that they needed to scroll the "snippets modal" were misaligned. Their position did not account for the iframe offset of the modal. task-4072655
Miscellaneous changes
In the Inventory Adjustments view, it is currently possible to select any user for a count request or assign any user to a specific stock.quant, even portal users. This fix ensures only stock users are selected. task 4207784 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181376
Original PR description
In the Inventory Adjustments view, it is currently possible to select any user for a count request or assign any user to a specific stock.quant, even portal users. This fix ensures only stock users are selected. task 4207784 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181376
Projects created from confirmed sales orders now correctly receive a project manager when a project template is used. This helps ensure ownership is assigned automatically and avoids follow-up work to fill in missing project managers.
Original PR description
Previously, when SO confirmed the default project manager remain unset. This commit adapts the functionality of setting the project manager if the template is included otherwise the manager remains unset. task-3953729
This fixes how the IBAN validation settings are applied when users add a bank account to a partner. It ensures the updated bank account entry flow continues to show and enforce the right IBAN-related fields, avoiding confusion or missing checks.
Original PR description
In 17.0 the add a line of the res.partner.bank is no longer adding a line directly in the list view but opening a wizard. The xpath of the base_iban was no longer working like it should. task:4197710 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Chilean invoices now show discount percentage and discount amount under the correct column headings. This prevents customers and staff from misreading invoice discounts when confirmed invoices are sent.
Original PR description
Steps to reproduce: 1. In the Chilean localization, create a new invoice with a discount. 2. Confirm and send. The behavior: The Discount Amount is displayed under the Discount Percentage, and vice versa. Why this was the case: The Discount table header was placed after the Price Unit header (`th_priceunit`), and its data was displayed after the Discount Percentage (`th_discount`). OPW-4112378
The mobile shopping cart now displays selected multi-option product attributes in the item description. This helps shoppers confirm their choices before checkout and reduces confusion on smaller screens.
Original PR description
Steps to reproduce: -go to shop -choose product which has multi option attribute -tick atleast one attribute -add to cart Issue: -multi option values are not visible in cart description in mobile view. Cause: -the issue caused due to use of d-none and d-md-block classes, due to this it will not show in small size devices. Fix: -replace d-none and d-md-block with empty string, so now the values will show for all devices. opw-3853263 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix changes how mail message composition loads related data so it fetches only the field currently needed. This reduces unnecessary background work and helps improve performance in mail and mass mailing workflows without changing user-facing behavior.
Original PR description
Overriding the _compute_field_value in order to only prefetch the currently requested field. opw-4213262
This fixes an invoicing crash in the Spanish point of sale when an optional Spanish e-invoicing component has been removed. Businesses can continue generating invoices without needing that optional module installed.
Original PR description
The `l10n_es_edi_facturae` module is auto-installed with Spanish localization, but is not a direct dependency of the `l10n_es_pos` module. And in case it (`l10n_es_edi_facturae`) is manually uninstalled, trying to generate an invoice will crash with: AttributeError: 'res.company' object has no attribute 'l10n_es_edi_facturae_certificate_id' This commit ensure the field is present before trying to use it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event website menus now work correctly on mobile when users open a nested submenu. This prevents the main dropdown from closing too early, making event navigation easier and more reliable on smaller screens.
Original PR description
In the multilevel dropdown, when the submenu dropdown is accessed within the parent dropdown, it closes the parent dropdown, making it inaccessible to the child dropdown menu. We don't want the BS dropdown to close when the sub dropdown is clicked Task-4037692
This update fixes a tooltip positioning issue in the Documents module's search panel. The change aligns the Documents tests with improvements made to the core platform, ensuring the search interface displays correctly and provides better user experience when hovering over search options.
Original PR description
This commit adapts documents tests to changes made in https://github.com/odoo/odoo/pull/180776
Since https://github.com/odoo/odoo/pull/121963, there are tooltips on search panel items when the user hovers them. However, it is not very convenient since the user needs to hover precisely the span which contains the item name for the tooltip to pop up. This commit simply moves up the data-tooltip attribute in the elements hierarchy so that it will show for the whole button instead of only the title. This also fixes a bug with the tooltip position in the charts of account search panel as a sid
Original PR description
Since https://github.com/odoo/odoo/pull/121963, there are tooltips on search panel items when the user hovers them. However, it is not very convenient since the user needs to hover precisely the span which contains the item name for the tooltip to pop up. This commit simply moves up the data-tooltip attribute in the elements hierarchy so that it will show for the whole button instead of only the title. This also fixes a bug with the tooltip position in the charts of account search panel as a side effect. task-3917084 Forward-Port-Of: odoo/odoo#180776
This change allows us to practically revive the 'real price' costing method via customization, specifically using the stock_valuation_fifo_lot OCA module. By making `qty_taken_on_candidate` adjustable in the `_run_fifo()` method, we can fine-tune the FIFO calculation to better suit real price costing needs. @qrtl QT4650 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180245
Original PR description
This change allows us to practically revive the 'real price' costing method via customization, specifically using the stock_valuation_fifo_lot OCA module. By making `qty_taken_on_candidate` adjustable in the `_run_fifo()` method, we can fine-tune the FIFO calculation to better suit real price costing needs. @qrtl QT4650 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180245
Instead of only allowing selection by limited account type, the system allows selection by group. 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#181327
Original PR description
Instead of only allowing selection by limited account type, the system allows selection by group. 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#181327
Issue: ===== Written html code inside the forum post gets rendered in the readonly view. Steps to reproduce the issue: ============================= - Create a new forum post - Write `<p>abc</p>` - Save - The `p` element disappears (it got rendered, you can check it by inspecting the element). Origin of the issue and solution: ================================= Let's first name the `p` element added by the editor as `pe` to differenciate between them. The issue is divided
Original PR description
Issue: ===== Written html code inside the forum post gets rendered in the readonly view. Steps to reproduce the issue: ============================= - Create a new forum post - Write `<p>abc</p>` -…
Issue: ===== Written html code inside the forum post gets rendered in the readonly view. Steps to reproduce the issue: ============================= - Create a new forum post - Write `<p>abc</p>` - Save - The `p` element disappears (it got rendered, you can check it by inspecting the element). Origin of the issue and solution: ================================= Let's first name the `p` element added by the editor as `pe` to differenciate between them. The issue is divided into 2 subproblems: - We need to save the correct value: currently if we have written in the editor `<p>abc</p>`, it will save the value `<pe><p>abc</p></pe>` which means that the two `p` element will be handled the same either both will appear as a string in the readonly view or will be rendered which is not right. To solve the issue, we need to override the `value` of the text area and not the html before the submit. By doing this the textarea.value will be equal to `<pe><p>abcdef</p></pe>` which is the correct value. - Now the second problem is when we edit the post , it will render again the `p` element that we wrote. The fetched template actually have the correct value inside the textarea, but seems like the browser when rendering it, it will convert the value to `<pe><p>abd</p></pe>` which is not right, and if we use textarea.html it will encode the `<pe>` element which is wrong too. To get the original value, we fetch if again and use it in the options of the wysiwyg. opw-4148163 Forward-Port-Of: odoo/odoo#179854
Monaco is sharing the same CoA as France, therefore we should use l10n_fr when installing account with a company from Monaco. opw-4197369 Forward-Port-Of: odoo/odoo#181333
Original PR description
Monaco is sharing the same CoA as France, therefore we should use l10n_fr when installing account with a company from Monaco. opw-4197369 Forward-Port-Of: odoo/odoo#181333
Situation: Field `ir.models.fields.field_description` has value `{"en_US": "Foo", "fr_FR": "", "nl_NL": "Baz"}` in database. When using `EXCLUDED.{quote(fname)}`, the value of keys `fr_FR` and `nl_NL` will be lost. Solution: Use `ir.models.fields.field_description || EXCLUDED.field_description` to overwrite part of the value instead of replacing the old value. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#18097
Original PR description
Situation:
Field `ir.models.fields.field_description` has value `{"en_US": "Foo", "fr_FR": "", "nl_NL": "Baz"}` in database. When using `EXCLUDED.{quote(fname)}`, the value of keys `fr_FR` and `nl_NL` will be lost.
Solution:
Use `ir.models.fields.field_description || EXCLUDED.field_description` to overwrite part of the value instead of replacing the old value.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#180970