Saturday, February 18, 2023
10 changes · master
New functionality added to Odoo
This change lets Odoo administrators and developers mark specific fields as unavailable in export dialogs. It helps reduce clutter and can prevent sensitive or low-value internal data, such as access tokens, from being exposed during exports.
Original PR description
Description of the issue/feature this PR addresses: Odoo has been growing and more and more technical fields have been added who either contain rather sensitive data or nothing useful for exporting.…
Description of the issue/feature this PR addresses: Odoo has been growing and more and more technical fields have been added who either contain rather sensitive data or nothing useful for exporting. See also the discussion at https://twitter.com/ggellatly/status/1524145898380738561
Current behavior before PR: Every single field in Odoo is by default shown in the export dialog causing an overload of info with quite often content shown that has no use (or should even be hidden for semi-security reasons).
Desired behavior after PR is merged:
By adding an attribute `exportable` on the `ir.model.fields` we can custom define which fields we want to be exportable or not.
For example: by default on the `sale.order` model the field `access_token` is by default exportable. If you'd flag the field as non-exportable it would no longer show up and thus not leak (rather sensitive) data:
```
# -*- coding: utf-8 -*-
from odoo import models, fields, api
class SaleOrder(models.Model):
_inherit = 'sale.order'
access_token = fields.Char(
exportable=False
)
```
By adding this configurable flag a developer could override any field and simply add the `exportable` flag which is set to `False`.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prEnhancements to existing features
This update refines the live chat module’s interface and related client-side components to make the customer chat experience cleaner and more consistent. It mainly improves presentation and maintainability, helping users interact with live chat more comfortably without changing core business workflows.
Original PR description
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
Resolved issues and error corrections
This update prevents crashes in Safari on macOS and iOS by replacing unsupported code used in the web interface. It improves reliability for users accessing Odoo from Apple devices across both frontend and backend screens.
Original PR description
Positive Lookbehind regex syntax is currently not supported yet by Webkit, and thus Safari (both on macOS and iOS) resulting into a crash as the syntax is not recognized. This issue affects both frontend and backend. This commit fixes it by reimplementing the feature without using this syntax. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
The default font size of the frontend is 16 so the `default` option in the font size dropdown was supposed to be enough for this use case. However, this is not true in the context of website_blog where the default font size of blog content is not 16. This is not a problem because if the user does not like the default blog font size then they can change it using the font dropdown... except they have no way to select 16 for a size and `default` doesn't mean 16 in blog. This commit adds an ex
Original PR description
The default font size of the frontend is 16 so the `default` option in the font size dropdown was supposed to be enough for this use case. However, this is not true in the context of website_blog where the default font size of blog content is not 16. This is not a problem because if the user does not like the default blog font size then they can change it using the font dropdown... except they have no way to select 16 for a size and `default` doesn't mean 16 in blog. This commit adds an explicit entry for 16 in the font size dropdown. opw-3110711 Forward-Port-Of: odoo/odoo#112993
Commit [1] removed the protection around the call to setDirty because setDirty is always defined when the field is initialized through the standard field.js mechanism. However, in todo_list.js in hr_payroll, the html field is called without going through that mechanism, resulting in the prop being missing and the call to fail with a traceback. This could be fixed by adding the missing prop to todo_list.js, but other people are likely to do the same mistake in the future so adding a default of
Original PR description
Commit [1] removed the protection around the call to setDirty because setDirty is always defined when the field is initialized through the standard field.js mechanism. However, in todo_list.js in hr_payroll, the html field is called without going through that mechanism, resulting in the prop being missing and the call to fail with a traceback. This could be fixed by adding the missing prop to todo_list.js, but other people are likely to do the same mistake in the future so adding a default of our own is probably better to avoid future similar bugs. [1]: https://github.com/odoo/odoo/commit/f56e3bca2456f04616982a9a0e77b8d4c5a0abff Forward-Port-Of: odoo/odoo#112885
Before this commit, the bus service test "tabs share message from a channel" was sometimes failing. This is due to the fact that it was only waiting a `nextTick` to receive the message but the message is not guaranteed to arrive within a tick. Indeed, the message is first sent from the worker `MessagePort` via `postMessage` then triggered on the event bus via `dispatchEvent`. Forward-Port-Of: odoo/odoo#112984
Original PR description
Before this commit, the bus service test "tabs share message from a channel" was sometimes failing. This is due to the fact that it was only waiting a `nextTick` to receive the message but the message is not guaranteed to arrive within a tick. Indeed, the message is first sent from the worker `MessagePort` via `postMessage` then triggered on the event bus via `dispatchEvent`. Forward-Port-Of: odoo/odoo#112984
To reproduce ============= - on settings upload a custom background on document layout and save it - open document layout again and try to download the image -> Traceback Problem ======= when calling download method we will ask server for a record with `id=false` which gives an error Solution ======== download button shouldn't be visible when `record.resId == false` opw-3138230 Forward-Port-Of: odoo/odoo#112857
Original PR description
To reproduce ============= - on settings upload a custom background on document layout and save it - open document layout again and try to download the image -> Traceback Problem ======= when calling download method we will ask server for a record with `id=false` which gives an error Solution ======== download button shouldn't be visible when `record.resId == false` opw-3138230 Forward-Port-Of: odoo/odoo#112857
This update conatins the following commit: - [IMP] devtools: provide access to Fiber and RootFiber - [FIX] props validation: do not subscribe to props keys - [FIX] reactivity: only show key in subscription if observed by callback - [FIX] components: stop rendering stale t-component when delayed More details at: https://github.com/odoo/owl/releases/tag/v2.0.6 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged:
Original PR description
This update conatins the following commit: - [IMP] devtools: provide access to Fiber and RootFiber - [FIX] props validation: do not subscribe to props keys - [FIX] reactivity: only show key in subscription if observed by callback - [FIX] components: stop rendering stale t-component when delayed More details at: https://github.com/odoo/owl/releases/tag/v2.0.6 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 Forward-Port-Of: odoo/odoo#113006
Forward-port of #94947 for 16.0+ --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#112900
Original PR description
Forward-port of #94947 for 16.0+ --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#112900
In the EAS list, the United Kingdom code is set to 'UK' while in Odoo, it should be 'GB'. Because of that, the UBL Bis 3 format doesn't appear in the journals for GB companies. opw-3169038 Forward-Port-Of: odoo/odoo#113013
Original PR description
In the EAS list, the United Kingdom code is set to 'UK' while in Odoo, it should be 'GB'. Because of that, the UBL Bis 3 format doesn't appear in the journals for GB companies. opw-3169038 Forward-Port-Of: odoo/odoo#113013