Thursday, February 13, 2025
13 changes · 17.0
Resolved issues and error corrections
Editing an existing link with three or more digits no longer automatically changes it into a phone number link. This prevents website editors from unintentionally breaking normal links while still allowing phone links when they are clearly intended.
Original PR description
**Behavior before PR:** When user edits link and inserts 3 or more digits, link url gets converted to telephone url. This happens because in sanitize.js `deduceURLfromText` method converts url to telephone url if label matches the regex. **Behavior after PR:** Now, inserting 3 or more digits will not convert existing url to telephone url directly. If current link is telephone url or label starts with `"tel:"` prefix then url will get converted to telephone url if label matches the `PHONE_REGEX`. task-4173806 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The mail suggestion search now correctly uses the words entered by the user when ranking or returning suggestions. This fixes a small typo that could make searches less relevant, and adds a test to prevent the issue from coming back.
Original PR description
Since odoo/odoo#128570, there was a typo in `sortPartnerSuggestions` (`searchTerms` instead of `searchTerm`) which caused searchTerm to have no effect. This PR fixes that typo and adds a test to make sure the searchTerm is included in the returned suggestions.
This fixes an issue where part of a dropdown in some Kanban boards could not be selected. Users can now click the full dropdown area reliably when working with records such as tickets, tasks, or events.
Original PR description
 In some kanban views (helpdesk.ticket, project.task, event.event), the right part of the selection dropdown can sometimes be inoperative because it falls below the `o_column_quick_create` element. This element has a higher z-index than the `o_kanban_group` which the dropdown is part of. opw-4507121
The Project onboarding tour now works correctly after users switch languages. This prevents translated interfaces from breaking the guided setup experience, helping users complete onboarding reliably.
Original PR description
Steps to reproduce: - Run project tour. - Change the language - Proceed with the tour Isuse: - The tours fails. Problem: - It is due to the triggers using english text in :contains. Fix: - Replace all the :contains with concrete triggers. task-4479518
The web editor now places the cursor outside a link when users click at the start or end of a line containing that link. This prevents the link editing overlay from appearing unexpectedly and lets users type next to links without extra keyboard steps.
Original PR description
Steps to reproduce: - Set up the editor with a link at the end of a line. - Refresh to start with fresh content. - Place the cursor at the end of the line with the link. - Notice that the cursor defaults inside the link, displaying the green overlay. - Attempt to type after the link—this requires pressing right arrow key to exit. Description of the issue/feature this PR addresses: - Clicking at the end or start of a line with a link placed the cursor inside the link by default, displaying the green overlay. - Typing outside the link required pressing the arrow key. Current behavior before PR: - Placing the cursor at the start or end of a line with a link now defaults to positioning it outside the link. - Green overlay is no longer shown, enabling direct text entry beside link. - Accessing the link requires an intentional left or right arrow key press. task-4089085
Holding the right arrow key in the search bar no longer triggers repeated lookup requests. This reduces unnecessary server activity and keeps search interactions smoother for users.
Original PR description
Steps to reproduce: 1. Write anything in a searchbar 2. Navigate on togglable item 3. Press arrowleft 4. Hold arrowright -> It will spam name_search queries We fix this by checking that the "arrowright" event isn't held (repeat=false). Task: 4476832 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Portal users who can edit knowledge articles will no longer see an access error when they try to publish an article they are not allowed to publish. This keeps the editing experience smoother while respecting existing publishing permissions.
Original PR description
Steps to reproduce ============= 1. Allow edit access to portal user. 2. Try to publish an article from the portal user. The portal user has no right to publish/unpublish articles. After this commit ============== This commit prevents access error when portal users try to publish an article. Task-4414401
This update corrects how country codes are handled in the Swiss payroll ELM transmission process. It helps prevent payroll transmission failures and reduces disruption for HR teams processing Swiss payroll.
Original PR description
This commit fixes the country code field to prevent errors. Runbot Error: https://runbot.odoo.com/odoo/runbot.build.error/116683 and others.
This update prevents an unnecessary error from appearing when creating Knowledge articles in certain cases. It makes the template validation happen at the right point, improving reliability for users working with Knowledge content.
Original PR description
Bug === In some situation, it's possible that the `is_template` raises when it shouldn't. It's more consistent to check it after the creation (super call). Task-4571151
Miscellaneous changes
When doing an export, a lot of information are computed depending on the partner, the company and the transaction. This commit will modify the field Invoice Type Transaction which is defined in a structure of 7-digit code: Standard Invoice must have 01 as the first 2 digits and 02 for simplified tax invoice. Other 5 digits depend on nature of the transaction. Before this commit we used to send for Individual contacts, 0200000 for all invoices, where the country of the Customer is not Sa
Original PR description
When doing an export, a lot of information are computed depending on the partner, the company and the transaction. This commit will modify the field Invoice Type Transaction which is defined in a structure of 7-digit code: Standard Invoice must have 01 as the first 2 digits and 02 for simplified tax invoice. Other 5 digits depend on nature of the transaction. Before this commit we used to send for Individual contacts, 0200000 for all invoices, where the country of the Customer is not Saudi Arabia. But it's actually wrong and we should send 0100100 which is a simple export invoice. To fix that issues we added a condition for an invoice to be simplified that the partner need to be an individual from Saudi Arabia. task-4504987 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#195216
Before this commit, due to the group place on the setting, the cash basis option was not displayed to user with only invoicing. Now, we want the user (with only invoicing) to be able to see it but not modifying the account on the settings. It will allow the users to choose the tax exigibility on the taxes, which for french user is important since depending on that the sentence "Option to pay tax on debits" will be displayed on the invoice. task: 4342603 --- I confirm I have signe
Original PR description
Before this commit, due to the group place on the setting, the cash basis option was not displayed to user with only invoicing. Now, we want the user (with only invoicing) to be able to see it but not modifying the account on the settings. It will allow the users to choose the tax exigibility on the taxes, which for french user is important since depending on that the sentence "Option to pay tax on debits" will be displayed on the invoice. task: 4342603 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#190995
Steps to reproduce: - Run helpdesk tour. - Change the language - Proceed with the tour Isuse: - The tours fails. Problem: - It is due to the triggers using english text in :contains. Fix: - Replace all the :contains with concrete triggers. Also changed some tour steps pointer orientation as it doesnt sit right in some conditions(gets broken/ partially invisible) task-4479518 Forward-Port-Of: odoo/enterprise#77398
Original PR description
Steps to reproduce: - Run helpdesk tour. - Change the language - Proceed with the tour Isuse: - The tours fails. Problem: - It is due to the triggers using english text in :contains. Fix: - Replace all the :contains with concrete triggers. Also changed some tour steps pointer orientation as it doesnt sit right in some conditions(gets broken/ partially invisible) task-4479518 Forward-Port-Of: odoo/enterprise#77398
The assistant to create relation filters only suggested a limited amount of related models, namely the direct co-models of the available datasources. This limitation was quite bothersome if a user wanted to filter on another model that did not have a direct link to the datasource models. Task-4572098 Forward-Port-Of: odoo/enterprise#79183
Original PR description
The assistant to create relation filters only suggested a limited amount of related models, namely the direct co-models of the available datasources. This limitation was quite bothersome if a user wanted to filter on another model that did not have a direct link to the datasource models. Task-4572098 Forward-Port-Of: odoo/enterprise#79183