Friday, October 6, 2023
9 changes · master
Resolved issues and error corrections
This fixes a crash that occurred when users selected "Get View" from the debug menu. The debug tool now handles the updated view format correctly, helping administrators and support teams inspect views without interruption.
Original PR description
Since commit [1], there was a crash when the user clicked on the "Get View" item in the debug menu (in any views). This was because the arch now received by the views in props is an XmlDocument, whereas before it was a string. [1] odoo/odoo@cc3a3a328db913da76573404967e1190f40bcc98 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
Sales reports now group by the main product record rather than separating results by individual product variants. This makes product-level reporting match user expectations, while a separate grouping option remains available for product variants when that detail is needed.
Original PR description
Group by "Product" was grouping by product variant instead of product template. opw-3477918 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users who switch dark mode while working in the website backend now remain in the backend after the page reloads. This avoids unintentionally sending them to the public website page and makes the editing experience smoother.
Original PR description
*enterprise Since this task in community adds the user menu in the navbar, it is now possible to toggle the dark mode from the website backend. However, (1) toggling the dark mode reloads the page, and (2) since [commit 1], nothing in the displayed URL differentiates the frontend from the backend in the website app, meaning that reloading the page from the backend actually leads to the frontend page. This commit patches the `color_scheme_service` in order to remain in the backend if it is toggled from the website app. [commit 1]: https://github.com/odoo/odoo/commit/1c18b79972c3b0a97197b98390e0ba9fda703585 task-3381773
The recruitment document digitization message now uses "Resume" instead of "CV" when users do not have enough credits. This makes the wording clearer and more consistent for applicants and recruiters, with no functional change.
Original PR description
Change replaces word "CV" with word "Resume" in error message telling that you don't have enough credits to digitize document in application task-3539236
This update adjusts the Documents test suite to account for a brief delay before boolean toggle changes appear on screen. It helps keep automated checks stable and reduces the risk of false test failures after recent interface behavior changes.
Original PR description
The changes introduced to BooleanToggleField by the PR: https://github.com/odoo/odoo/pull/136924, mean that an update executed on a boolean field from a Component other than the BooleanToggleField displaying it requires waiting for one more nextTick for the change to be displayed. This is caused by useObserveRecord waiting for an animationFrame to execute its callBack and therefore in this case to apply the change of state to the BooleanToggleField.
This change fixes the WhatsApp point-of-sale settings so the receipt template can be selected when WhatsApp is enabled for POS. It prevents users from being blocked by a read-only field and restores the expected setup behavior.
Original PR description
before this commit, if the WhatsApp Enabled is pos setting the receipt template remains readonly and user cannot edit and change the template value after this commit, wrongly given invisible attribute will be changed to required attribute as in the lower version, ie, 16.3 and 16.4
This change makes an automated Studio test wait for an expected error before checking the result. It helps prevent random test failures, improving confidence in release validation without changing user-facing behavior.
Original PR description
This commit ensures the error event is handled before the assert in in the "error when new app's view is invalid" studio test. This could lead to an nondeterministic error in the test. runbot-error-24580
This update adjusts an internal performance test threshold for Australian payroll accounting to reduce false failures caused by variable caching and data volume. It helps keep automated validation reliable without changing payroll features or user workflows.
Original PR description
Those tests could have some random requests, as there are a lot of records and the cache could have some random behavior according to the execution order, the number of installed module, so I'm gonna just bump it a little bit.
This update fixes Avatax accounting tests by removing a dependency on a sales-related field that is not always available. It helps ensure the Avatax module can be tested reliably regardless of installation order, reducing the risk of false test failures.
Original PR description
removed the reference to field invoice_policy, added in a module this one doesn't depend on (sales). This has been wrong since a long time and was only put into light with the recent changes of 70329177713131d3d6ec424137cad3702e9d38ae (#136490) where the order of modules' installation changed, avatax being installed before sales.