Daily updates from Odoo
Thursday, November 2, 2023
9 changes
1 change
Resolved issues and error corrections
The barcode app now filters manufacturing orders so users see only orders assigned to them or not assigned to anyone. This reduces clutter and helps employees focus on work they are responsible for.
Original PR description
In barcode app, we need to apply a responsible filter for manufacturing orders. Only MO that are assigned to the user or unassigned should be displayed.
8 changes
Resolved issues and error corrections
Fixed an issue where the copy-to-clipboard feature in the Knowledge module's /clipboard block wasn't properly capturing dynamically edited content. The fix switches from using a static copy button to directly using the browser's clipboard API, ensuring users can reliably copy content they've edited in real-time.
Original PR description
In [1], the `CopyButton` was introduced in the `/clipboard` block of `Knowledge` to replace `ClipboardJS`, but the content to copy is dynamic in edition so the content to copy should be given by a function and not a static value. [1]: https://github.com/odoo/enterprise/pull/47154 task-3571973
This fix resolves an error that appeared when users tried to open a payment link WhatsApp template in the system. The issue occurred when both the account tax and WhatsApp modules were installed together. After this fix, users can now open payment link WhatsApp templates without encountering any errors.
Original PR description
before this commit, on opening payment link whatsapp template, a traceback is shown to end user. * install account_avatax and whatsapp modules * whatsapp-> templates -> whatsapp templates * open payment link whatsapp template * traceback is shown  after this commit, no traceback is shown on opening payment link whatsapp template Forward-Port-Of: odoo/enterprise#47565
Fixed an issue where the product page layout was not properly adapting to the website width when all filter options (attributes and categories) were disabled in the Rental module. The page now correctly adjusts its width based on whether filters are actually available, improving the user experience and visual consistency of the shop page.
Original PR description
Before this PR, On the Products page(/shop), when all the options on the left panel(attributes and categories) are disabled, then the width of the page is not adapted to the width of the website. The issue occurs after installing the Rental(website_sale_renting) module because we set the value for [hasLeftColumn](https://github.com/odoo/enterprise/blob/16.0/website_sale_renting/views/templates.xml#L217) directly, so we always get hasLeftColumn(left panel) even after all options are disabled After this PR, we set the value for the left panel based on the condition so that when all the options are disabled the Product page adapts the width of the website task-3267971 Forward-Port-Of: odoo/enterprise#41616
This fix resolves an issue where scanning serial numbers for multiple components in a manufacturing order was incorrectly counting quantities. When scanning components with different serial numbers, the system was combining them into a single line item instead of tracking them separately. The fix ensures that each component is properly counted and the production order closes correctly when all components are scanned.
This fix resolves an issue where the representation fees calculation was trying to access a field that only exists when the Belgian contract salary module is installed. The functionality has been properly reorganized so that the representation fees behavior is now correctly handled within the Belgian contract salary module, preventing errors when this optional module is not active.
Original PR description
Before correction : The function _get_representation_fees_threshold used a field from hr_job. But this field exist only if l10n_be_hr_contract_salary is installed After correction : Put the behaviour of this function linked to this field in l10n_be_hr_contract_salary.
Fixed an issue where employee avatars were not displaying in the Planning module for users without direct access to employee records. The system now automatically falls back to public employee information to ensure avatars are always visible, improving the user experience for all planning team members.
Original PR description
In planning, avatar can be displayed for resource.resource, hr.employee and hr.employee.public records. Avatar of resource.resource records is a computed field that return the avatar of the hr.employee record linked to the resource if any. The problem is that not all user of planning have access to hr.employee records. This was not a problem in versions <16.0 but since, https://github.com/odoo/odoo/commit/85bd6e62a59fef3086a9ae2138209cc73f086227, access rights are checked when accessing an image through the route /web/images/<model>/<id>/<field>. This commit avoids empty avatar for employees by falling back on hr.employee.public avatar if the current user has no access to hr.employee model. Forward-Port-Of: odoo/enterprise#50006 Forward-Port-Of: odoo/enterprise#49560
This fix resolves an issue where creating a new human resource in the Planning module was not automatically generating a corresponding employee record. The problem was caused by a duplicate field declaration that prevented the necessary context from being passed. Now, when users create a human-type resource, an employee will be automatically created as expected.
Original PR description
Steps: - Install Planning module - Open the Planning module - Create the new resource - Then go to the Configuration's Employees - There is not created employee through the resource Before this commit, At the time of creating the new resource , shouldn't creating a human resource should automatically create an employee for that resource. This commit ensure that : Creating the human type resource will automatically creates an employee Task-3508241 Forward-Port-Of: odoo/enterprise#47589
This fix resolves an error that occurred when exporting Trial Balance reports to PDF after selecting a journal group. The system was attempting to save incompatible data (a set) that couldn't be converted to the required format, preventing the export from completing. The fix ensures all report data is properly formatted for export.
Original PR description
Create a test account journal group Go to Accounting -> Reporting -> Trial Balance Ensure the journal group is selected Click on the PDF export button Error will raise TypeError: Object of type set is not JSON serializable” This occurs because in the process of gathering options initializer the system add a `set` to the options, which is not json serializable opw-3564632 Forward-Port-Of: odoo/enterprise#49876