Tuesday, March 25, 2025
8 changes · 17.0
Resolved issues and error corrections
Stages created in the To-Do app no longer disappear after reloading the page. They are correctly shown as personal stages when they are not linked to a specific project, helping users keep their task organization intact.
Original PR description
Steps: - create a stage from "To-Do" app - reload the page Actual result: - stage disappear Expected result: - stage is shown as personal stage opw-4637169
This update fixes unstable automated tests in the base automation area by waiting for the expected page content more reliably. It helps reduce random test failures in validation pipelines, making release checks more dependable without changing user-facing functionality.
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
The analytic distribution widget now correctly uses context settings defined on the field. This helps ensure accounting-related actions behave as configured and reduces errors in workflows that rely on those settings.
Original PR description
Description of the issue/feature this PR addresses: Previously, the `context` attribute set in the `analytic_distribution` field was not usable in the related `AnalyticDistribution` widget. For…
Description of the issue/feature this PR addresses:
Previously, the `context` attribute set in the `analytic_distribution` field was not usable in the related `AnalyticDistribution` widget. For example:
```xml
<field name="analytic_distribution" widget="analytic_distribution"
groups="analytic.group_analytic_accounting"
optional="show"
options="{'product_field': 'product_id', 'account_field': 'account_id', 'force_applicability': 'optional'}"
context="{'context_key': 'context_value'}" <!-- not usable in the widget -->
/>
```
Current behavior before PR:
The `context` was neither extracted nor propagated to relevant methods, causing issues in operations dependent on it.
Desired behavior after PR is merged:
This fix ensures that the `context` is properly handled and propagated throughout the component, enabling its use in ORM interactions and improving the widget's functionality.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update corrects how style values are generated for the web search panel, preventing broken CSS from being included in the application. It helps ensure the interface displays consistently and avoids visual glitches caused by malformed styling rules.
Original PR description
This commit fixes improper interpolation of SCSS variables assigned to CSS custom properties, leading to malformed generated CSS rules (i.e. `--my-prop: $my-value` in the CSS bundle). Quote from the SASS/SCSS documentation: > CSS custom properties, also known as CSS variables, have an unusual > declaration syntax: they allow almost any text at all in their > declaration values. (...) Because of this, Sass parses custom property > declarations differently than other property declarations. All tokens, > including those that look like SassScript, are passed through to CSS > as-is. The only exception is interpolation, which is the only way to > inject dynamic values into a custom property. Reference: https://sass-lang.com/documentation/style-rules/declarations/#custom-properties
This fix makes project-related sales item lookups more reliable by ensuring pending data updates are saved before the lookup runs. It helps prevent intermittent test failures and reduces the risk of inconsistent project profitability or sales information during processing.
Original PR description
Description of the issue/feature this PR addresses: Tests dependent on project.task's _get_sale_order_items method fail intermittently. This was noted while migrating a custom module from 15.0 to…
Description of the issue/feature this PR addresses: Tests dependent on project.task's _get_sale_order_items method fail intermittently. This was noted while migrating a custom module from 15.0 to 17.0 and ensuring it passed all tests. In debugging, it was noted that the project.task and sale.order.line records expected to be found by the query in project.project's _get_sale_order_items_query were in fact not present in the database despite the objects being accessible in the memory. This was confirmed by observing records in memory at a break point during test debugging as well as running SQL queries using the same debug environment. Current behavior before PR: Intermittent test failures at: - sale_project/tests/test_sale_project.py:143 - sale_project/tests/test_project_profitability:175 Desired behavior after PR is merged: Sale order items are correctly fetched by project._get_sale_order_items() regardless of whether there are pending computations and updates to the database. Tests mentioned above now pass as expected more consistently. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website searches using this result layout no longer trigger an unnecessary warning. This keeps logs cleaner for administrators without changing how search results appear or behave for users.
Original PR description
This commit fixes a warning raised each time a user runs a search on a website where the results are listed using the list_hybrid template from website/views/website_templates.xml. As the warning points out, the t-key directive is unused. **Warning prior to this fix:** Unknown directives or unused attributes: ["t-key"] in website.list_hybrid **Expected behaviour after this fix:** No more warning and no functionality is lost. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Branch companies can no longer open the Peru tax report, which was not intended for their use. This avoids confusing errors and ensures the report is only accessed by eligible main companies.
Original PR description
Accessing the tax report from a branch company raised a user error due to attempting to fetch tax group XML IDs using the company’s CID. While this could be resolved by using `self.env["account.chart.template"].ref`, the report isn’t intended to be shown for branch companies. Instead, a constraint was added to prevent access in such cases. opw-4569580
This update corrects how Studio styling values are inserted into generated stylesheets. It prevents broken visual rules from being produced, helping the Studio interface display consistently.
Original PR description
This commit fixes improper interpolation of SCSS variables assigned to CSS custom properties, leading to malformed generated CSS rules (i.e. `--my-prop: $my-value` in the CSS bundle). Quote from the SASS/SCSS documentation: > CSS custom properties, also known as CSS variables, have an unusual > declaration syntax: they allow almost any text at all in their > declaration values. (...) Because of this, Sass parses custom property > declarations differently than other property declarations. All tokens, > including those that look like SassScript, are passed through to CSS > as-is. The only exception is interpolation, which is the only way to > inject dynamic values into a custom property. Reference: https://sass-lang.com/documentation/style-rules/declarations/#custom-properties