Thursday, June 15, 2023
10 changes · master
Resolved issues and error corrections
This change adjusts an automated test so it waits for the system to finish updating a related field before checking the result. It helps prevent occasional false test failures, improving confidence in future updates without changing user-facing behavior.
Original PR description
To test the onchange on uom, the service type is first change. Checking the value of the uom input right after introduces underteministic behavior which makes the test fail in some cases. To try to solve this, another step is processed inbetween, before checking the value of the uom input. related-https://github.com/odoo/odoo/pull/105951
This fix prevents portal layouts from crashing when no language is set for a user or request. It improves reliability for customers accessing portal pages in edge cases where language information is unavailable.
Original PR description
language can be None -> we don't want to crash if that is the case --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Chat notifications now show special characters like angle brackets and ampersands exactly as sent. This avoids confusing escaped text in out-of-focus message popups and makes notifications easier to read.
Original PR description
**Before this commit:** In discuss when a user receives a message containing strings from any of these '>,<,&' it gets converted to `>,<,&` respectively. For example, if a user sends '<abc>', when the chat is out of focus, the toaster notification will show a notification with an escaped message i.e.`<abc>`. **After this commit:** The message will be shown as it is, in the toaster notification. **Task**-3284244
This fixes an issue in the Mail app where some conversation actions did not receive the information they needed to display or work correctly. It helps ensure mail and discussion interface actions behave reliably for users.
Original PR description
Since [1] thread actions are stored in a specific registry. Some of those actions require props to be passed to their component. Those props are not correctly passed as the `componentProps` key is in fact a function that returns the props but is treated as the props themselves. This commit fixes this issue by transforming `componentProps` into a getter, so that `action` is internally passed to `componentProps` definition. The templates using thread actions can still use `t-props="componentProps"` as getter, as the active action is deduced by transform automatically. [1]: https://github.com/odoo/odoo/pull/123454
Fixes an issue in Mail where removing an attachment from the message composer could cause the message to be sent twice. This prevents duplicate communications and reduces confusion for users and recipients.
Original PR description
When removing the attachment, message is sent twice.
Fixes an issue where users could not retry sending an invoice through Peppol after a previous attempt failed if the invoice XML had already been generated. The send wizard now keeps the Peppol option available and ensures the required XML is generated when Peppol sending is selected.
Original PR description
Currently: Create an invoice and send it using Peppol and make sure the PDF and the XML are well generated but Peppol failed for some reason. When opening the wizard later, the checkbox is no longer there since the XML is already generated. Fix: This commit adds `enable_peppol` to show the checkbox depending on this field, so that if there is already a ubl XML generated, we can still send an invoice via Peppol. Also, if the ubl generation is enabled but the ubl checkbox is not checked, and the user chooses to send via Peppol, we assume that the ubl XML needs to be generated as well. task-3358419 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures an existing IAP website test runs as part of regular nightly website checks. It also adds Arabic to the tested languages so translation quality for industry content can be verified earlier.
Original PR description
A test of IAP has been introduced by [this commit]. We want it to be part of the website nightly tests, so that we can easily check if it passes. [this commit]: https://github.com/odoo/odoo/commit/9177076caee4f83590704e3af8e51ec6f7eaa0bc --- This commit adds arabic in the list of iap languages so that we can test that the industries are correctly translated in arabic. related to task-3343616
This fix prevents an error when users open valuation details after completing a manufacturing order. It helps keep the manufacturing workflow running smoothly and avoids an unexpected interruption at a key accounting step.
Original PR description
Steps to reproduce --- - Create Manufacturing Orders and confirm it. - Validate the done quantities. - Click on valuation button. It will raise trackback Error caused by commit: a080337
This fixes an issue in Odoo Mail where some conversation actions did not receive the information they needed to work correctly. Users should see more reliable behavior when using mail discussion actions, especially flows such as channel invitations.
Original PR description
Since [1] thread actions are stored in a specific registry. Some of those actions require props to be passed to their component. Those props are not correctly passed as the `componentProps` key is in fact a function that returns the props but is treated as the props themselves. This commit fixes this issue by transforming `componentProps` into a getter, so that `action` is internally passed to `componentProps` definition. The templates using thread actions can still use `t-props="componentProps"` as getter, as the active action is deduced by transform automatically. [1]: https://github.com/odoo/odoo/pull/123454
This update fixes unstable automated tests in the Knowledge app that were repeatedly failing during internal build checks. It helps keep development and release validation reliable without changing the user-facing Knowledge experience.
Original PR description
This commit fixes a bug where the test `test_knowledge_template_command_tour` would be failing inside runbot build and create error on every runbot build. We removed te `@users` decorator from the test. task-3345004