Monday, February 10, 2025
12 changes · 18.0
Resolved issues and error corrections
This fixes an error that could appear when a user enabled secure hashing for posted accounting entries and immediately returned to the dashboard before any entries were hashed. The dashboard now handles that transition safely, helping accounting users avoid an unexpected interruption.
Original PR description
**To reproduce:** 1. Check the field 'Secure Posted Entries with Hash' in a journal with existing entries 2. Immediately return to the Dashboard, before posting new entries 3. An error is raised…
**To reproduce:** 1. Check the field 'Secure Posted Entries with Hash' in a journal with existing entries 2. Immediately return to the Dashboard, before posting new entries 3. An error is raised **Cause:** In odoo/odoo#196748, the secured group usability was changed to only grant access to the new features relating to securing entries if moves from a journal without "Hash on Post" are secured. However, if before any entries are hashed, either by posting a new move in a journal with 'Hash on Post' or using the 'Secure Entries' wizard, the user returns to the dashboard, an error is raised. This is due to _get_chains_to_hash() being called with early_stop = True, in which case chain_info is an int. **Fix:** The key 'journal_restrict_move', which information on whether the journal is 'Hash on Post' to chain_info, should only be added after the function returns True in case of early_stop. This avoids the item assignment on an int. no-task --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes an issue that could cause errors when Point of Sale data was updated using a specific internal update command. It helps keep related sales information processing reliably and reduces the chance of interruptions for users.
Original PR description
Fix error with "set" command in related models.
This fixes an intermittent issue in automated checks where a button could be treated as hidden even though it was present. The change makes the two-factor authentication flow tests more reliable, reducing false failures and helping teams ship updates with greater confidence.
Original PR description
Fix nondeterministic JS errors of button trying to be clicked while detected as not visible (while being there). HOOT rely on DOM mutation to check if elements visible state change or not. We suspect if the tab load fast enough the button will be considered invisible as the fading didn't started yet. The issue is nondeterministic but fail more consistently by toggling Chrome CPU to 10x, it will then fail 3/4 of the times rb-112019
This fixes cases where the HTML editor could record unintended background changes while users changed selections or undid embedded content. The fix helps keep undo history cleaner and prevents unexpected editor behavior without changing normal editing workflows.
Original PR description
This PR handles 2 cases of ghost mutations generation: When switching the selection, the hint plugin generated mutations that were not part of a step. They should be ignored. When undoing the insertion of nested embedded components, the post-processing allowing for OWL Component destruction was generating ghost mutations. They should also be ignored. See commits for further details task-4561045
This fix removes two unsupported text matching options from the condition editor used in Studio. Users will no longer hit an error when configuring required-field rules, improving reliability while editing views.
Original PR description
Example of steps:
- Install `web_studio`
- Open any view editor with `web_studio`
- Try to edit a field required condition
- Pick a char field
- Add `starts_with` or `ends_with` operator
- Traceback
The solution is to remove these two operators from expression_editor as
this is not a python expression,
`starts_with` and `ends_with` are interpreted as `=ilike`, but there is
no way to translate it easily to a python expression like for `=`, `>=`, etc..
opw-4551688This fix makes several automated website walkthroughs more reliable by adding checks that ensure each test is on the correct path before continuing. It reduces unpredictable test behavior across website, eCommerce, recruitment, live chat, blog, and eLearning areas, helping maintain release stability without changing customer-facing features.
Original PR description
In this commit, we fix multiple tours on step that can cause non deterministic behaviors by adding additionnal steps to ensure tour is well on the way to taking the right path. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes an automated mail template test more reliable by allowing enough time for the page content to render after opening a dropdown. It helps reduce false test failures and keeps development checks stable without changing customer-facing behavior.
Original PR description
mail_template_dynamic_placeholder_tour is failing, as the delay between two steps is too small and dom is rendering right after clicking the dropdown. this pr fixes the issue. [failing runbot builds](https://runbot.odoo.com/odoo/action-573/111986) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A broken automated website page properties test has been fixed and re-enabled. This helps ensure website page settings continue to work correctly and reduces the chance of regressions reaching users.
Original PR description
In this commit, we make the fixes in order to reactivate the tour. runbot-error-id~106391 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Chatbot steps that ask users to choose an answer can no longer be saved without any available answers. This prevents live chat bots from failing during testing or customer conversations.
Original PR description
*= crm_livechat, website_livechat **Current behavior before PR:** It was possible to save a step with step_type set to "question selection" without any answers. However, this would cause an error when the bot was tested or executed. **Desired behavior after PR is merged:** A constraint has been added to ensure that a "question selection" step cannot be saved without at least one answer. task-id:4522835 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Worldline payment cancellations and declines are now recognized correctly instead of being shown as invalid transaction statuses. This helps staff understand failed checkout payments more clearly by showing the relevant error code and marking canceled payments appropriately.
Original PR description
Versions -------- - 18.0+ Steps ----- 1. Go to eCommerce; 2. add items to cart; 3. go to checkout; 4. pay with Worldline; 5. on Worldline's site, cancel transaction; 6. open order in the backend. Issue ----- Chatter displays: > Error: Worldline: Received invalid transaction status CANCELLED Cause ----- The cancel & declined statuses aren't handled when processing Worldline's response, leading to them being displayed as invalid. Solution -------- Handle the `cancel` and `declined` statuses and display the given error code. Also, when canceled, call `_set_canceled` instead of `_set_error`. opw-4481602
The Chilean PoS localization now detects when the required 'Consumidor Final Anónimo' customer record has been archived and shows a clearer message instead of failing unexpectedly. This helps store staff and administrators understand the setup issue quickly so the PoS can be restored with less disruption.
Original PR description
Before this commit, if the 'Consumidor Final Anónimo' partner was archived, attempting to open the PoS would lead to an error. This commit shows a clearer error message. opw-4506474
This update stops helpdesk live chat bot question steps from being saved unless they include at least one answer option. This prevents errors when the bot is tested or used, making chatbot setup more reliable.
Original PR description
**Current behavior before PR**: It was possible to save a step with step_type set to "question selection" without any answers. However, this would cause an error when the bot was tested or executed. **Desired behavior after PR is merged**: A constraint has been added to ensure that a "question selection" step cannot be saved without at least one answer. **task-id**:4522835