Wednesday, August 21, 2024
25 changes · 17.0
Enhancements to existing features
This work-in-progress change adds a new capability intended to help the Helpdesk app compare similarity between items, which could support better matching or suggestions in future workflows. Because it is marked as testing-only and incomplete, the immediate business impact is limited until it is finalized.
Original PR description
This is a work in progress, and is just for testing purposes. Don't review it pls ty :).
Resolved issues and error corrections
Deleting a parent website menu now also removes its child menus in the correct order. This prevents an error during saving and helps editors manage website navigation reliably.
Original PR description
Steps to reproduce: - Open website menu editor - Add a child menu to a menu - Delete the parent menu - Save Old behavior: a traceback appears New behavior: no traceback, parent and children menus are correctly deleted. This commit fixes the issue by properly deleting children menus recursively before deleting the parent. opw-4119441
Miscellaneous changes
Improving tax scopes and EC sales tax report tags for `l10n_at` Old PR: odoo/odoo#171606 Info: @wt-io-it Ticket link: https://www.odoo.com/odoo/project.task/3916300 opw-3916300 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#171702
Original PR description
Improving tax scopes and EC sales tax report tags for `l10n_at` Old PR: odoo/odoo#171606 Info: @wt-io-it Ticket link: https://www.odoo.com/odoo/project.task/3916300 opw-3916300 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#171702
This fixes an issue where signature frames could be partly hidden when a signature box had an unusual shape, such as very wide and short. Users signing documents will now keep the full frame and hash visible, helping signatures appear correctly and reliably.
Original PR description
Steps to reproduce: - Install Sign - Open Sign, add a document and put a signature box - Make the sign box have a weird aspect ratio (very short and super wide for example) Issues: When you sign with the frame, the frame will be partially hidden making the hash invisible. Solution: Put the container back just like in the 16.0, that way we don't have the weird CSS behavior that we had previously. opw-4042289
This fixes spelling and translation text for carryover constraint messages in the Accounting app. It helps users see clearer, more accurate messages when working with carryover rules, without changing the underlying accounting behavior.
Original PR description
Some spelling mistakes were forgotten in a previous pull request that meant to add constraints on carryover See https://github.com/odoo/odoo/pull/177064#pullrequestreview-2248102992 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Uruguay localization demo data was updated to avoid using real partner information. This helps protect personal data while keeping demo environments useful for testing and demonstrations.
Original PR description
Ticket: 1239 Adhoc-task: 41734 Description of the issue/feature this PR addresses: This task was created to modify the demo data for Uruguay, to avoid using real partner information. 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
Clearing an Odoo meeting from the calendar no longer triggers an error in debug mode. This makes calendar event management more reliable for users working with meeting links.
Original PR description
**Versions:** 17.0 **Steps to reproduce:** 1. Enable debug mode. 2. Go to the calendar. 3. Create an event using the quick create form. 4. Click on the Odoo meeting link. 5. Try to clear the meeting. **Issue:** A traceback occurs when attempting to clear a meeting in debug mode. **Cause:** The 'CopyButton' component expects the content to be a string but receives `false`. **Solution:** In the form controller, set `videocall_location` to an empty string instead of `false` in `beforeExecuteActionButton`. Task-4091314
The Mexico localization now uses a more appropriate default account for deferred expenses when installed. This helps companies using Mexican accounting settings align their setup with SAT account grouping guidance and avoid manual correction after installation.
Original PR description
Version: 17.0+ Current behavior: The default account for Deferred Expense on res.config.setting is "inappropriate". A new account should be established according to account codes by SAT mexico, http://omawww.sat.gob.mx/fichas_tematicas/buzon_tributario/Documents/codigo_agrupador.pdf Purpose of this PR: To introduce an appropriate account to be used for Deferred expenses and automatically selected upon l10n_mx installation. Steps to reproduce on Runbot: 1) install l10n_mx 2) Accounting Settings > incorrect account selected for Deferred Expense opw-4105993
A styling rule from Website Sale was too broad and accidentally affected Marketing Automation campaign cards, causing activity buttons to appear in the wrong place. The selector is now narrowed so Website Sale mobile styling no longer disrupts Marketing Automation screens.
Original PR description
Steps to reproduce =================== 1. Install website_sale module 2. Go to any campaign in marketing_automation 3. The kanban card of the activity will have buttons misplaced in the title Issue ================= With commit https://github.com/odoo/odoo/pull/165486/commits/f46e7e8bd6dc205d83a107f62d8b5944caa3d4d5, a style was applied for website_sale form mobile view. The selector also matched marketing_automation's campaign form view which removed the required float property from the element. After this commit ================= This commit makes the selector in website_sale more specific to match only the desired element. Task-4110902
The mobile shop product configurator now shows optional product details under the correct columns. This prevents confusing shifted information when customers add products with optional items to their cart, improving the mobile shopping experience.
Original PR description
Steps to reproduce: /!\ on mobile - Sale > Any Product > Sales tab - Add an optional product - Website > Shop > Select product - Add to cart Columns are misaligned with their data, the style that dictates which elements should display depending on screen width only applied to the table body, meaning we had 4 columns with only three data points to fill them, hence why everything is shifted over to the left. opw-4067850 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This pull request appears to make a small test-related update and fixes a previous change. It likely has minimal business impact and does not introduce a notable user-facing change.
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
This update adds support for the FedEx International Connect Plus shipping service type, which was previously missing from the available delivery options. This enables businesses using Odoo's FedEx integration to offer this international shipping method to their customers, expanding their delivery service capabilities.
Original PR description
before this commit: Service type `FEDEX_INTERNATIONAL_CONNECT_PLUS` was not available the list 'fedex_service_type'. After this commit: Missing service type is added in the list. reference fedex doc: https://developer.fedex.com/api/en-us/guides/api-reference.html#servicetypes opw-4061797 Forward-Port-Of: odoo/enterprise#64250
This update removes the display of empty IS (insurance) lines in Swiss payroll processing. The change improves the clarity of payroll documents by eliminating unnecessary blank entries, making payroll statements cleaner and easier to read for employees and administrators.
This update adjusts the Chart of Accounts report test in the Mexico localization module to account for a newly added account (173.01 Deferred expenses). The change ensures that the trial balance test continues to work correctly with the expanded chart of accounts structure.
Original PR description
Purpose of this PR: CoA Report trial balance test adjusted to accommodate for the new account, 173.01 Deferred expenses Community PR that adds new account: #176681 opw-4105993
- Intall website_sale_product_configurator - Create a product A with price 3 999.00 € - Add an optional product on product A - Go to shop page - Go to product A - Add to cart - A modal popup appear - Finelize cart --> Issue the price send to datalayer is 3. Because "3 999,00" is send in the json, endead 3999.00. Co-Authored-By: "Louis (loti)" <loti@odoo.com> Forward-Port-Of: odoo/odoo#177211 Forward-Port-Of: odoo/odoo#167962
Original PR description
- Intall website_sale_product_configurator - Create a product A with price 3 999.00 € - Add an optional product on product A - Go to shop page - Go to product A - Add to cart - A modal popup appear - Finelize cart --> Issue the price send to datalayer is 3. Because "3 999,00" is send in the json, endead 3999.00. Co-Authored-By: "Louis (loti)" <loti@odoo.com> Forward-Port-Of: odoo/odoo#177211 Forward-Port-Of: odoo/odoo#167962
Before this PR, simple notifications did not have options for 'success' or 'info' type border color themes. This PR allows users to send simple notifications with 'success', 'info', 'warning', and 'danger' border color schemes. If the warning or type parameter is not provided, it will default to the 'danger' type, as it did before this PR, so it will not affect any previously written bus notification call. Desired behavior after PR is merged: This PR enables simple notifications to use 's
Original PR description
Before this PR, simple notifications did not have options for 'success' or 'info' type border color themes. This PR allows users to send simple notifications with 'success', 'info', 'warning', and 'danger' border color schemes. If the warning or type parameter is not provided, it will default to the 'danger' type, as it did before this PR, so it will not affect any previously written bus notification call. Desired behavior after PR is merged: This PR enables simple notifications to use 'success', 'info', 'warning', and 'danger' type border color schemes. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#177323
This PR addresses issues with the custom amount selection on the `/donation/pay` page, which has been present since version 15.0. Users have experienced confusion about the actual donation amount due to the following bugs: **Bug 1:** Multiple amounts could be selected simultaneously, affecting versions 17+. **Bug 2:** The last selected amount was not the actual amount donated, affecting all versions from 15 onwards. **Fixes:** - This PR fixes Bug 1,2 in version 17.0+. - During the for
Original PR description
This PR addresses issues with the custom amount selection on the `/donation/pay` page, which has been present since version 15.0. Users have experienced confusion about the actual donation amount due to the following bugs: **Bug 1:** Multiple amounts could be selected simultaneously, affecting versions 17+. **Bug 2:** The last selected amount was not the actual amount donated, affecting all versions from 15 onwards. **Fixes:** - This PR fixes Bug 1,2 in version 17.0+. - During the forward-port to master the patch will be removed task-4115678 Forward-Port-Of: odoo/odoo#177189 Forward-Port-Of: odoo/odoo#176722
Issue: Signature command doesn't work in 16.0 and raises an error in 17.0+ Steps to reproduce the issue: - install website - add forum in the website - create a new post in the forum - add signature - (nothing happens in 16.0, error in 17.0) Origin of the issue: ==================== The session in the forum post view doesn't have `uid`. Solution: ======== Use `session.user_id` instead of `session.uid` which works in forum as well as in other apps. opw-4066436 Forward-Port-
Original PR description
Issue: Signature command doesn't work in 16.0 and raises an error in 17.0+ Steps to reproduce the issue: - install website - add forum in the website - create a new post in the forum - add signature - (nothing happens in 16.0, error in 17.0) Origin of the issue: ==================== The session in the forum post view doesn't have `uid`. Solution: ======== Use `session.user_id` instead of `session.uid` which works in forum as well as in other apps. opw-4066436 Forward-Port-Of: odoo/odoo#175573
Steps to reproduce the issue: ============================= - Install website and events - Go to events page and enable editor - Click on customize and enable sidebar - enable Follow us option - Select a social media icon and enable open in a new window option - Save - Click on the updated icon, it still opens in the same page => the changes aren't saved. Origin of the issue: ==================== The `target` attribute was ignored when saving and `arch_section`. Solution =======
Original PR description
Steps to reproduce the issue: ============================= - Install website and events - Go to events page and enable editor - Click on customize and enable sidebar - enable Follow us option - Select a social media icon and enable open in a new window option - Save - Click on the updated icon, it still opens in the same page => the changes aren't saved. Origin of the issue: ==================== The `target` attribute was ignored when saving and `arch_section`. Solution ======== Add `target` attribute to the allowed root attrs. opw-4077657 Forward-Port-Of: odoo/odoo#177035
Before this commit, the user would get a UserError when multiple attachments are merged for export and one of them is corrupted. The error message did not contain information helping the user identify the problematic records. After this commit, the user will get a RedirectWarning stating the number of corrupted files and a link to a form view (if single) or a list view (if multiple) of problematic record(s). ### Example workflow: 1. Go to Accounting > Vendors > Bills. 2. Create a bill wi
Original PR description
Before this commit, the user would get a UserError when multiple attachments are merged for export and one of them is corrupted. The error message did not contain information helping the user…
Before this commit, the user would get a UserError when multiple attachments are merged for export and one of them is corrupted. The error message did not contain information helping the user identify the problematic records. After this commit, the user will get a RedirectWarning stating the number of corrupted files and a link to a form view (if single) or a list view (if multiple) of problematic record(s). ### Example workflow: 1. Go to Accounting > Vendors > Bills. 2. Create a bill with a corrupted attachment. 3. Select the corrupted bill amongst other bills with valid attachments. 4. Click on Print > Original Bills. 5. The error is: "Odoo is unable to merge the generated PDFs." ### Cause: Errors raised by instantiating a PdfFileReader of a corrupted file were handled with a UserError with a static error message. ### Solution: In `_merge_pdfs` method signature, add an optional callback to define the way errors are handled. The default callback reproduces the default behavior. In `_render_qweb_pdf`, a custom callback is defined to keep track of the corrupted streams and log them in the RedirectWarning popup. opw-4067992 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174701
When using a non parsable ODOO_MAX_HTTP_THREADS value, take into account max_cron_threads. When a lot of xmlrpc or jsonrpc calls are made, 2 cursor are used per call due to the authentification so it maxes out and the pool limit. If the cron_thread are using a cursor we end up with a "Pool Is Full" error. Forward-Port-Of: odoo/odoo#172902
Original PR description
When using a non parsable ODOO_MAX_HTTP_THREADS value, take into account max_cron_threads. When a lot of xmlrpc or jsonrpc calls are made, 2 cursor are used per call due to the authentification so it maxes out and the pool limit. If the cron_thread are using a cursor we end up with a "Pool Is Full" error. Forward-Port-Of: odoo/odoo#172902
__Current behavior before commit:__ When a mega menu has the class `o_mega_menu_container_size`, it is translated by 50% to the left because of this line [1]. However it shouldn't be if it is displayed inside a dropdown menu. __Description of the fix:__ Unset `transform` of `.o_mega_menu_container_size` when it is inside an `.o_extra_menu_items` element. __Steps to reproduce the issue on runbot:__ 1. Add a mega menu to the website 2. In the Editor, set Mega Menu > Size to `Narrow` a
Original PR description
__Current behavior before commit:__ When a mega menu has the class `o_mega_menu_container_size`, it is translated by 50% to the left because of this line [1]. However it shouldn't be if it is displayed inside a dropdown menu. __Description of the fix:__ Unset `transform` of `.o_mega_menu_container_size` when it is inside an `.o_extra_menu_items` element. __Steps to reproduce the issue on runbot:__ 1. Add a mega menu to the website 2. In the Editor, set Mega Menu > Size to `Narrow` and save 3. Resize the window just enough that a dropdown menu appear 4. Open the dropdown menu -> The mega menu is offset to the left opw-4021738 [1]: https://github.com/odoo/odoo/blob/9835632/addons/website/static/src/scss/website.scss#L1294 Forward-Port-Of: odoo/odoo#172438
Issue: the reserved quantity appearing on the SOL wizard is not well behaved with respect to 2+ steps deliveries. ### Steps to reproduce: - Enable Multi-step routes in the settings - Inventory > Configuration > Warehouse Management > Warehouses - Enable delivery in 2 steps - Create a storable product and put 1 unit in stock - Create and confirm an SO for 1 unit - Click on the chart icon next to the delivered qty #### > the reserved qty is 0 + "No future availability" even though 1
Original PR description
Issue: the reserved quantity appearing on the SOL wizard is not well behaved with respect to 2+ steps deliveries. ### Steps to reproduce: - Enable Multi-step routes in the settings - Inventory >…
Issue: the reserved quantity appearing on the SOL wizard is not well behaved with respect to 2+ steps deliveries. ### Steps to reproduce: - Enable Multi-step routes in the settings - Inventory > Configuration > Warehouse Management > Warehouses - Enable delivery in 2 steps - Create a storable product and put 1 unit in stock - Create and confirm an SO for 1 unit - Click on the chart icon next to the delivered qty #### > the reserved qty is 0 + "No future availability" even though 1 unit is reserved from stock ### Cause of the issue: The reserved qty displayed on the next to the delivered qty on the SOL is the `qty_available_today` computed field of the SOL model. This field is computed by summing the qties of the stock moves linked to the SOL: https://github.com/odoo/odoo/blob/817186b7b896c9a415bd947baf189bf7f1bde321/addons/sale_stock/models/sale_order_line.py#L69 https://github.com/odoo/odoo/blob/817186b7b896c9a415bd947baf189bf7f1bde321/addons/sale_stock/models/sale_order_line.py#L80-L81 However, when you are not delivering in 1 step, the only delivery move linked to the SOL will be the move which destination is the customer location. To be more precise, confirming the SO in a delivery in two steps a stock move from the Output to the customer will be created and linked to the SOL. During the action confirm of this move a procurement will be run to generate a move from stock to the Output but the SOL will not be referenced anymore so that the SOL will not be linked to it. ### Note: The behavior is different in saas-17.2 where each of the delivering move is linked to the SOL so that the probably need to be adapted. opw-3981935 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176756
This fix add a verification check to ir.filter and ir.default. This aims at preventing user to put such record out of their own reach This behaviour is usually valid in Odoo, however in this case, it is not normal that the user cannot delete the filter and default that he created himself. Forward-Port-Of: odoo/odoo#174227
Original PR description
This fix add a verification check to ir.filter and ir.default. This aims at preventing user to put such record out of their own reach This behaviour is usually valid in Odoo, however in this case, it is not normal that the user cannot delete the filter and default that he created himself. Forward-Port-Of: odoo/odoo#174227
When a blog cover is edited, a tag option is displayed while there is no `tag_ids` inside the `blog.blog` model because the `o_wblog_post_page_cover` appears on both the `blog.blog` covers and on the `blog.post` covers. This commit hides the blog tags option if the model of the cover is `blog.blog`. Steps to reproduce: - Go to blogs. - Select the "Travel" blog. - Edit. - Select the blog's cover. => A tag option could be specified. opw-4107748 Forward-Port-Of: odoo/odoo#177077 Fo
Original PR description
When a blog cover is edited, a tag option is displayed while there is no `tag_ids` inside the `blog.blog` model because the `o_wblog_post_page_cover` appears on both the `blog.blog` covers and on the `blog.post` covers. This commit hides the blog tags option if the model of the cover is `blog.blog`. Steps to reproduce: - Go to blogs. - Select the "Travel" blog. - Edit. - Select the blog's cover. => A tag option could be specified. opw-4107748 Forward-Port-Of: odoo/odoo#177077 Forward-Port-Of: odoo/odoo#176510