Daily updates from Odoo
Thursday, November 21, 2024
16 changes · saas-17.2
Resolved issues and error corrections
Several country-specific accounting localizations now install automatically when the main Accounting app is installed. This ensures businesses in affected SYSCOHADA countries get the correct accounting configuration without manual setup steps.
Original PR description
The dependency `l10n_syscohada` doesn't get installed automatically when account is installed, therefore these l10n don't get installed either. Each localization that had `countries` set in the manifest should have an `auto_install` containing the main app it is for.
The accounting demo setup now ensures a country is defined for the company. This prevents failures in automated checks that depend on country-specific accounting configuration, improving reliability for test and demo environments.
Original PR description
Fix for 1c5cc23b5eb3b59da10926688fc350b56397b550 Generic CoA sets the country on the company. Without one many tests fail. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
The existing FedEx implementation used the old FedEx SOAP API which is no longer in development. This new version makes use of the current REST APIs available at developer.fedex.com task-3759206 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186787
Original PR description
The existing FedEx implementation used the old FedEx SOAP API which is no longer in development. This new version makes use of the current REST APIs available at developer.fedex.com task-3759206 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186787
Since odoo/odoo@4d2aa271 we cannot add any manual field to `res.users`. We are always faced with the error: ``` ... fields used for ordering must be present on the model and stored. ``` The reason is that the `res.users.name` field is a related stored field, via inherits. Similarly if we install base_automation we cannot add any field to `base.automation` model, because they are ordered by `sequence`, another stored related field. In this patch we propose to extend the check for field
Original PR description
Since odoo/odoo@4d2aa271 we cannot add any manual field to `res.users`. We are always faced with the error: ``` ... fields used for ordering must be present on the model and stored. ``` The reason is that the `res.users.name` field is a related stored field, via inherits. Similarly if we install base_automation we cannot add any field to `base.automation` model, because they are ordered by `sequence`, another stored related field. In this patch we propose to extend the check for field used in `_order` to related fields. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187629
Description of the issue/feature this PR addresses: Commit [1] made sure that when pasting within blockquote and pre the pasted tag are not unwrapped. But the commit did not change the title as well as the describe of the test cases. This PR places the test cases at correct place. [1]: https://github.com/odoo/odoo/commit/460d88a20a908182e7e9aaf607816c0419a1c6bc --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187918 Fo
Original PR description
Description of the issue/feature this PR addresses: Commit [1] made sure that when pasting within blockquote and pre the pasted tag are not unwrapped. But the commit did not change the title as well as the describe of the test cases. This PR places the test cases at correct place. [1]: https://github.com/odoo/odoo/commit/460d88a20a908182e7e9aaf607816c0419a1c6bc --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187918 Forward-Port-Of: odoo/odoo#187724
**Steps to reproduce:** - Go to the `Todo` app. - Open a task. - Write any text. - Select the text. - Type `/command` - Hit Enter. **Description of the issue/feature this PR addresses:** The command is correctly added, but the issue is that the selected text is also re-added after the command is applied. **Desired behavior after PR is merged:** Selected text from before the `/command` will be removed and commands will still be executed. The process now involves clearing the c
Original PR description
**Steps to reproduce:** - Go to the `Todo` app. - Open a task. - Write any text. - Select the text. - Type `/command` - Hit Enter. **Description of the issue/feature this PR addresses:** The command is correctly added, but the issue is that the selected text is also re-added after the command is applied. **Desired behavior after PR is merged:** Selected text from before the `/command` will be removed and commands will still be executed. The process now involves clearing the content first and then launching the command. task-3487792 Forward-Port-Of: odoo/odoo#175808
### Steps to reproduce the issue: 1. Make sure you are in a company that is not a branch 2. Create a branch company 3. In the parent company, create an account group 4. In the branch company, create an account that should be set in the account group 5. The branch account is not set in the account group ### Explanation: When creating an account, we will enter `_adapt_accounts_for_account_groups` with a value for `account_ids`. As can be seen, `company_ids` is then assigned `account_i
Original PR description
### Steps to reproduce the issue: 1. Make sure you are in a company that is not a branch 2. Create a branch company 3. In the parent company, create an account group 4. In the branch company, create an account that should be set in the account group 5. The branch account is not set in the account group ### Explanation: When creating an account, we will enter `_adapt_accounts_for_account_groups` with a value for `account_ids`. As can be seen, `company_ids` is then assigned `account_ids.company_id.root_id.ids` which only corresponds to the id of the root company, not its branches. ### Fix reasoning: As asked by TSB, `account.group.company_id` can not have a `parent_id`, redirecting default value to `root_id`. `_accessible_branches` is only looking for active companies, the objective is to retrieve all children of `root_companies` (recursively). opw-4192988 Forward-Port-Of: odoo/odoo#182109
This commit fixes the direction of the arrows in the stock rules diagram if the user languange is right-to-left. opw-4302429 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187921
Original PR description
This commit fixes the direction of the arrows in the stock rules diagram if the user languange is right-to-left. opw-4302429 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187921
Before this commit, there was no check to see if the microphone was still needed when starting recording, which could leave the stream active with no reference to it. This commit fixes this issue by checking if the component is destroyed when the microphone promise is resolved. Forward-Port-Of: odoo/odoo#187870
Original PR description
Before this commit, there was no check to see if the microphone was still needed when starting recording, which could leave the stream active with no reference to it. This commit fixes this issue by checking if the component is destroyed when the microphone promise is resolved. Forward-Port-Of: odoo/odoo#187870
Related to https://github.com/odoo/enterprise/pull/73927 Forward-Port-Of: odoo/odoo#187468 Forward-Port-Of: odoo/odoo#187430
Original PR description
Related to https://github.com/odoo/enterprise/pull/73927 Forward-Port-Of: odoo/odoo#187468 Forward-Port-Of: odoo/odoo#187430
Prior to this commit, the `FormStatusIndicator` buttons were not properly aligned with the content of the breadcrumb in the control panel. This commit adjusts the alignment of `FormStatusIndicator` correctly according to the content of the breadcrumb. Also, to align the cog menu perfectly with the "save" and "cancel" buttons, we've removed the border around the latter two. task-3874495 | Before | After | |--------|--------| |  |  | |  |  | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186463
Steps to reproduce: 1. Drag and drop a text snippet. 2. Select background video and insert the video in the mediaDialog. 3. Click on the add button. Issue: A traceback occurs due to the tag name not being found for an element. This issue was introduced in commit [1]. Issue link: https://github.com/odoo/odoo/issues/186874 Solution: This PR resolves the traceback by adding a `parentEl` condition in the replace media on save function. [1] : https://github.com/odoo/odoo/commit/36594d04a
Original PR description
Steps to reproduce: 1. Drag and drop a text snippet. 2. Select background video and insert the video in the mediaDialog. 3. Click on the add button. Issue: A traceback occurs due to the tag name not being found for an element. This issue was introduced in commit [1]. Issue link: https://github.com/odoo/odoo/issues/186874 Solution: This PR resolves the traceback by adding a `parentEl` condition in the replace media on save function. [1] : https://github.com/odoo/odoo/commit/36594d04a8909dd40ab6384f387c372ddae62345 Forward-Port-Of: odoo/odoo#187793 Forward-Port-Of: odoo/odoo#186876
Issue: ====== sperator isn't inserted in the correct place. Steps to reproduce the issue: ============================= - Go to studio - Create a new internal report - Put the cursor in the div (second line) - Add some content over some lines - Insert seperator at the end of the lines - It gets inserted at the start Origin of the issue: ==================== Since we are writing inside the div directly, inserting the hr will look for the closest block and insert it before it whi
Original PR description
Issue: ====== sperator isn't inserted in the correct place. Steps to reproduce the issue: ============================= - Go to studio - Create a new internal report - Put the cursor in the div (second line) - Add some content over some lines - Insert seperator at the end of the lines - It gets inserted at the start Origin of the issue: ==================== Since we are writing inside the div directly, inserting the hr will look for the closest block and insert it before it which is the div. Because, new line inside a div is just a br and doesn't split the div. Solution: ========= Add a p element inside an empty div element when we put the selection there. task-4240730 Forward-Port-Of: odoo/odoo#183129
Before this PR, one-letter domain (like https://x.com) would not be linkified. This PR allows one-letter domain. Task-4344826 Forward-Port-Of: odoo/odoo#187924 Forward-Port-Of: odoo/odoo#187899
Original PR description
Before this PR, one-letter domain (like https://x.com) would not be linkified. This PR allows one-letter domain. Task-4344826 Forward-Port-Of: odoo/odoo#187924 Forward-Port-Of: odoo/odoo#187899
In #173866, the IoT configuration files were merged into one file. However, a logic check in `wireless_ap.sh` was inverted in the process, causing it not to wait for an IP. This PR simply restores the `!` to fix the check. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187862
Original PR description
In #173866, the IoT configuration files were merged into one file. However, a logic check in `wireless_ap.sh` was inverted in the process, causing it not to wait for an IP. This PR simply restores the `!` to fix the check. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187862
Follow-up of https://github.com/odoo/odoo/pull/186756 PR above improves push notification title in group chat without a name. The fix assumed that all members are partners, which is not necessarily the case. As a result, title contains `False` in conversation name and author when new message comes from a guest. This commit takes guests into account in push notification from new messages in channels as author. Group chat default name also uses guest names for the conversation name. Forw
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/186756 PR above improves push notification title in group chat without a name. The fix assumed that all members are partners, which is not necessarily the case. As a result, title contains `False` in conversation name and author when new message comes from a guest. This commit takes guests into account in push notification from new messages in channels as author. Group chat default name also uses guest names for the conversation name. Forward-Port-Of: odoo/odoo#187713