Wednesday, January 3, 2024
16 changes · 17.0
Enhancements to existing features
The Settings page now includes a default search context so links from warning lists can take users directly to the relevant setting. This makes follow-up actions clearer and reduces time spent searching within Settings.
Original PR description
The Settings page lacks a default search context key, because it lacks the `<search>` arch. We add a context key to make actions target some specific settings. Needed for this PR, to point the user to the current Setting from a list of warnings (ActionableErrors widget): https://github.com/odoo/odoo/pull/142596
Resolved issues and error corrections
The demo payment popup was adjusted so it no longer clashes visually with the page header. This makes test checkout flows clearer and prevents users from seeing a confusing or obscured payment dialog.
Original PR description
prevent header overlap with `pay with demo` dialog
Miscellaneous changes
Minor fix: the background grid is not observed in the first place, setting a z-index on it should not be observed either. Noticed when fixing `automaticStep(Un)active()` at [1]. [1]: https://github.com/odoo/odoo/commit/c2d952689c97add74a372c90aa18787094d5d93a Related to task-3576046 Forward-Port-Of: odoo/odoo#146816
Original PR description
Minor fix: the background grid is not observed in the first place, setting a z-index on it should not be observed either. Noticed when fixing `automaticStep(Un)active()` at [1]. [1]: https://github.com/odoo/odoo/commit/c2d952689c97add74a372c90aa18787094d5d93a Related to task-3576046 Forward-Port-Of: odoo/odoo#146816
Fixes an issue where creating a new website form in Studio could crash when selecting a field. This keeps the website form editing flow usable when an expected internal form key is missing.
Original PR description
Steps to reproduce ================== Go to Maintenance > Studio > Website > New Form Click on the website editor Click on the name field UncaughtPromiseError > KeyNotFoundError Cause of the issue ================== Starting from 17, the FormEditorRegistry is not the legacy one. If the key is not present in the registry, it will fail, unless we pass a default value. In this case, the key `website_form_key` is false. Solution ======== Pass null as the default value. opw-3652423
The chat help command now shows its guidance without exposing formatting tags to users. This prevents confusing output in Mail and Live Chat and keeps support conversations looking polished.
Original PR description
Mismatch of str and Markup led to escaping everything. Now properly Markup code and escape the rest.
Spanish translation has been modified by commit bf81596aa7b36a9a08b9701a9fcdab3e30902349 This behavior makes spanish variant (maxico, uruguay, columbia, etc.) use the es_419.po instead of es.po. This commit renames the po files for the LATAM localizations so that translations work as expected. Initiated by customer issue: opw-3627465 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I h
Original PR description
Spanish translation has been modified by commit bf81596aa7b36a9a08b9701a9fcdab3e30902349 This behavior makes spanish variant (maxico, uruguay, columbia, etc.) use the es_419.po instead of es.po. This commit renames the po files for the LATAM localizations so that translations work as expected. Initiated by customer issue: opw-3627465 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 hides all module type choices in the module import interface so users are not shown irrelevant or confusing options. It helps keep the import workflow cleaner and reduces the chance of selecting an unintended module type.
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
Horizontal radio button choices now wrap onto additional lines instead of overflowing their container. This improves usability on mobile devices and narrow screens by keeping all options visible and accessible.
Original PR description
This PR adds the possibility for the `.o_horizontal` class to wrap, which is especially interesting in mobile. task-3580082 When using a `radio` widget, you can choose to use two options : -…
This PR adds the possibility for the `.o_horizontal` class to wrap, which is especially interesting in mobile. task-3580082 When using a `radio` widget, you can choose to use two options : - `horizontal` which will add a `.o_horizontal` class to the radios and allow them to display with a `flex-row` - `vertical` which will add a `.o_vertical` class to the radios and allow them to display with a `flex-column` Prior to this commit, the `.o_horizontal` class was not allowing elements to wrap, which would cause overflow issues on small devices. To fix this issue, we add a `flex-wrap` property to the class, to ensure that if the buttons are larger than the breakpoint, they will wrap and stay inside the container. | 17.0 | 17-0-fix-planning-alert-radio-btn-chgo | | ------------- | ------------- | | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/85e23989-8c40-4e1c-b165-106187acd088"> | <img alt="image" src="https://github.com/odoo/odoo/assets/128030743/4f751fd8-d91a-4d69-91ea-f23a16ff5a60"> |
Users can now edit tags in Documents without encountering an error. This restores the expected tag management workflow and ensures the edit form opens normally.
Original PR description
Steps to reproduce: =================== 1. Open Document 2. In the workspace column on hovering tags 3. Click on the setting icon 4. Click on Edit -> Traceback occurs Technical ========= The commit https://github.com/odoo/enterprise/commit/2254eb07fd42ec88341d9d7ac92f09a379c6fa55 adds specific form_view_ref to the action of the edit button which breaks when we try to edit the tag. After this PR ================= Now the traceback doesn't occurs and form view will load. Task-3576877
This update removes leftover code references that are no longer needed in the barcode scanning module. The detailed operation view was previously moved to a different location in the system, and this change completes that cleanup by removing the obsolete code that was trying to force that old view to display.
Original PR description
Since odoo/odoo#140898 the pickings detailed operation view has been moved to a smart button instead of showing in a picking tab. This included the removal of the `force_detailed_view` context since there was no longer a detailed view to force show. This commit removes some leftover references to this context within tests.
This update makes the appointment scheduling tests more reliable by fixing how they handle date selection when the calendar year changes. Previously, tests could fail when run around New Year because the date picker calculations weren't accounting for year transitions. This ensures tests run consistently regardless of when they're executed.
Original PR description
This commit adapts the tests to be more robust when the current year change to avoid error in test as the click on the datepicker is calculated and not fixed. Forward-Port-Of: odoo/enterprise#53538
**Steps:** - Open Field Service - Create a new task - At first, the product stat button shows the price as 0.00 - Add task name and customer - Save the task. - Check product stat button **Issue:** - Now, after saving the task, the product stat button will not have the price shown as it was displayed before. **Cause:** - The class o_field_empty is applied which has the property of display: none and hence the price field is not displayed. **Fix:** - The o_field_empty class is app
Original PR description
**Steps:** - Open Field Service - Create a new task - At first, the product stat button shows the price as 0.00 - Add task name and customer - Save the task. - Check product stat button **Issue:** - Now, after saving the task, the product stat button will not have the price shown as it was displayed before. **Cause:** - The class o_field_empty is applied which has the property of display: none and hence the price field is not displayed. **Fix:** - The o_field_empty class is applied at the wrong place, we need to apply the o_field_empty only when o_stat_text is applied. **Task:** 3394985 Forward-Port-Of: odoo/odoo#127248
**Steps:** - Open Field Service - Switch to the calendar view - Click on any task - Notice the space in the row of the worksheet template **Issue:** - There is a weird space between the title Worksheet Template and the template name **Cause:** - Due to the long name of Worksheet Template, it moves to the next line but occupies a certain amount of space around it **Fix:** - By giving flex-wrap, the content is displayed properly **Task:** 3394985 Forward-Port-Of: odoo/odoo#1280
Original PR description
**Steps:** - Open Field Service - Switch to the calendar view - Click on any task - Notice the space in the row of the worksheet template **Issue:** - There is a weird space between the title Worksheet Template and the template name **Cause:** - Due to the long name of Worksheet Template, it moves to the next line but occupies a certain amount of space around it **Fix:** - By giving flex-wrap, the content is displayed properly **Task:** 3394985 Forward-Port-Of: odoo/odoo#128035
Current behaviour: --- When changing the text color in the document layout of the company to one of the first row colors, the text stays black in the preview of the document. Steps to reproduce: --- 1. Go to Settings 2. Click on Configure Document Layout 3. In Company Details, highlight the text 4. Change the font color to any of the first row 5. (By example the color #35979c) 6. The text color in the preview is still black 7. (Same when exporting to PDF) Cause of the issue:
Original PR description
Current behaviour: --- When changing the text color in the document layout of the company to one of the first row colors, the text stays black in the preview of the document. Steps to reproduce: --- 1. Go to Settings 2. Click on Configure Document Layout 3. In Company Details, highlight the text 4. Change the font color to any of the first row 5. (By example the color #35979c) 6. The text color in the preview is still black 7. (Same when exporting to PDF) Cause of the issue: --- The css code for colors in top row (o-color-1 to 6) is generated in web_editor (.text-o-color-1 to 6) and was not in the report_assets_common bundle See: https://github.com/odoo/odoo/blob/01b42c7d76c814e13325f8880dc9de765b0f43c8/addons/web_editor/static/src/scss/web_editor.common.scss#L662 opw-3360456 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#136566
Before this commit, since we are no longer in 2023, the test failed because there is no longer 2021 in the filters dynamically added in the dropdown of the date filter. The reason is now we have the current year, the previous one, and the one before, that is, 2024, 2023, 2022. This commit adds a patchDate to be sure we will start the test in 2023, to get the expected filters displayed (2023, 2022, 2021). Forward-Port-Of: odoo/odoo#147862 Forward-Port-Of: odoo/odoo#147824
Original PR description
Before this commit, since we are no longer in 2023, the test failed because there is no longer 2021 in the filters dynamically added in the dropdown of the date filter. The reason is now we have the current year, the previous one, and the one before, that is, 2024, 2023, 2022. This commit adds a patchDate to be sure we will start the test in 2023, to get the expected filters displayed (2023, 2022, 2021). Forward-Port-Of: odoo/odoo#147862 Forward-Port-Of: odoo/odoo#147824
- Replaces a randomly failing test by a simpler test. As reported by XDO (https://github.com/odoo/odoo/pull/123237#discussion_r1410620206), executing web requests asynchronously during the execution of a tour which does an RPC is randomly failing. The fix consists in not testing the full online payment flow with the cashier frontend interface, but instead simulate an order saved on the server and simulate real customer web requests for paying online for that order. - Simplifies the way payme
Original PR description
- Replaces a randomly failing test by a simpler test. As reported by XDO (https://github.com/odoo/odoo/pull/123237#discussion_r1410620206), executing web requests asynchronously during the execution of a tour which does an RPC is randomly failing. The fix consists in not testing the full online payment flow with the cashier frontend interface, but instead simulate an order saved on the server and simulate real customer web requests for paying online for that order. - Simplifies the way payment portal URLs are build. task-id: 3632217 Forward-Port-Of: odoo/odoo#145595