Thursday, September 26, 2024
75 changes · 18.0
Enhancements to existing features
The confirmation message shown when updating product attribute values now explains that a value is being added, rather than showing only the value name. This helps users better understand the action before applying it to multiple products.
Original PR description
This commit update confirmation msg of ptav wizard to update product attributes message to add what it'll add to product instead just attribute name **Before**: `You are about to add "Black" to 10 products` **After**: `You are about to add the value "Black" to 10 product`
The Sales reporting menu labels have been renamed to better match the naming style used by other sales reports. This makes navigation more consistent and easier for users to understand, with no expected impact on business processes.
Original PR description
This commit rename reporting menus to have consistent name with other reporting menus in sales. task-4209879
This pull request updates Odoo's internal Hoot testing framework and switches the main web test route to the newer test suite. It improves how automated tests simulate user actions such as clicks, touch events, resizing, and hover behavior, helping reduce false failures without changing normal business features.
Original PR description
## Pull Request HOOT (PRHOOT) - part 23 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
The website editor no longer shows image width choices for images inside cards, where those settings could produce confusing or awkward results. This keeps card editing simpler and helps users create more consistent page layouts.
Original PR description
Commit [1] introduced new options for cards and more. Image integration into cards and related options were added. Image have a "width" option (25-50-100%)... which actually does not make much sense when it concern card images. This has always been the case but [1] made it more visible and created new ways for that option to be weird when used on card images. Time to hide it in that case. [1]: https://github.com/odoo/odoo/commit/dd40e1e8d9026d189dc17134c85331711f50a470 task-4208444
Financial reports now show both the start and end dates for quarter labels. This reduces confusion for companies whose fiscal year does not match the calendar year, making report periods easier to understand.
Original PR description
Before this commit quarter strings on reports were not always explicit. If the fiscal year was not aligned to the calendar year, people would get confused by thinking the quarter was aligned on the fiscal year Now to avoid that we show the start and the end of the quarter. task-4200096
This update improves Odoo's automated test suite by adapting enterprise tests to newer Hoot testing behavior and cleaner test syntax. It helps maintain product quality and reduces the risk of issues reaching users, without changing normal business workflows.
Original PR description
## Pull Request HOOT (PRHOOT) - part 23 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4:…
## Pull Request HOOT (PRHOOT) - part 23 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Part 16: https://github.com/odoo/odoo/pull/166311 Part 17: https://github.com/odoo/odoo/pull/168328 Part 18: https://github.com/odoo/odoo/pull/171004 / https://github.com/odoo/enterprise/pull/65657 Part 19: https://github.com/odoo/odoo/pull/171242 / https://github.com/odoo/enterprise/pull/65767 Part 20: https://github.com/odoo/odoo/pull/173332 / https://github.com/odoo/enterprise/pull/66895 Part 21: https://github.com/odoo/odoo/pull/174337 Part 22: https://github.com/odoo/odoo/pull/176777 / https://github.com/odoo/enterprise/pull/68721 Community: https://github.com/odoo/odoo/pull/179660 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#69728
Resolved issues and error corrections
Mention links in Mail now use matching link details so users are sent to the correct record. This restores expected navigation from mentions and prevents failed redirects caused by inconsistent URL formatting.
Original PR description
This PR corrects an issue introduced in [1], where the `base href` of mention URLs was converted from `web` to `odoo`, but the associated query parameters were not updated accordingly. As a result, the redirection to the proper record failed. [1]: https://github.com/odoo/odoo/pull/174516 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This update reorganizes how editor overlays, such as pop-ups and helper panels, are managed so they are easier for developers to use consistently. It also centralizes how these overlays close and improves editing behavior when users interact with fields inside them, reducing duplicated logic and potential interface glitches.
Original PR description
The purpose of this PR is to make it easier to use overlays in the editor. 1. Clarify the createOverlay API. ================================ Before, we mixed up the positioning hook options and the…
The purpose of this PR is to make it easier to use overlays in the editor. 1. Clarify the createOverlay API. ================================ Before, we mixed up the positioning hook options and the EditorOverlay props. After, put all the positioning options in the positionOptions props and move the sequence to the last param, which corresponds to the overlay system options. 2. Automatically manage the close at pointerdown. ================================================= Before, the logic for closing overlays outside the overlay was duplicated in each component use by createOverlay. After, the overlay editor is responsible for closing overlays when a pointerdown occurs outsite of the overlay. You can disable this functionality with the closeOnPointerdown=‘false’ props. 3. Managing setSelections when the selection is not in the editable =================================================================== For example, the selection is in the input of an overlay. From this commit, when you call setSelection, if the selection is not in the editable, you no longer force the selection to be moved into the editable, you just update the activeSelection. When you want to force the restoration of the selection in the editable, for example when you close an overlay, you call the focusEditable function. This change makes it possible to call functions that manipulate the selection from the outside without having to refocus in the editor.
Documentation and clarification updates
This pull request updates ForgeFlow's corporate Contributor License Agreement record. It helps keep Odoo's contributor legal documentation current and does not change product features or user workflows.
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
Miscellaneous changes
If markup is set to a value then reset to 0, the discount is not properly reset to 0. This commit removes `if item.price_markup` as it was wrong. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181391
Original PR description
If markup is set to a value then reset to 0, the discount is not properly reset to 0. This commit removes `if item.price_markup` as it was wrong. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181391
## Pull Request HOOT (PRHOOT) - part 23 Part 1: https://github.com/odoo/odoo/pull/152930 Part 2: https://github.com/odoo/odoo/pull/153018 Part 3: https://github.com/odoo/odoo/pull/153023 Part 4: https://github.com/odoo/odoo/pull/153203 Part 5: https://github.com/odoo/odoo/pull/153425 Part 6: https://github.com/odoo/odoo/pull/153700 Part 7: https://github.com/odoo/odoo/pull/154054 Part 8: https://github.com/odoo/odoo/pull/154579 Part 9: https://github.com/odoo/odoo/pull/155073 Part 10: https://github.com/odoo/odoo/pull/155639 Part 11: https://github.com/odoo/odoo/pull/156255 / https://github.com/odoo/enterprise/pull/58135 Part 12: https://github.com/odoo/odoo/pull/156869 Part 13: https://github.com/odoo/odoo/pull/158384 / https://github.com/odoo/enterprise/pull/59019 Part 14: https://github.com/odoo/odoo/pull/158916 Part 15: https://github.com/odoo/odoo/pull/160292 / https://github.com/odoo/enterprise/pull/59971 Part 15.5: https://github.com/odoo/odoo/pull/166463 Part 16: https://github.com/odoo/odoo/pull/166311 Part 17: https://github.com/odoo/odoo/pull/168328 Part 18: https://github.com/odoo/odoo/pull/171004 / https://github.com/odoo/enterprise/pull/65657 Part 19: https://github.com/odoo/odoo/pull/171242 / https://github.com/odoo/enterprise/pull/65767 Part 20: https://github.com/odoo/odoo/pull/173332 / https://github.com/odoo/enterprise/pull/66895 Part 21: https://github.com/odoo/odoo/pull/174337 Part 22: https://github.com/odoo/odoo/pull/176777 / https://github.com/odoo/enterprise/pull/68721 Enterprise: https://github.com/odoo/enterprise/pull/69728 This pull requests brings various improvements and fixes to Hoot and the Odoo unit test ecosystem. See the different commit messages for more details. Note: these changes are made in stable to avoid having to support multiple versions of the HOOT API. As such, these changes are intended to be strictly limited to unit tests as to not put the rest of the code base at risk. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179660
This fix prevents an error when adding products to a sales quotation for customers with an analytic distribution model that has no distribution lines. It ensures the quotation flow continues normally instead of showing a traceback, improving reliability for accounting-enabled sales workflows.
Original PR description
Steps --------- 1. Install `accounting` and `sale_management` 2. Activate Accounting > Configuration > Settings > Analytics > Analytic Accounting 3. Accounting > Configuration > Analytic Accounting > Distribution Model 4. Create a new model and only put Deco Addict as partner, then save 5. Go to the Sale app 6. New quotation 7. Select Deco Addict as partner 8. Click `Add a product`, a traceback is raised. Problem --------- Using `|=` requires two objects of the same type. Unfortunately, when there is no distribution line, `analytic_distribution` is False whereas `res` is a dict. Solution --------- Use a empty dict instead when `analytic_distribution` is False. V18 Accounting PAD issues --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes the table border color in the stock rule diagram so the report displays with the intended visual styling. It is a small presentation correction that helps users read inventory rule diagrams more clearly and consistently.
Original PR description
In the stock rule diagram, the table border color was not correct anymore. before:  after:  Retarget of https://github.com/odoo/odoo/pull/181395 task-id: 4207218 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales order previews now show the same Terms and Conditions content as the PDF invoice. This prevents customers from seeing only a webpage link when custom text or images were added to the order notes, improving consistency across sales documents.
Original PR description
Problem: When the option "Add a link to a Web Page" is enabled, the preview page always shows the T&C link regardless of the content added to the notes. This behavior is inconsistent with the T&C section in the PDF invoice. Steps to reproduce: - Enable "Add a link to a Web Page." - Create a new Sales Order (SO). - Add content (text or image) to the notes. - Confirm and preview the SO. - The added content does not appear in the T&C section. opw-4170021 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant floor plans with background images now allow tables to be dragged correctly in Chrome on iOS. This prevents the browser context menu from interrupting staff when linking or repositioning tables.
Original PR description
Table linking in chrome on ios does not work if the floorplan has a bg image. When the user tries to drag a table, the context menu appears, which prevents the table dragging from taking place. This is because of a mistake in commit 894d7c25b7dd216ac6df1fd8ebedffccd20ef64e, where a line was removed. Task: 4196350 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The loyalty rewards page now hides the claim button when a customer has no rewards available. This prevents confusing prompts and makes the shopping experience clearer.
Original PR description
Before the commit: The button label remained as 'Claim' even when there were no rewards, which seemed inconsistent. After this commit: The button gets hidden when no rewards are available.
This fixes an editor issue where deleting selected paragraphs near a horizontal line could add extra blank space under the line. Users can now edit content around horizontal rules without the layout being unexpectedly altered.
Original PR description
Steps: 1. have a horizontal rule (HR) and two paragraphs in the editor 2. make a selection across the two paragraphs 3. press backspace or delete Result: the HR gets filled with a BR element, leading to a vertical space being added below it. The isShrunkBlock function is typically used to detect blocks that need to have a BR element added to it, otherwise they would be displayed collapsed in the editor. Before this commit, the HR element was (incorrectly) considered as a shrunk block. The issue described above happened because the deleteRange method, after removing nodes as joining blocks, looks for shrunk blocks and fills them with a BR element.
Deleting a Point of Sale order now removes its linked records first, preventing errors during the deletion process. This makes order cleanup more reliable for cashiers and back-office users.
Original PR description
Before when deleting an order, we removed the order and after related records. This caused an error when trying to remove the order because the related records try to access the order. Now we remove the related records first and then the order.
This fix makes an image editing test run consistently instead of failing unpredictably. It helps keep the editor quality checks dependable, reducing noise for development and release validation without changing user-facing behavior.
Original PR description
Before this commit, the @html_editor/image/Image transformation dissapear when selection change test was failing unpredictably. This commit fix it. Backward-port of #181200
Website price list snippets have been moved into the Text category so users can find them in a more logical place. This is a small usability fix that improves content editing organization without changing website behavior.
Original PR description
This commit moves the price list snippets to a more appropriate category: Text task-4212916 Requires: - https://github.com/odoo/design-themes/pull/942 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix corrects an internal reference used when selecting a cashier in Point of Sale with employee support. It prevents cashier selection from failing because the system was looking for an outdated item name.
Original PR description
Item does not exist anymore on the employee list in the select cashier mixin. Adapt the code to use the correct variable name.
The Reset to Draft button is available again for payments that are still in process. This lets users correct or revise these payments before they reach stages where resetting is no longer allowed, while validated and sent payments remain protected.
Original PR description
This commit Restore "Reset to Draft" on Payments "In Process". Only Validated & Sent Payments can not be Reset to Draft. task: 4213210 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website visitor view now adds proper spacing between SMS and chat buttons. This small visual fix makes the buttons easier to distinguish and improves the overall presentation for visitors and staff using the interface.
Original PR description
before this commit there is no space between 'sms' and 'chat' buttons. after this commit added a space between both buttons. enterprise PR-https://github.com/odoo/enterprise/pull/70742 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes the website call-to-action card snippet so its styling is applied correctly. Users will see the intended card colors and borders when using this website building block.
Original PR description
In commit [1], the new `s_cta_card` snippet has been added. It uses the `s_card` inner snippet. This commit fixes the card: - add the missing `data-snippet` attribute, - fix the versioning: indeed, it was using `data-vcss` while the inner snippet in fact uses `data-vxml`. This caused the card background colors to be washed out, instead of being the real selected color. - fix the `border-width` style: it was missing the `px` unit and the `!important` that would be added if we used the option to set it. [1]: https://github.com/odoo/odoo/commit/4b88c63a96e84f5a603eea35fee3a395fbb4aae3 Related to task-4094392
The website loading screen no longer shows the "follow the tips" message while interactive website tours are not working correctly. This avoids directing users to a broken or unreliable guidance feature until a proper fix is available.
Original PR description
Website user/interactive tours are not properly working at the moment. This disables the "follow the tips" message in the website loader while waiting for a fix. Follow-up of https://github.com/odoo/odoo/pull/180471 Related to task-3084175
This fix updates newer Kanban views so outdated bold and display settings are no longer applied where they are unsupported. It helps keep Kanban card styling consistent and encourages the supported Bootstrap styling approach, while preserving compatibility for older legacy Kanban layouts.
Original PR description
*in new API kanban views. Those attributes are no longer supported as the css rules associated with the classname they generate are scoped to legacy kanban. Instead, we want to encourage the use of bootstrap utility classes (e.g. fw-bold). Note: those attributes were no longer used in standard views. Note 2: we keep supporting them in legacy archs (those using "kanban-box"). The support of legacy archs will be dropped after v18. Part of task~3992107 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
Mobile users can now open the emoji reaction picker without the phone keyboard covering it. This makes adding reactions easier and avoids a frustrating display issue on smaller screens.
Original PR description
Before this commit: In mobile view, when the 'Add a reaction' action is clicked, the EmojiPicker opens, but the native keyboard also appears due to the focus being on the input field. This causes the keyboard to block the view of the EmojiPicker. After this commit: Now, in mobile view, the input search bar will not be automatically focused when the EmojiPicker opens, preventing the native keyboard from appearing and obstructing the EmojiPicker. task-4208499
This update fixes several issues in Odoo's data population tooling so it works more reliably across different database permissions and newer field storage formats. It also restores missing help information in the command-line interface, making the tool easier to use and troubleshoot.
Original PR description
## [FIX] tools: variate `company_dependent` dates Following de302c2d36305c0d7562572a30587641eabfe914, `company_dependent` fields are stored as `jsonb` now, so the variation of dates needs to take that into account. ## [FIX] tools: allow populate for less priviledged `pg_roles` When running the `populate` with a `pg_roles` that doesn't have admin access or the group `session_replication_role` (only since PG15), the routine crashes with an Insufficient exception when trying to drop the Fkey constriants. This context manager was initially added to speed up batch insertion by 10x, but we are adding a generic catch to ignore said optimisation when privileges are insufficient. ## [FIX] cli: show --help for populate CLI Group options were added with the respective `help` section for each arg, but the group was never added to the CLI arg parser. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an editing issue where deleting content below a separator could add an unwanted blank line inside the separator. This keeps page content cleaner and avoids small visual glitches when users edit formatted text.
Original PR description
Before this commit: delete an empty line under a separator and some text adds a br element to the separator After this commit: the br won't be added to hr element because it already has a visible height --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product categories now record changes to their costing method in the activity log. This helps teams see when costing rules were changed, improving traceability for inventory valuation and accounting reviews.
Original PR description
This commit enables tracking of the costing method in chatter for the product category.
This change prevents the HTML editor from crashing when users drag selected table cells into content outside the table. It improves editing reliability and adds a test to help ensure the issue does not return.
Original PR description
Before this commit: in a table, select last two cells of first row and drag drop it to a p element out of the table, a traceback is raised After this commit: the traceback is fixed, the added test only simulate the to be pasted content when drag and drop the selected cells --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The editor now applies the correct spacing to the placeholder text shown inside empty quote blocks. This makes the editing experience look cleaner and ensures the placeholder appears where typed text will actually begin.
Original PR description
This commit adds the styling rules for the blockquote (present in the web_editor module), and fixes the padding for the hint that is displayed when the blockquote is empty. Before this commit, the hint would be displayed on the top left corner of the blockquote without any padding, which, other than looking bad, does not match the position in which the text is inserted after typing. task-4207507
Corrects a website page template so parallax sections no longer duplicate the background positioning setting. This helps ensure newly created service pages render cleaner markup and avoids potential visual inconsistencies.
Original PR description
The `new_page_template_services_s_parallax` template wrongly adds the `background-position` of the `style` attribute. This commit fixes this definition so that the old `background-position` is replaced. Steps to reproduce: - Add a new page - In the Service tab, pick a template that contains a parallax block (at the time of writing, this is the case of the second one in the first column) - Inspect the parallax block => The `background-position` was defined twice. task-4206845
The message composer now shows clearer placeholder text when replying in subchannels. This avoids using the # symbol, which can make a thread look like a channel and confuse users.
Original PR description
Purpose of this commit: Adjust the placeholder text for subchannels, as it previously included the '#' symbol, which typically denotes a channel rather than a thread Before  After 
Fixes an issue where temporary preview content could remain visible when replacing an outdated website editor snippet. This keeps the editing experience cleaner and prevents unwanted placeholder elements from appearing in updated page content.
Original PR description
Since commit [1], the snippets are dropped by using a snippets dialog. In order for dynamic elements to be visible in the modal, fake previews are used. They are then removed once the snippet is dropped. These previews can be recognized by their `s_dialog_preview` class. When a snippet is deprecated, a message is displayed in the right panel, informing that it is outdated and allowing to therefore replace it by its new version. However, in the case where the new version would have a dialog preview in it, this preview would not be removed. This commit handles the dialog previews removal when replacing an outdated snippet. [1]: https://github.com/odoo/odoo/commit/edf81c13d8f2f6d29a77d68cbfa0dc9216da3c2a task-4185274
The mobile app now handles expected permission-related responses during startup without showing or logging disruptive unhandled errors. This helps make app launch more reliable when native device permissions are requested for the first time.
Original PR description
In the Native Mobile Apps when we use a Native method that requires a permission the promise is rejected on the first call. This commit avoids to generate `unhandledrejection` in this case.
This fix prevents styling meant for grid views from affecting empty-state messages in other parts of Odoo. Users should see more consistent layout behavior across views, with the grid view still displaying its no-content helper correctly.
Original PR description
Before this commit, the 3c7775f4c7a3efaa891bc31072c41abff24edfad commit adds some style to correctly display the noContent helper inside the grid view. The problem is the selector used to apply that styling is too generic and not specific to the grid view which can alter the position of the no content helper in other views. This commit makes sure the style added for the grid view is only applied inside the grid view and not somewhere else. task-4207210
This fix prevents an error when calculating allocated hours for open shifts that do not yet have a resource assigned. It improves reliability in planning by safely checking that a resource exists before using its scheduling settings.
Original PR description
Before this commit, the compute of the allocated hours could be raised a traceback if the shift is an open one because we check if the resource is flexible before checking if there is a resource set on the shift. This commit makes sure a resource exists on the shift before checking if the resource is flexible or not. task-4206945
A Web Studio automated test now checks that required optional apps are installed before running. This prevents false failures in limited test environments and helps keep release validation stable without changing business features.
Original PR description
**Before this commit** Tests on test_23_export_hardcoded_models_and_fields function break on single app tests because we are trying to find models from PRESET_MODELS_DEFAULTS in runbot that do not actually exist in self.env if we do not install extra modules like hr, crm, etc. **After this commit** This test checks beforehand if some needed modules are all installed.
This fixes the layout of the SMS and Chat buttons so they no longer appear too close together. The change improves readability and makes the visitor contact options look cleaner for users.
Original PR description
before this commit there is no space between 'sms' and 'chat' buttons. after this commit added a space between both buttons.
Creating multiple restaurant appointments in a row no longer triggers an error in the back-office calendar. The calendar now relies on its normal data update process, preventing the wrong booking from being reloaded.
Original PR description
Before when creating two appointment one by one, an error was raised for the second appointment. This was due to the fact that the calendar view was refreshed with a wrong active id. This commit remove the view refresh since the view itself make a RPC to get the new data.
Users customizing Kanban views in Studio can now reliably turn bold formatting on or off for fields. This fixes a styling issue so visual changes made in the editor are correctly reflected in the view.
Original PR description
Before this commit, toggling the bold attribute on a field in a (new API) kanban view didn't work. This was because the feature wasn't fully implemented (in web) for new API kanban. Indeed, the class "o_text_bold" was correctly set, but the associated css rule was scoped for legacy kanban records. Instead of fixing it in web, we rather want to promote the use of bootstrap utility class. So instead of setting the `bold` attribute, we toggle the `fw-bold` classname.
The appointment demo setup now shows the table booking appointment as "Table" instead of "Table Booking". This avoids a confusing label on the booking page and keeps the demo experience aligned with the intended naming.
Original PR description
**How to reproduce** Create a Table Booking appointment from the Action helper Go to the booking page for that appointment it looks like this - https://tinyurl.com/29q2ktjb **After this PR** Now that appointment name will be Table instead of Table Booking Backport of this commit - https://github.com/odoo/enterprise/pull/70643/commits/209aeae1f5d6689ef15fd8016cbcd08b03710f6f Task-4210749
Portal users can now switch to the document list view without seeing a client error. This improves reliability for external users accessing shared documents through the portal.
Original PR description
When portal users try to switch to the list view, they get a client error. The error is solved by keeping the studio service accessible to the ListRenderer. task-3373836
This fixes an issue where marketing automation for website sales used the wrong website field when filtering sales teams. Campaign targeting should now work more reliably for businesses using multiple websites or website-specific sales flows.
Original PR description
website_id is not defined on sale teams... website_ids is. "False" should be False... task-4210343
Spreadsheet pivot views now correctly support using the same field with multiple calculation methods. This prevents incorrect or missing pivot results and keeps spreadsheet reporting aligned with the related pivot view fix.
Original PR description
This commit is the counter part of https://github.com/odoo/odoo/pull/181354 and adapt a test to the fix of the pivot view in spreadsheet. Task: 4207668
Since the refactor https://github.com/odoo/odoo/pull/110188, the welcome page had several bugs: 1) The `fa-microphone-slash` icon was displayed when the microphone was on instead of when the microphone was mute. 2) The localStorage keys `discuss_call_preview_join_mute` and `discuss_call_preview_join_video` were set with booleans, while the localStorage stores as strings, which made them always truthy as soon as they were set. 3) The microphone preview was not working as the `srcObject`
Original PR description
Since the refactor https://github.com/odoo/odoo/pull/110188, the welcome page had several bugs: 1) The `fa-microphone-slash` icon was displayed when the microphone was on instead of when the…
Since the refactor https://github.com/odoo/odoo/pull/110188, the welcome page had several bugs: 1) The `fa-microphone-slash` icon was displayed when the microphone was on instead of when the microphone was mute. 2) The localStorage keys `discuss_call_preview_join_mute` and `discuss_call_preview_join_video` were set with booleans, while the localStorage stores as strings, which made them always truthy as soon as they were set. 3) The microphone preview was not working as the `srcObject` of the audio element was `undefined` because we were using `this.audioStream` instead of `this.state.audioStream`. 4) Before the refactor, the preview was automatically started when opening the welcome page, this commit restores this behavior: https://github.com/odoo/odoo/blob/16.0/addons/mail/static/src/models/discuss_public_view.js#L46-L49 5) Streams (tracks) were not closed after leaving the welcome view, nor was it checked whether they were still needed after the `getUserMedia` promise. Forward-Port-Of: odoo/odoo#179209 Forward-Port-Of: odoo/odoo#177525
The issue was recently fixed with a sudo, but it allowed standard salesman/users to create discount products and update the company, which ideally shouldn't happen. Since a single use of the wizard by the admin will properly create the discount product, we prefer to encourage the user to request the admin to do it first instead of bypassing the standard access rights. opw-4048403 Forward-Port-Of: odoo/odoo#180298 Forward-Port-Of: odoo/odoo#180221
Original PR description
The issue was recently fixed with a sudo, but it allowed standard salesman/users to create discount products and update the company, which ideally shouldn't happen. Since a single use of the wizard by the admin will properly create the discount product, we prefer to encourage the user to request the admin to do it first instead of bypassing the standard access rights. opw-4048403 Forward-Port-Of: odoo/odoo#180298 Forward-Port-Of: odoo/odoo#180221
### Steps to reproduce: - Create and confirm an SO for 5 units of a consumable product. - Validate the associated delivery. - Return and validate the return. - Return and validate the return of the return. - Change the demand of the SO from 5 to 8 units. #### > A delivery order for 8 units is created instead of 3. ### Cause of the issue: Changing the demand on the SO will trigger the ` _action_launch_stock_rule` to determine which procurement to trigger in order to fulfill the de
Original PR description
### Steps to reproduce: - Create and confirm an SO for 5 units of a consumable product. - Validate the associated delivery. - Return and validate the return. - Return and validate the return of the…
### Steps to reproduce: - Create and confirm an SO for 5 units of a consumable product. - Validate the associated delivery. - Return and validate the return. - Return and validate the return of the return. - Change the demand of the SO from 5 to 8 units. #### > A delivery order for 8 units is created instead of 3. ### Cause of the issue: Changing the demand on the SO will trigger the ` _action_launch_stock_rule` to determine which procurement to trigger in order to fulfill the delivery. During this call the qty to deliver will be computed by comparing the quantity handled by incoming and outgoing moves linked to the sol. However, the return of the return of an outgoing move will not be flagged as an outgoing move since it does not have a `location_final_id` since it was created as a return: https://github.com/odoo/odoo/blob/4a050ec0efb929f7605856f490025f7921d39672/addons/sale_stock/models/sale_order_line.py#L266-L267 https://github.com/odoo/odoo/blob/4a050ec0efb929f7605856f490025f7921d39672/addons/sale_stock/models/sale_order_line.py#L288-L292 opw-4105394 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180492 Forward-Port-Of: odoo/odoo#179719
Before this commit, adding a product to the cart became progressively slower after creating several orders in the PoS, especially when a high number of products were loaded. This performance issue was due to the search operation across all order lines for each product, which became increasingly inefficient with a large number of loaded products and created orders. To address this, "<-pos.order.line.product_id" is now utilized to directly find the corresponding order line, significantly reducing
Original PR description
Before this commit, adding a product to the cart became progressively slower after creating several orders in the PoS, especially when a high number of products were loaded. This performance issue was due to the search operation across all order lines for each product, which became increasingly inefficient with a large number of loaded products and created orders. To address this, "<-pos.order.line.product_id" is now utilized to directly find the corresponding order line, significantly reducing the time complexity and improving the responsiveness of product addition to the cart. opw-4209134 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181415
Before this commit, attempting to add a product to the cart that did not have an archived variant would result in an error. opw-4212973 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181512
Original PR description
Before this commit, attempting to add a product to the cart that did not have an archived variant would result in an error. opw-4212973 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181512
Before this commit, connecting a `<-` field unnecessarily attempted to link the record to the reversed field, which was not required. This additional search operation increased the time complexity of the connection process, leading to performance inefficiencies. opw-4169060 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179886
Original PR description
Before this commit, connecting a `<-` field unnecessarily attempted to link the record to the reversed field, which was not required. This additional search operation increased the time complexity of the connection process, leading to performance inefficiencies. opw-4169060 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179886
Steps - install `stock` - create a delivery for 2 products > *Mark as Todo* > *Validate* - make a return, a `ListRenderer` for the return moves opens - click the last field (quantity) of the last record in the list - press `tab` * => Traceback: `Uncaught Promise > futureRecord is undefined` Cause --- This specific view is `editable='top' create='0'`, but the return moves have been generated on the fly, so their `isNew` property is true. But, we check `isNew` to decide if a rec
Original PR description
Steps - install `stock` - create a delivery for 2 products > *Mark as Todo* > *Validate* - make a return, a `ListRenderer` for the return moves opens - click the last field (quantity) of the last record in the list - press `tab` * => Traceback: `Uncaught Promise > futureRecord is undefined` Cause --- This specific view is `editable='top' create='0'`, but the return moves have been generated on the fly, so their `isNew` property is true. But, we check `isNew` to decide if a record has just been created in the list, and what element is the last. This leads to a false negative where we don't detect that we're on the last record. Note --- `.isNew` is still needed because we can run into problems with the pager or if we start with a grouped list view. opw-4108845 Forward-Port-Of: odoo/odoo#180908 Forward-Port-Of: odoo/odoo#180690
Before this commit, attempting to sync a paid order that had not been previously synced in a newly opened session would result in an error due to the absence of the `session_id`. opw-4182909 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181015
Original PR description
Before this commit, attempting to sync a paid order that had not been previously synced in a newly opened session would result in an error due to the absence of the `session_id`. opw-4182909 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#181015
Steps to reproduce the bug: - Create a storable product “P1” with the following BoM: - Type: subcontracting - subcontractor: Azure interior - Components: C1: - Route of C1: Resupply subcontractor on Order - Create a purchase order: - Vendor: Azure interior - Product: 1 unit of P1 - Confirm the PO - Go to the resupply of P1 and confirm it - Go to the receipt and record the components - Click on the subcontracting button Problem: An owl error
Original PR description
Steps to reproduce the bug: - Create a storable product “P1” with the following BoM: - Type: subcontracting - subcontractor: Azure interior - Components: C1: - Route of C1: Resupply subcontractor on…
Steps to reproduce the bug:
- Create a storable product “P1” with the following BoM:
- Type: subcontracting
- subcontractor: Azure interior
- Components: C1:
- Route of C1: Resupply subcontractor on Order
- Create a purchase order:
- Vendor: Azure interior
- Product: 1 unit of P1
- Confirm the PO
- Go to the resupply of P1 and confirm it
- Go to the receipt and record the components
- Click on the subcontracting button
Problem:
An owl error is triggered:
```
Caused by: KeyNotFoundError: Cannot find key "subcontracting_portal_move_list_view" in the "views" registry
Error: Cannot find key "subcontracting_portal_move_list_view" in the "views" registry
```
The file is not included in the web_asset_backend bundle but only in the client bundle.
This bug was introduced after the following commit:
https://github.com/odoo/odoo/commit/f1749d3299957e2949e0b78653266a5397bb213c#diff-2395c9159b2ea0bf841d6f47ad8299bfa34fa516650acb55ae1392fa3aa32870L321-R328
Previously, if the key was not found when the backend was loaded, the default was used. However, now the key must be found in the registry, otherwise an error is thrown.
opw-4194661
opw-4184122
opw-4181126
Forward-Port-Of: odoo/odoo#180777**Current behavior before PR:** - When a table was created within an empty list item `(li)`, it was inserted directly inside the `ul` and as a sibling of the list item `(li)`. Furthermore, an additional `li` element was generated after the table. **Desired behavior after PR is merged:** - Now, when a table created inside empty `li` elements, it will be correctly inserted within the list item itself instead of the `ul`. Additionally, no extra `li` element will be generated after the tabl
Original PR description
**Current behavior before PR:** - When a table was created within an empty list item `(li)`, it was inserted directly inside the `ul` and as a sibling of the list item `(li)`. Furthermore, an additional `li` element was generated after the table. **Desired behavior after PR is merged:** - Now, when a table created inside empty `li` elements, it will be correctly inserted within the list item itself instead of the `ul`. Additionally, no extra `li` element will be generated after the table. task-3550599 Forward-Port-Of: odoo/odoo#164304
Design Themes: https://github.com/odoo/design-themes/pull/940 Enterprise: https://github.com/odoo/enterprise/pull/70693
Original PR description
Design Themes: https://github.com/odoo/design-themes/pull/940 Enterprise: https://github.com/odoo/enterprise/pull/70693
Before: In chrome, you can see the message "[DOM] Input elements should have autocomplete attributes (suggested: "username"): (More info: https://goo.gl/9p2vKq)". After: The message does not appear. Also, This maintains consistency with the password input which has the attribute autocomplete.  --- I confirm I have signed the CLA and read the PR guid
Original PR description
Before: In chrome, you can see the message "[DOM] Input elements should have autocomplete attributes (suggested: "username"): (More info: https://goo.gl/9p2vKq)". After: The message does not appear. Also, This maintains consistency with the password input which has the attribute autocomplete.  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#146934 Forward-Port-Of: odoo/odoo#146037
template data of model res.company: {id: values} template data of model account.journal, account.tax...: {xmlid: values} An error occurred when adding the x2many field to res.company and try load template --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180816
Original PR description
template data of model res.company: {id: values}
template data of model account.journal, account.tax...: {xmlid: values}
An error occurred when adding the x2many field to res.company and try load template
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#180816Situation: Field `ir.models.fields.field_description` has value `{"en_US": "Foo", "fr_FR": "", "nl_NL": "Baz"}` in database. When using `EXCLUDED.{quote(fname)}`, the value of keys `fr_FR` and `nl_NL` will be lost. Solution: Use `ir.models.fields.field_description || EXCLUDED.field_description` to overwrite part of the value instead of replacing the old value. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#18097
Original PR description
Situation:
Field `ir.models.fields.field_description` has value `{"en_US": "Foo", "fr_FR": "", "nl_NL": "Baz"}` in database. When using `EXCLUDED.{quote(fname)}`, the value of keys `fr_FR` and `nl_NL` will be lost.
Solution:
Use `ir.models.fields.field_description || EXCLUDED.field_description` to overwrite part of the value instead of replacing the old value.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#180970Steps to reproduce the bug: - Create a storable product “P1”: - vendors: -Azure interior, code: Vendor 1 - Deco Addict, code: Vendor 2 - Create a purchase order: - product P1 - Vendor: Azure interior > Description P1 [Vendor 1] - Create an Alternative PO: - Vendor: Deco Addict - Copy products: True Problem: The description of POL is incorrect: P1 [Vendor 1] instead of P1 [Vendor 2] opw-4133933 Forward-Port-Of: odoo/odoo#180798 Forward-Po
Original PR description
Steps to reproduce the bug:
- Create a storable product “P1”:
- vendors:
-Azure interior, code: Vendor 1
- Deco Addict, code: Vendor 2
- Create a purchase order:
- product P1
- Vendor: Azure interior
> Description P1 [Vendor 1]
- Create an Alternative PO:
- Vendor: Deco Addict
- Copy products: True
Problem:
The description of POL is incorrect: P1 [Vendor 1] instead of P1 [Vendor 2]
opw-4133933
Forward-Port-Of: odoo/odoo#180798
Forward-Port-Of: odoo/odoo#179487In de29ff9cee5be830b8d2aaf2c703f4f13ee24dec, we missed a tag for credit notes on PST tax for saskatchewan tax report. opw-3955926 Forward-Port-Of: odoo/odoo#181004
Original PR description
In de29ff9cee5be830b8d2aaf2c703f4f13ee24dec, we missed a tag for credit notes on PST tax for saskatchewan tax report. opw-3955926 Forward-Port-Of: odoo/odoo#181004
Purpose: - Ensure that muted text is displayed exclusively on active lines while remaining absent from other lines. - Resolve the issue where muted text wasn't displaying on the checklist when the selection or cursor was on it. task-3875225 Forward-Port-Of: odoo/odoo#162804
Original PR description
Purpose: - Ensure that muted text is displayed exclusively on active lines while remaining absent from other lines. - Resolve the issue where muted text wasn't displaying on the checklist when the selection or cursor was on it. task-3875225 Forward-Port-Of: odoo/odoo#162804
Problem: The `role` attribute is being retrieved from the `raw` field, but when the page is refreshed, all attributes (including `role`) are set in the `cashier` object, not in `raw`. Steps to reproduce: - Set up a PoS session with the "Log in with Employees" setting enabled. - Use a User/Employee with Administrator PoS access (e.g., Mitchell Admin). - Start a PoS session. - Refresh the page. - Click the "i" icon to see more information about a product. - A traceback occurs. opw-4
Original PR description
Problem: The `role` attribute is being retrieved from the `raw` field, but when the page is refreshed, all attributes (including `role`) are set in the `cashier` object, not in `raw`. Steps to reproduce: - Set up a PoS session with the "Log in with Employees" setting enabled. - Use a User/Employee with Administrator PoS access (e.g., Mitchell Admin). - Start a PoS session. - Refresh the page. - Click the "i" icon to see more information about a product. - A traceback occurs. opw-4120414 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180841
Problem: The query generating the report view has several issues: - The ID for the POS order line is set using `MIN(l.id) AS id`, which causes only the first order line for each order to be displayed, instead of all order lines. - For mapping the `payment_method_id`, the query uses `order_id`, which results in duplicated records. When multiple payment methods are used for a single order (as in the given ticket), the report shows an order line for each payment method. Consequently, all aggrega
Original PR description
Problem: The query generating the report view has several issues: - The ID for the POS order line is set using `MIN(l.id) AS id`, which causes only the first order line for each order to be…
Problem: The query generating the report view has several issues: - The ID for the POS order line is set using `MIN(l.id) AS id`, which causes only the first order line for each order to be displayed, instead of all order lines. - For mapping the `payment_method_id`, the query uses `order_id`, which results in duplicated records. When multiple payment methods are used for a single order (as in the given ticket), the report shows an order line for each payment method. Consequently, all aggregations are multiplied by the number of `payment_method_id` entries for that order. Steps to reproduce: - Open POS. - Add two products with different quantities. - Use two different payment methods during checkout. - Go to the orders report of that shop. - In the list, click on the order you just created. - Notice that many values are incorrectly multiplied by the number of `payment_method_id` entries. opw-4171674 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180020
Updated the tax names, descriptions, and invoice labels to be more clear. Added an additional tax group for exempt. task-4196993 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180766
Original PR description
Updated the tax names, descriptions, and invoice labels to be more clear. Added an additional tax group for exempt. task-4196993 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180766
Before this commit: ========== - Rewards were being applied even when loyalty points were insufficient for the redemption of loyalty rewards. After this commit: ========== - Reward products will not be applied if the customer's loyalty points are Insufficient for the specific reward product. task-4126886 Related PR: https://github.com/odoo/odoo/pull/180972 Forward-Port-Of: odoo/odoo#180981
Original PR description
Before this commit: ========== - Rewards were being applied even when loyalty points were insufficient for the redemption of loyalty rewards. After this commit: ========== - Reward products will not be applied if the customer's loyalty points are Insufficient for the specific reward product. task-4126886 Related PR: https://github.com/odoo/odoo/pull/180972 Forward-Port-Of: odoo/odoo#180981
Starting d1a94147060083da54f9423f8c379676fbb7db66, when making ingenico payment, the pos app sends an `NaN` as `TransactionID`. As a result, users are unable to receive payments from Ingenico terminal. This change proposes to take the last 13 characters of the payment's uuid (after removing the `-` separators) and convert it as integer which will serve as the `TransactionID`. We're only taking the 13 characters because it's the number of characters that can be converted to JS int without exponen
Original PR description
Starting d1a94147060083da54f9423f8c379676fbb7db66, when making ingenico payment, the pos app sends an `NaN` as `TransactionID`. As a result, users are unable to receive payments from Ingenico terminal. This change proposes to take the last 13 characters of the payment's uuid (after removing the `-` separators) and convert it as integer which will serve as the `TransactionID`. We're only taking the 13 characters because it's the number of characters that can be converted to JS int without exponent. Forward-Port-Of: odoo/enterprise#70672
Due to legal reasons, we need to send a zip containing the PDF and the xml. The xml is an UBL `AttachedDocument` containing both the initial xml representing the invoice and the `ApplicationResponse` returned when calling the GetStatus webservice of DIAN. The `ApplicationResponse` is an xml representing the state of the invoice on the DIAN server. task-4133688 backport of https://github.com/odoo/enterprise/pull/70171 Forward-Port-Of: odoo/enterprise#70664
Original PR description
Due to legal reasons, we need to send a zip containing the PDF and the xml. The xml is an UBL `AttachedDocument` containing both the initial xml representing the invoice and the `ApplicationResponse` returned when calling the GetStatus webservice of DIAN. The `ApplicationResponse` is an xml representing the state of the invoice on the DIAN server. task-4133688 backport of https://github.com/odoo/enterprise/pull/70171 Forward-Port-Of: odoo/enterprise#70664
Before this commit, changing the partner in POS for the EC localization was raising an OWL error. This error happens because missingFields got stripped from most of the codebase, including PartnerList, leading to an "Invalid Props" error in Owl. This was preventing users from selecting a partner other than the default "consumidor final". After this commit, clicking the partner button correctly opens the "partner selection" popup. opw-4171779 opw-4192162 Forward-Port-Of: odoo/enterpr
Original PR description
Before this commit, changing the partner in POS for the EC localization was raising an OWL error. This error happens because missingFields got stripped from most of the codebase, including PartnerList, leading to an "Invalid Props" error in Owl. This was preventing users from selecting a partner other than the default "consumidor final". After this commit, clicking the partner button correctly opens the "partner selection" popup. opw-4171779 opw-4192162 Forward-Port-Of: odoo/enterprise#70559
The aim of this commit is to add an extra security in the test of the reporting framework. Context: Those line_id are used to recognize lines in the framework and also in the frontend by owl as t-key. Those line_id not being unique would result in a crash in the front-end framework (only from 17.0 as OWL is used starting version 17.0 on accounting reports). Before the commit: There isn't any test performed on the line_id property. After the commit: assertLinesValues will make sure th
Original PR description
The aim of this commit is to add an extra security in the test of the reporting framework. Context: Those line_id are used to recognize lines in the framework and also in the frontend by owl as t-key. Those line_id not being unique would result in a crash in the front-end framework (only from 17.0 as OWL is used starting version 17.0 on accounting reports). Before the commit: There isn't any test performed on the line_id property. After the commit: assertLinesValues will make sure that each line_id is unique for the generated data. Back-ports the following commits: - https://github.com/odoo/enterprise/commit/fa3f03d859a35595990f34606c0864f9868e13fc - https://github.com/odoo/enterprise/commit/74000d6d5c8435bcaad93f7baf143abdf8593064 - https://github.com/odoo/enterprise/commit/fed41d1b3042414823345d995eb173f7acb3c6dc Co-authored-by: Brice Bartoletti <bib@odoo.com> task-4063612 Forward-Port-Of: odoo/enterprise#70566 Forward-Port-Of: odoo/enterprise#68840
Community: https://github.com/odoo/odoo/pull/181488 Design Themes: https://github.com/odoo/design-themes/pull/940
Original PR description
Community: https://github.com/odoo/odoo/pull/181488 Design Themes: https://github.com/odoo/design-themes/pull/940
The common SAFT test class has tags that will be passed to all inheriting test classes. We don't want that. Hence, we remove to tags and let the lower level test classes define those test tags. Runbot error 99192 Forward-Port-Of: odoo/enterprise#70634
Original PR description
The common SAFT test class has tags that will be passed to all inheriting test classes. We don't want that. Hence, we remove to tags and let the lower level test classes define those test tags. Runbot error 99192 Forward-Port-Of: odoo/enterprise#70634
before this commit: On mobile devices, the `Locating new addresses` and `Set up token` Bootstrap alerts are overlapping. after this commit: On mobile devices, the `Set up token` alert only becomes visible after the `Locating new addresses` process has been completed. Task-3928322 Forward-Port-Of: odoo/enterprise#70552 Forward-Port-Of: odoo/enterprise#69822
Original PR description
before this commit: On mobile devices, the `Locating new addresses` and `Set up token` Bootstrap alerts are overlapping. after this commit: On mobile devices, the `Set up token` alert only becomes visible after the `Locating new addresses` process has been completed. Task-3928322 Forward-Port-Of: odoo/enterprise#70552 Forward-Port-Of: odoo/enterprise#69822
## Description Currently the ebay module logs as `INFO` the whole content of the JSON response coming from the Ebay API. This can bloat excessively the logs of databases, forcing customers to quickly exceed their disk quotas. We can just log this type of information as a DEBUG log. ## Reference opw-4192547 Forward-Port-Of: odoo/enterprise#70626
Original PR description
## Description Currently the ebay module logs as `INFO` the whole content of the JSON response coming from the Ebay API. This can bloat excessively the logs of databases, forcing customers to quickly exceed their disk quotas. We can just log this type of information as a DEBUG log. ## Reference opw-4192547 Forward-Port-Of: odoo/enterprise#70626
Currently, a traceback is occurring if the net To reproduce this issue: 1) Install accounting 2) Create a confirmed customer invoice with a product and tax 2) Open `Tax report` report from reporting Error:- ``` TypeError: unsupported operand type(s) for /: 'float' and 'str' ``` This error is occurring after the recent changes from the commit https://github.com/odoo/enterprise/pull/68632/commits/f2bf719665dc3d19024d585e95d4913643b12572 We get `net_value` as an empty string from
Original PR description
Currently, a traceback is occurring if the net To reproduce this issue: 1) Install accounting 2) Create a confirmed customer invoice with a product and tax 2) Open `Tax report` report from reporting Error:- ``` TypeError: unsupported operand type(s) for /: 'float' and 'str' ``` This error is occurring after the recent changes from the commit https://github.com/odoo/enterprise/pull/68632/commits/f2bf719665dc3d19024d585e95d4913643b12572 We get `net_value` as an empty string from the below line https://github.com/odoo/enterprise/blob/7f3c71f03ff21dbfdda2763862f609445c4c9103/account_reports/models/account_generic_tax_report.py#L969-L970 But here `net_value` is used to calculate the error value, which leads to the above traceback https://github.com/odoo/enterprise/blob/7f3c71f03ff21dbfdda2763862f609445c4c9103/account_reports/models/account_generic_tax_report.py#L1076-L1077 sentry-5842821270 Forward-Port-Of: odoo/enterprise#70620