Daily updates from Odoo
Thursday, July 25, 2024
11 changes
1 change
Resolved issues and error corrections
Website maps now wait for address lookup to finish before choosing the map center. This prevents maps from opening in the wrong place when coordinates are not already available, improving visitor experience on location pages.
Original PR description
Before this commit, the map could be wrongly centered if the longitude and latitude were unknown and localized on the fly using the JavaScript Geocoder API, as we did not wait for the result. Now, the code is reorganized as an async function, and we await all the promises before computing the map options.
10 changes
Resolved issues and error corrections
This fix resolves a system error that occurred when trying to enable Batch Transfers in Inventory settings on databases using Mexican EDI features. The issue was caused by a missing field reference that prevented the feature from being properly installed. Users can now successfully enable Batch Transfers without encountering errors.
Original PR description
When clicking on Batch Transfers in the settings to install stock_picking_batch on a database having l10n_mx_edi_stock_30 installed a traceback is raised due to the field l10n_mx_edi_is_delivery_guide_needed which is missing as it is removed in stock_picking_batch. Steps to reproduce: - Install l10n_mx_edi_stock_30 - In Inventory -> Configuration -> Settings - Check 'Batch Transfers', and Save A ParseError traceback appears. This commits aims to solve the issue by adding the field before its parent element is removed from the arch. Forward-Port-Of: odoo/enterprise#66798
Fixed an issue where sample values and button URLs in the WhatsApp Composer were not updating when users changed the WhatsApp template. Previously, the composer would display sample values from the initially selected template instead of the newly chosen one. Now, all sample values and dynamic URLs refresh automatically based on the selected template.
Original PR description
### Before this PR In WhatsApp Composer, the Sample Values do not update when changing the WhatsApp Template. Instead, it display the sample values from the initially selected template. This issue also occurs with the Button URL as well. ### After this PR The Sample Values for Free Text Fields and Button Dynamic URL will now update based on the selected WhatsApp Template. Task-3996935
This fix corrects a bug in the barcode scanning application where splitting a transfer line would incorrectly reset the source location to the warehouse default instead of preserving the original sublocation. When warehouse staff scan products from different shelf locations during internal transfers, the system now correctly maintains the original source location for the remaining quantity after a split occurs.
Original PR description
How to reproduce: ================= - Enable "Storage Locations"; - Create a product with a barcode and add some qty in a sublocation (e.g.: 10 products in Shelf 1); - Create an internal transfer from WH/Stock to WH/Stock for this product for at least 2 qty; - Confirm the internal transfer and open it in the Barcode app; - You can see you have one line, from WH/Stock/Shelf 1 to WH/Stock (if we follow previous example); - Scan one time the product, then scan another location (eg.: shelf2), the line will be split. => Issue here: the line for the remaining quantity has WH/Stock as source location instead of Shelf 1. Expected behavior: ================== The source location of the split line doesn't change. Explanation: ============ When a line is split, a new line is created for the remaining quantity. But the issue is, when a new line is created, it uses the picking's source location (or the previous scanned source) as the default location. OPW-4016136
This fix resolves an issue where appointment bookings in multi-company and multi-website environments were using the wrong company context, causing confirmation emails to be sent from the incorrect company. The system now correctly uses the company associated with the website where the appointment was booked, ensuring proper email delivery and company-specific settings are applied.
Original PR description
Before, in a multi company and mutli website setup, booking an appointment used the companies on the organizer for the context. This was leading to issue for appointment type in Website 2 tied to Company 2. Indeed the mails for the booking were sent with the context of Company 1 (value based on the allowed_company_ids of the user). Now, when website_appointment is installed, if a website is linked to the actual request we use the company tied to it. This ensure that we always use the correct company of the website for the creation of the event. We target 17.0 to avoid a behavior change in older stable as the multi website was officially supported for appointment type in that version. Could be backported if really necessary. task-3977787
The Mexican EDI stock module (l10n_mx_edi_stock_30) was failing to install on systems with large numbers of stock picking records due to excessive memory usage. This fix optimizes the installation process by manually creating database fields instead of performing automatic computations, allowing the module to install successfully even with large datasets.
Original PR description
Installation of l10n_mx_edi_stock_30 module can fail due to memory limit Having a large number of "stock.picking" records causes this due to the computations of the initial values of fields. Solving this requires creating the field columns and assigning the values manually, by overriding the _auto_init method. This allows us to skip the computations, to avoid the memory limit. opw-3846355 Forward-Port-Of: odoo/enterprise#60948
Fixed a display issue in the shop floor interface where the 'no content' message was incorrectly covering the entire screen, including the employee panel. The message now only appears for disabled workorders and is hidden on smaller screens, improving the overall user experience and screen real estate usage.
Original PR description
Before this commit, the 'no content' message was showing in the entire display, taking the employee panel account. Now, it is fixed, the message just stay at the disabled workorders, and when the screen is less than md, the message is hidded. Previous PR: https://github.com/odoo/enterprise/pull/62997 ### Before  ### After  task: 3794286
When a printer is removed from an IoT device, users previously saw a confusing error message. This fix now detects the missing printer on the server side and automatically clears the saved printer preference, allowing users to select a new printer on their next print attempt instead of encountering an error.
Original PR description
Before this commit: Having a printer P saved in the browser cache as the printer for a report R. If the printer P is removed from the IoT device, a pop-up error will raise when R tried to be printed with an unclear "iot.device(X) is missing". After this commit: The missing device is detected on the server side, and the cache is automatically cleaned for this report so that on the next attempt, the printer choice pop-up appear. Also took the opportunity to clean the JS code on the modified functions :) opw-3965623 opw-4017201
This fix ensures that all employees see consistent weekend highlighting in the Time Off calendar view, regardless of whether they have an active contract. Previously, employees without contracts or with contracts starting after certain dates would not display the grey weekend cells. Now the system properly falls back to company working hours to display the correct schedule information for all employees.
Original PR description
### Steps to reproduce: - Install hr_holidays_contract_gantt module - Create two employees one with a contract and another without - Create a time off for each employee - Check Time Off -> Overview ### Current behavior before PR: The employee who has a contract will have grey cells on weekend days that are coming after his contract start date but the ones before will be white. The employee who has no contract won't have any grey cells neither for his off days nor the weekend days. ### Desired behavior after PR is merged: Both employees should show the grey cells in the gantt view whether they have contract or not because if so we fallback on the employee working hours and then company's working hours 'According to the PO' opw-3961873
Fixed an issue where installing HR payroll modules would fail if certain accounting codes had been customized. The system now logs a warning instead of blocking installation, allowing users to proceed even when expected accounts are missing. This improves the flexibility of the payroll setup process.
Original PR description
Problem --------- Currently, if you install l10n_xx and update some specific account codes (depending on the localization) and then try to install the corresponding l10n_xx_hr_payroll_account hr module, you are struck with an error that cancels the installation as some accounts are missing. 1. Install l10n_ae for example 2. Switch to AE company 3. Update the account with code 201002 to 701002 4. Install l10n_ae_hr_payroll_account -> Error occurs during the installation Objective --------- Be able to install the module even when the account is missing. Solution --------- Log a warning instead of raising an error. opw-3961798
Planning users were unable to view published shifts when draft shifts existed at the same time due to missing access permissions. This fix grants planning users the necessary access to draft shifts so they can properly view and manage shift conflicts without encountering errors.
Original PR description
We are facing an access error when the planning user tries to access the conflict shift because we have not given the planning user access to the draft shift. Steps to reproduce: - Install the planning app - Go to planning - Create two shifts at the same time (one published and the other in draft) - Create a new planning user - Log in as the planning user - Open the published shift task-3823274