Wednesday, November 15, 2023
13 changes · 17.0
Resolved issues and error corrections
This fixes an issue that could cause the Point of Sale order screen to crash when showing sales order lines. The change ensures the needed screen context is available so staff can view and manage related orders without interruption.
Original PR description
`Orderline.getDisplayData()` relies on the presence of the component's `env`. However, since 7dd76be303b6769767ef0736ba738fc0063a4a28, an `Orderline` instance can be created without `env`, which results to a traceback when rendering the order widget. This commit makes sure the `env` is present in the Orderline instance created from pos_sale module. Closes runbot error: 27820 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue on Safari where website pages could still scroll behind the mobile menu after it was opened. Visitors using mobile navigation get a cleaner, more stable browsing experience without unintended page movement.
Original PR description
Since [commit 1] replaced the mobile menu, a bug appeared on Safari where the `#wrapwrap` element would still be scrollable even with the menu open and even though the `body` has `overflow: hidden;`. This commit fixes it. [commit 1]: https://github.com/odoo/odoo/commit/bc13176de8d66bbdc1c536017b1f046c5fd31a86 task-3584299
This update fixes an intermittent failure in a mobile test flow by ensuring the next record is fully displayed before trying to edit it. It improves test reliability without changing any user-facing business behavior.
Original PR description
Since the commit afdcf9a5d5cd0d25b2ba61167d3ae6726a97d554, the mobile main flow tour fail sometimes. This is due to the fact that the tour try to edit the record before the new record is displayed. The solution is to wait for the new record to be displayed before trying to edit it. 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 restores the missing desktop spacing between the message filters and the New Message action in the Messaging menu. It improves visual clarity and prevents the controls from appearing cramped after a previous mobile-focused update.
Original PR description
Follow-up of [1] PR above made several improvements to Messaging Menu, especially in mobile. By mistake, it removes the spacing between "All"|"Chats"|"Channels" and "New Message" in desktop. This commit re-adds this spacing with `div.flex-grow-1`. [1]: https://github.com/odoo/odoo/pull/140405 Before/After  
This fixes a visual issue where the file drop area background did not appear in embedded live chat. The change keeps the live chat upload experience consistent in both light and dark modes.
Original PR description
Before this PR, the dropzone background was not showing on the embed live chat. The dropzone is displayed as a `main component`. In the Odoo frontend, the main component container is displayed outside of the live chat shadow dom, where the `bg-view` class is not available. This commit replaces this class by the `bg-100` one that is almost the same and available in the frontend. task-3595537 Before/After - Light:  Before/After - Dark: 
Module imports now handle static file paths that contain spaces when creating attachments. This prevents import failures for modules that include files or folders with spaces in their names.
Original PR description
When we are importing a module and we need to create an attachment from a file in static. We get an error if the file path of the file contains a space. We get this error becuase it takes the path to generate an xml id and the name of an xml_id cannot contains spaces. 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
Repair order line items now default to a quantity of 1, avoiding accidental overstatement based on the main repair quantity. The repair screen also uses clearer forecasted availability wording and removes a redundant quantity-clearing button to reduce confusion.
Original PR description
This commit fixes the following issues: 1. Before this commit, when adding a new move in a repair order, its default quantity was equal to the repair order's product quantity. The move's quantity should be 1 by default; 2. The `forecast_availability` is renamed from "Reserved" to "Forecasted"; 3. Removes the "Clear Quantities" button since it does basically the same thing than the "Unreserve" button.
The manufacturing order overview now opens correctly even when some work orders have no expected duration set. This prevents a division-by-zero error, helping users review manufacturing details without interruption.
Original PR description
Opening the Overview of manufacturing orders containing work orders without expected duration gives a division by zero. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a problem that caused the Purchase tour test to fail when launched from debug mode. The change keeps the guided purchase workflow test compatible with recent internal code changes, helping ensure purchase-related features remain reliably tested.
Original PR description
Steps to reproduce ================== - Install purchase_tour - Enable debug mode - Click on the debug menu - Click on Start tour - Run the purchase_tour tour in test mode `TypeError: Cannot read properties of undefined (reading 'apply')` See https://github.com/odoo/odoo/pull/125716 opw-3595512
Fixed an issue where the fuel type wasn't displaying when employees selected a new car model in their contract. The system now correctly shows fuel type information whether a car is selected from existing inventory or as a new car model. This ensures accurate vehicle information is always visible in employee contracts.
Original PR description
https://github.com/odoo/enterprise/pull/34883 started showing the fuel type of the car_id in the form view of hr_contract. However, when selecting new cars, the car_id won't be set. Instead we'll set the new_car_model_id field and the fuel type won't be shown. This commit changes the fuel_type field in hr_contract to be a computed field that will either take the fuel_type from car_id or from new_car_model_id. task-3515936 Forward-Port-Of: odoo/enterprise#47717
A white gap that appeared on the right side of the room booking interface has been fixed. The issue was caused by a missing CSS class that controls how the layout adapts to larger screens. Adding this class ensures the interface displays properly without unwanted spacing.
Original PR description
Prior to this commit, there was a white gap on the right side in the frontend view. This was due to a missing class enabling the column size to be set correctly on large screens. To fix that, this commit introduces this missing class. task-3592631
This update reorganizes how the recruitment module handles credit purchasing functionality. The credit widget has been moved to the specialized recruitment extraction module where it's actually used, removing an unnecessary dependency. This improves the system's organization and makes the code cleaner without affecting how recruitment features work.
Original PR description
The recruitment settings were using the iap_buy_more_credits widget, even tho there is no hard dependency between IAP and Recruitment. The widget has been moved to the enterprise module `hr_recruitment_extract`. Closes odoo/odoo#114747 Forward-Port-Of: odoo/enterprise#49576 Forward-Port-Of: odoo/enterprise#37959
This fix improves the user experience when working with embedded views in knowledge article templates. The toolbar that appears next to embedded content is now easier to click and visually appears properly connected to the content, rather than floating above it. This makes the interface more intuitive and responsive for users creating or editing knowledge articles.
Original PR description
This commit slightly adapts the template data to add a br element after the hr separator, which is necessary to be able to easily click on the embed view toolbar that appears right next to it. In addition, we modify the toolbar styling to make it appear "connected" to its embed view rather than floating a few pixels above it.