Thursday, September 12, 2024
14 changes · 17.0
Enhancements to existing features
The POS display screens now use a blurred background behind device and pairing code boxes. This makes important information easier to read and improves the setup experience for users.
Original PR description
Added blur on pos display devices and pairing code boxes background to ease readability and improve user experience.
Resolved issues and error corrections
Guest users in live chat and mail could see a “Download Files” option that they were not allowed to use, causing an error. The update hides that option for non-internal users, preventing failed downloads and creating a smoother guest experience.
Original PR description
Download files are restricted to the internal users by acl. This commit adapts the UI so the feature would not be available for non-internal users. Steps to reproduce: - Go to a public channel as a guest - Send a message with multiple attachments - Try to download all of them by clicking on Download Files in the message action menu - It crashes with Forbidden error
Miscellaneous changes
JQuery ajax was supporting extra headers sent along with the HTTP request, but this was no longer possible with the new RPC service. With this commit, we reintroduce this feature, so that extra HTTP headers can be specified by the caller. Forward-Port-Of: odoo/odoo#180055
Original PR description
JQuery ajax was supporting extra headers sent along with the HTTP request, but this was no longer possible with the new RPC service. With this commit, we reintroduce this feature, so that extra HTTP headers can be specified by the caller. Forward-Port-Of: odoo/odoo#180055
Industry modules now show Odoo S.A. as their author in the Apps list instead of appearing as unknown. This helps users identify the source of installed industry apps more clearly and avoids confusion in app listings.
Original PR description
Steps To Reproduce: - Install any industry module - Go to Apps, list view Current behaviour: author is displayed unknown Expected behaviour: author should display Odoo S.A. Task- 3959713
The stock forecast report now clearly highlights late purchase order lines in red again. This restores the expected visual warning so users can quickly spot supply delays that may affect deliveries.
Original PR description
### Steps to reproduce: - Create a storable product with 0 unit in stock - Create and confirm a Sale order for 1 unit fo that product - Create and confirm a Purchase Order for 1 unit of that product and an expected date further than the delivery date. - Click on the chart icon on the pol to be redirected to the forecast ### Expected behavior: The line should be displayed in red since the PO is late just as in 16.0 as the cell has the "".o_grid_warning" class. ### Current behavior: It is not. ### Cause of the issue: The `o_report_replenishment` class does not exist in 17.0 and the `table` class is used instead the html of the report so that the css file is not defining the color of the `o_warning` class correctly anymore. opw-4161304 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where changing the allocation type while creating a Time Off allocation could overwrite the name the user had entered. The allocation form now preserves the intended name, reducing rework and confusion for HR users.
Original PR description
### NOT FOR MASTER **17.0 -> Master - 0.1** Steps to reproduce the bug: - Go to Time Off -> Allocation -> Create - put a name - change the allocation type -> the name is reset Expected result: The name should not be reset to the old value Reason: The displayed name is relies on the private_name field to get its value. And thus every time an onchange is triggered the name is reset. Fix: Put the private_name field in the form view instead of the name field. Because we rely on the onchange of name on the dashboard to task-3713656 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The analytic module’s tests were updated to avoid relying on accounting or product features that are not part of its required setup. This helps single-app test runs complete reliably and reduces the chance of false failures during validation.
Original PR description
Before this fix `TestAnalyticMixin` used `product.product`, `account.move` and `account.move.line`, but `analytic` does not have these models in its dependencies. So this test causes `Single App` tests (when tests are run with just concerned modules and its dependencies) to fail. This commit adapts the tests so that they only use `account.analytic.*` models. original fix: https://github.com/odoo/odoo/commit/9d51fa9daee09e5467d38c5a890be7c0392d93f4 runbot error logs: https://runbot.odoo.com/web#id=74493&menu_id=405&cids=1&model=runbot.build.error&view_type=form
This fix removes the date granularity selection option from relative and from/to date filters in spreadsheets, where it was not applicable. The granularity option now only appears for period-based filters, making the interface cleaner and less confusing for users.
Original PR description
[FIX] *_spreadsheet_*: useless filter date granularity option In task 3887844 we added the possibilty to select which date granularities were available for a given period global filter. But this options was also displayed for relative and from/to global filters, where it made no sense. Task: [4176679](https://www.odoo.com/odoo/2328/tasks/4176679)
Steps to reproduce: - Include in your assets a CSS file with invalid formatting. - Translate your website in RTL language. > The website will never load and you will be left with a blank page. Cause of the issue: `rtlcss` never exit with a returncode, consequently our error management there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but only when using a CSS file. In our case, Odoo pass the CSS payload via the `stdin`. A PR [2] has been opened on `rtlcss` to also
Original PR description
Steps to reproduce: - Include in your assets a CSS file with invalid formatting. - Translate your website in RTL language. > The website will never load and you will be left with a blank page. Cause…
Steps to reproduce: - Include in your assets a CSS file with invalid formatting. - Translate your website in RTL language. > The website will never load and you will be left with a blank page. Cause of the issue: `rtlcss` never exit with a returncode, consequently our error management there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but only when using a CSS file. In our case, Odoo pass the CSS payload via the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return code in this scenario (and log details to `stderr`). In the meantime and also for earlier versions, the error management had to be slightly adjusted. As we cannot deduce any informations from the return code (and the `stderr` is completely empty), we can exploit the fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`. [1]: https://github.com/MohammadYounes/rtlcss/commit/4e625458cb236a4a21cb6d5e54283a9d5244fdc8 [2]: https://github.com/MohammadYounes/rtlcss/pull/342 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179784 Forward-Port-Of: odoo/odoo#178021
In this commit, we fix undeterministic bugs in tour add_to_cart_snippet_tour. To fix this behavior, we add few additionnal steps to check the state of DOM before continuing the tour. Forward-Port-Of: odoo/odoo#178788
Original PR description
In this commit, we fix undeterministic bugs in tour add_to_cart_snippet_tour. To fix this behavior, we add few additionnal steps to check the state of DOM before continuing the tour. Forward-Port-Of: odoo/odoo#178788
Duplicating languages wasn't possible because no logic was added to it, so it threw an error whenever trying to duplicate a language. The main reason is that when you try to duplicate a language, the ORM tries to create a new record with the same fields. However, the `name`, `code` , and `url_code` fields should be unique. This commit adds the needed logic to handle duplicating languages by adding a `(copy)` postfix to the fields. Task-4141689 Forward-Port-Of: odoo/odoo#179926 Forward-Port-O
Original PR description
Duplicating languages wasn't possible because no logic was added to it, so it threw an error whenever trying to duplicate a language. The main reason is that when you try to duplicate a language, the ORM tries to create a new record with the same fields. However, the `name`, `code` , and `url_code` fields should be unique. This commit adds the needed logic to handle duplicating languages by adding a `(copy)` postfix to the fields. Task-4141689 Forward-Port-Of: odoo/odoo#179926 Forward-Port-Of: odoo/odoo#179686
Check identity would previously store a wrong password until the next grabage collection. This commit fix this behaviour. Forward-Port-Of: odoo/odoo#179866
Original PR description
Check identity would previously store a wrong password until the next grabage collection. This commit fix this behaviour. Forward-Port-Of: odoo/odoo#179866
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ### Steps to Reproduce 1. With barcode installed, set the barcode nomenclature in settings to "Default GS1 Nomenclature" 2. Attempt to scan this barcode  3. If you debug [here](https://github.com/
Original PR description
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ###…
### Current Behavior: When scanning a barcode like attached, ascii 29 (FNC1) will be added to the beginning of the final code. ### Expected Behavior: FNC1 should be removed from the final code. ### Steps to Reproduce 1. With barcode installed, set the barcode nomenclature in settings to "Default GS1 Nomenclature" 2. Attempt to scan this barcode  3. If you debug [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L101), you will find that `barcode` starts with ascii 29, but it isn't removed. ### Details This commit adds ascii code 29 (FNC1) to the list of strings to be escaped from in gs1 decomposition. In PR #163404, logic was added to escape barcode scan results that start with FNC1. This is only specifically checking ']C1', but it is possible for the literal ascii code 29 to be present in the beginning of the string as well. This should also be escaped. You can see that ascii 29 is added in `zxing-library.js` [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/web/static/lib/zxing-library/zxing-library.js#L12308) in this case. It also could potentially be added in several other places such as [here](https://github.com/odoo-dev/odoo/blob/b387345f557adace35767ec2ca7ada271cca8423/addons/web/static/lib/zxing-library/zxing-library.js#L6932) opw-3965925 Forward-Port-Of: odoo/odoo#177958
Steps to reproduce the issue: ============================= - Switch to dark mode - Go to any record with a chatter - Open mail composer in log note - Add a table - Save - Switch to light mode - The table is still dark Origin of the issue: ==================== Since in dark mode we add some styles to improve the display, those styles are getting applied in convert_inline. Solution: ========= Skip the stylesheets for table that have color only for now since skipping all styles
Original PR description
Steps to reproduce the issue: ============================= - Switch to dark mode - Go to any record with a chatter - Open mail composer in log note - Add a table - Save - Switch to light mode - The…
Steps to reproduce the issue: ============================= - Switch to dark mode - Go to any record with a chatter - Open mail composer in log note - Add a table - Save - Switch to light mode - The table is still dark Origin of the issue: ==================== Since in dark mode we add some styles to improve the display, those styles are getting applied in convert_inline. Solution: ========= Skip the stylesheets for table that have color only for now since skipping all styles can produce more issues. We skip also the background-color and border color for light mode too because they will not display the same in dark mode. Before: ======   After: =====   opw-4137267 Forward-Port-Of: odoo/odoo#178520