Tuesday, December 3, 2024
6 changes · 17.0
Resolved issues and error corrections
This fix prevents an error when a point-of-sale order line has a quantity of zero. It helps ensure orders using manufacturing-related products can be processed without interruption in this edge case.
Original PR description
Before this commit, if the orderline quantity was zero, it would cause a division by zero error when calculating the anglo-saxon price unit. opw-4370055 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website link suggestion feature is now properly available when editing links in mass mailing content. This fixes a mismatch where users saw a prompt to search with “/” but the search did not respond, making it easier to add the right links in marketing emails.
Original PR description
Issue: ====== url autocomplete doesn't work in mass mailing Steps to reproduce the issue: ============================= - Install website - Create a new mass mailing - Choose welcome message - Select some text and click on the link icon on the toolbar in the snippets sidebar - You will see the hint of `type / to search ....` - If you type that nothing happens Origin of the issue: ==================== The behavior of autocomplete was added only in website but the hint was added for the linkTools in general. Solution: ========= Patch linkTools to include the behavior too. opw-4318224
This update resolves a problem where email layouts for sign requests weren't correctly translated into the recipient's language. Previously, emails used the sender's language for all content, regardless of the recipient's preferences. Now, emails will consistently use the language specified in the request, ensuring accurate translations and a better user experience.
Original PR description
**Email layout is not translated to targeted sender's language with Sign mails** Impacted versions: - 16.0 - 17.0 - 18.0 Steps to reproduce: 1. Create a partner with language other than the current…
**Email layout is not translated to targeted sender's language with Sign mails** Impacted versions: - 16.0 - 17.0 - 18.0 Steps to reproduce: 1. Create a partner with language other than the current user's language. 2. Create a sign request and send the request to the created partner. 3. The strings from the email layout like Odoo's `Powered By` and `Your Document` (Your Signature Request) are not translated to the partner's language, but translated with the user's language. This differs from the language in the body. Current behavior: Before this commit, the language of the logged in user and the language given in kwargs would be used to translate the content. The email layout would translate to the user language and the body content would use the kwarg's language. This lead to translation discrepancies. Expected behavior: After this commit, only the language given in the kwargs is used and therefore fixing the translations issues. Forward-Port-Of: odoo/enterprise#73784
This update fixes an issue where branch companies couldn't select accounts from their parent company when creating assets. Now, users can choose accounts from the parent company, streamlining the asset creation process and ensuring accurate accounting across the organization. This improves efficiency and data consistency.
Original PR description
**Steps to reproduce:** - Install Accounting - Create a Branch company without COA - Switch to the Branch company - Go to "Accounting / Accounting / Management / Assets" - Create an asset - Try to select an account for "Fixed Asset Account", "Depreciation Account" or "Expense Account" **Issue:** The list is empty. The accounts from the parent company should be proposed. opw-4368887
This update fixes a bug that prevented users from editing the justification field within employee skill assessments. By adding a simple setting, the system now correctly allows editing of this field, ensuring accurate and up-to-date skill evaluations. This improves the usability of the appraisal process.
Original PR description
Added `editable="bottom"` to the tree view of `skill_ids` in the `Skills` tab of the `hr.appraisal` form. This ensures the `justification` field and other tree fields are editable when allowed. Resolves an issue where the `justification` field was rendered as read-only. Steps to reproduce: 1. Go to Appraisal 2. 3. Chose any employee and go to their skills 4. Try to edit the justification field opw-4334153
This update resolves a bug that caused a traceback when updating planning slots without recurrence settings. The fix adds a check to handle cases where recurrence information is missing, preventing errors and ensuring smooth slot updates. This improves the reliability of the planning module.
Original PR description
Currently, a traceback occurs when the user tries to update the planning slot but has no recurrence. To reproduce this issue: 1) Install planning 2) Open any existing Open Shift planning slot 3)…
Currently, a traceback occurs when the user tries to update the planning slot but has no recurrence. To reproduce this issue: 1) Install planning 2) Open any existing Open Shift planning slot 3) Enable the `repeat` and update the start and end date 4) Give the edit value as `All shifts` and make sure the resource be empty 5) Save the record. Error:- ``` IndexError: tuple index out of range ``` Here the `resource` is not required in planning slot. So, when the user tries to update an open shift with the `repeat` enabled and `resource_update` as `all`, it leads to a traceback from the below line. https://github.com/odoo/enterprise/blob/64fc38a80520cfeeb81c0bb329c6b24c3e9454e1/planning/models/planning.py#L866-L871 This is because when there is no `recurrence_slots` in the slot, we get an empty recordset for the `recurrence_slots`, which leads to the above traceback when trying to extract a value from the recurrency_slots. We can resolve this issue by adding an extra check of `recurrence_slots` which makes the code more robust. sentry-6096445646