Thursday, December 14, 2023
8 changes · 17.0
Resolved issues and error corrections
New mailing lists are now kept private unless someone chooses to show them in subscription preferences. This prevents audiences from seeing or subscribing to lists that were not intentionally published.
Original PR description
Purpose: - Changed the default value of 'Show In Preference' (is_public) field from true to false for preventing the automatic publishing of mailing lists. Task-3594678
Automated actions now skip read-only fields when choosing a default field to update. This prevents errors when users create actions on records such as stock move lines, making setup more reliable.
Original PR description
Before this commit, the default update_path even if the field was readonly, it weas returned. So, if you try to create an automated action on the stock.move.line model and try to add an action, the button return a traceback because the field is readonly. After this commit, the method that get the default update_path will also check if the field is not readonly. Bugfix Task-Id: 3624328 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 self-ordering settings no longer include an empty option in the mode selector. This prevents an unnecessary validation error when saving settings and makes configuration clearer for users.
Original PR description
In this pr we remove the blank choice in the self-ordering mode select. It's unnecessary and throws a validation error on saving settings. Task 3599144 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change updates automated tests across several Odoo apps so they no longer depend on optional demo data being present. This helps make quality checks more consistent and reduces false failures during development and release validation.
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
Editing supplier information views in Studio from a product form no longer triggers an error. The product filtering logic was adjusted so the setup is simpler and works reliably in that editing context.
Original PR description
How to reprodruce: 1) Go to product.template view form 2) Open Studio 3) Go to tab 'Purchase' tab 4) Edit list/form view of the seller_ids (supplierinfo) Before this commit, the domain on product_id of supplierinfo was using 'parent' as if already doing the filter on the view. Because of the complex domain in the string, a traceback was throw when editing supplierinfo view with studio on the product.template. After this commit, the domain on the python side is simpler. The domain for the view has been changed to not be dependent of the parent view, but of the context. Bugfix Task-ID: 3615851 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
This fix resolves an error that occurred when users tried to remove recurring products and recurrence settings from a quotation that had already been sent. Previously, the system would raise an error and prevent saving the changes. Now users can successfully remove recurring products from sent quotations without encountering errors.
Original PR description
### Version 16.0 ### Steps to reproduce: 1. Create a sale order with a non-recurring product. 2. Click on the send by email button then send email. 3. Add recurring product and recurrence in the sale order and save it. 4. Remove recurrence and recurring product from the sale order, then click on save manually. ### Issue: Error raised after removing both recurring products and recurring in quotation send state and not able to save the record. ### Cause: While saving the sale order, the recurring product is not deleted from the database, it is only removed from the UI. ### Solution: While updating the record, it does not check for recurrence and recurring products in the quotation sent state. (fixed point-4) task-3501381 Forward-Port-Of: odoo/enterprise#51659 Forward-Port-Of: odoo/enterprise#48277
Fixed the quick create view for field service tasks to properly display customer and worksheet template fields while hiding the project field. This ensures users can quickly create tasks with the relevant information visible without unnecessary project selection, improving the task creation workflow for field service operations.
Original PR description
In the field service task when we create a new task through quick create view, the project_id field is there that shows the current project and through the project sharing, customer and worksheet template fields are not visible when the project is "field services". this PR ensures that when the field services project is there, customers and worksheet template fields are visible in the quick create view and hide the project_id field. task-3247213 Forward-Port-Of: odoo/enterprise#52511 Forward-Port-Of: odoo/enterprise#39539
This update resolves a warning that was appearing at the end of the Field Service tour due to the final step being skipped. The fix ensures the last step is properly executed by adding a trigger attribute, improving the tour experience and eliminating error messages for users.
Original PR description
Before this commit, a warning is raised at the end of `industry_fsm_tour` tour because it ignores the last step because it is auto action. This commit adds `run` attribute in the last to trigger click event to avoid considering the last step has `auto`. runbot-24582 Forward-Port-Of: odoo/enterprise#51610