Monday, March 10, 2025
6 changes · saas-18.1
Resolved issues and error corrections
The live chat feedback panel now respects page rules that hide the chat button, preventing visitors from starting a new chat where chats are meant to be unavailable. This keeps website behavior consistent with the configured live chat rules and avoids unwanted chat requests.
Original PR description
Before this PR, it was possible to start a new live chat while the rule for the page was "hide_button". The intent of this action is clear: prevent users from creating new chat on this page so we should not allow it throught the feedback panel.
Steps to reproduce:
- Setup a live chat rule ("/", "hide").
- Start a chat from the contactus page.
- Go to another page.
- Close the chat: a "new session" button is available while it should not.
This PR ensures this button is not shown with the "hide_button" rule.
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-prThis update fixes issues in how automated tests are selected and run, including a typo and problems with file paths containing dots. It helps maintain stable quality checks and reduces the risk of incorrect test runs during development and releases.
Original PR description
Fix a typo introduce in previous changes Backport a fix to restore test file behavior from 18.2 Fix test-file with dots in path
This change corrects how upgrade-related tests are matched so the right tests are selected during automated checks. It helps prevent missed or incorrectly selected upgrade tests, improving confidence in release validation without affecting end users.
Original PR description
For upgrade tests, the test modules can be imported from odoo.upgrade. The current solution is not correct since `test_module_path` would be `odoo/upgrade/module/tests/test_file.py` and so the condition `test_module_path.endswith(file_path):` would match `/upgrade/module/tests/test_file.py` (but not `/odoo/upgrade/module/tests/test_file.py`) whitch is not really expected. The problem is even more problematic in master with #195929 because the tag `/module/tests/test_file.py` won't match `odoo/upgrade/module/tests/test_file.py`
Opening the product catalog from a quotation no longer fails when a product has no category assigned. This helps sales users continue preparing quotations even when product data is incomplete.
Original PR description
Currently, an exception is raised when the user clicks on the catalog in a quotation if a product has no assigned category. Steps to Reproduce: 1. Install the sale_management module. 2. Navigate to…
Currently, an exception is raised when the user clicks on the catalog in a quotation if a product has no assigned category. Steps to Reproduce: 1. Install the sale_management module. 2. Navigate to Sales -> Configuration -> Settings. 3. Enable the Pricelists. 4. Open a new Pricelists -> Add a Price Rules with Apply To `Category`, select a category, and save. 5. Go to Products -> Products. 6. Open an existing product and remove its product category. 7. Go to Sales -> Orders -> New Quotation. 8. Select the created Pricelists, and click on Catalog. 9. An error occurs. Error: `AttributeError 'bool' object has no attribute 'startswith' ` This issue [1] occurs because when the user tries to access product category, the product category is not provided, as it is not a required field. [1] - https://github.com/odoo/odoo/blob/4bf8fc4c43ab7d8fd923aaaea8c6423c9a16e428/addons/product/models/product_pricelist_item.py#L481 This fix resolves the issue by ensuring that the product category exists before trying to access it. sentry-6320016916 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a Project app issue where a sub-task could incorrectly appear in a project's task board after being converted to a regular task and then back to a sub-task. Users now see task lists that correctly respect the option to show or hide sub-tasks.
Original PR description
Before this commit, when the compute method of the project_id field in `project.task` model is triggered, the compute method of `display_in_project` field is not triggered and so when a user converts…
Before this commit, when the compute method of the project_id field in `project.task` model is triggered, the compute method of `display_in_project` field is not triggered and so when a user converts a sub-task to a task and convert again the task into a sub-task, the display_in_project for that sub-task stays at True instead of being falsy as expected. This commit makes sure the compute of `display_in_project` field is triggered even if the one of the project_id is triggered since now the compute of project_id no longer depends on `display_in_project` field and so we will not have a dependency loop. Steps to reproduce the issue: ---------------------------- 0. Install Project app. 1. Create a project A 2. Create a task A on that project A 3. Create a sub-task B in task A 4. Go to the form view of sub-task B 5. Clear the parent_id field on that sub-task (to convert it into a task) 6. Set the task A as the parent task of sub-task B 7. Go back to the kanban view of tasks of Project A Current behavior: ---------------- The sub-task B is displayed in the kanban view even if the filter `Show sub-task` is not enabled Expected behavior: ----------------- The sub-task B should not be displayed in the kanban view if the filter Show sub-task is not enabled. opw-4597692
Manual starts of Odoo no longer produce noisy zero and one entries from LED status updates. This keeps startup logs easier to read and helps teams spot real issues faster.
Original PR description
Logs when odoo was started manually were polluted by zeros and ones due to recurrent echos to the led configuration file.