Wednesday, January 31, 2024
3 changes · saas-17.1
Resolved issues and error corrections
Fixed an issue where website form fields could remain visibly editable after changing the form's send settings and saving. This helps ensure saved website pages appear correctly to visitors and avoids confusing editor artifacts.
Original PR description
With commit [1], the ability to add property field inside a website form was implemented. In this case, some models have different fields available depending on the action they perform. E.g. if you…
With commit [1], the ability to add property field inside a website form was implemented. In this case, some models have different fields available depending on the action they perform. E.g. if you select "Create a task", depending on which project you choose to create a task in, different fields will be available. For that reason, the decision was made to destroy the SnippetEditors of existing fields, so that they would update their available fields. However, while we destroy the editors, we do not properly clean the DOM before destroying them. This can lead to editor elements still being in the DOM after saving. Steps to reproduce: - Drop a form snippet - Add a "selection" field - Change the email address on which the form will be sent to - Click on save => The selection field is still in editable mode This commit fixes that by properly calling `cleanForSave` before destroying the SnippetEditors. [1]: https://github.com/odoo/odoo/commit/5c08ac23 Related to task-3278975
This update restores two user navigation actions that could fail after an internal service change. Users can reliably open “My Account” from the user menu and trigger the home action without interruption.
Original PR description
Since [1], the rpc service no longer exists, and the rpc function can be directly imported. This PR adapts a forgotten usecase, accessible when clicking on "My account" in the user menu. [1] odoo/odoo@137c43d02a27aec8302f823d8e3a1f18599489a2 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 update fixes an issue in Manufacturing shop floor quality check dialogs caused by a recent technical change in how selection fields receive their settings. It helps prevent errors when users interact with related record fields during work order quality checks.
Original PR description
Due to commit [1] The props on context for m2o take an object but the shopfloor hasn't been adapted [1] https://github.com/odoo/odoo/commit/3670f78be767396f322ff3ebf068af5c2f547b36