Saturday, April 12, 2025
6 changes · saas-18.2
Miscellaneous changes
Problem: The inner content (text) of `oe-tabs` can be larger than the `span` itself, causing the selection to visually overflow outside the tab. Solution: Set `tab-size` to match `width` for `oe-tabs` to prevent the selection overflow. Steps to reproduce: 1. Add a tab between some text in the editor. 2. Select only the tab. 3. Notice that the selection (blue highlight) visually overflows outside the tab. opw-4711458 --- I confirm I have signed the CLA and read the PR guid
Original PR description
Problem: The inner content (text) of `oe-tabs` can be larger than the `span` itself, causing the selection to visually overflow outside the tab. Solution: Set `tab-size` to match `width` for `oe-tabs` to prevent the selection overflow. Steps to reproduce: 1. Add a tab between some text in the editor. 2. Select only the tab. 3. Notice that the selection (blue highlight) visually overflows outside the tab. opw-4711458 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#205130
Currently, when paying for subscriptions via credit card, eventhough it will force tokenization in the backend, it will only create single-use tokens. This is because creation of multi-use tokens is dependent on `paymentContext.tokenizationRequested` which is only True when the "Save my payment details" button is checked. However when paying subscriptions, this button is not there because it should be tokenized by default. With this commit, we're making sure that the creation of multi-use tokens
Original PR description
Currently, when paying for subscriptions via credit card, eventhough it will force tokenization in the backend, it will only create single-use tokens. This is because creation of multi-use tokens is dependent on `paymentContext.tokenizationRequested` which is only True when the "Save my payment details" button is checked. However when paying subscriptions, this button is not there because it should be tokenized by default. With this commit, we're making sure that the creation of multi-use tokens is reliant on whether the backend will tokenize it or not --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#205648
country_code has to be defined. Required field from Adyen. Falling back to the company country code or NL if the partner country is empty. opw-4698444 Forward-Port-Of: odoo/odoo#205723 Forward-Port-Of: odoo/odoo#205678
Original PR description
country_code has to be defined. Required field from Adyen. Falling back to the company country code or NL if the partner country is empty. opw-4698444 Forward-Port-Of: odoo/odoo#205723 Forward-Port-Of: odoo/odoo#205678
This commit is unlinking all demo categories before starting the tour. In this way we avoid different behavior in no-demo and demo databases. runbot error: 162972 Forward-Port-Of: odoo/odoo#205537
Original PR description
This commit is unlinking all demo categories before starting the tour. In this way we avoid different behavior in no-demo and demo databases. runbot error: 162972 Forward-Port-Of: odoo/odoo#205537
Using the enterprise feature Vendor Bill Scan, When the partner doesn't exists in the database the following traceback: ```py File "/home/odoo/odoo18/community/odoo/api.py", line 496, in _model_create_multi return create(self, arg) File "/home/odoo/odoo18/community/addons/mail/models/mail_thread.py", line 268, in create threads = super(MailThread, self).create(vals_list) File "<decorator-gen-31>", line 2, in create File "/home/odoo/odoo18/community/odoo/api.py", line 496,
Original PR description
Using the enterprise feature Vendor Bill Scan, When the partner doesn't exists in the database the following traceback: ```py File "/home/odoo/odoo18/community/odoo/api.py", line 496, in…
Using the enterprise feature Vendor Bill Scan, When the partner doesn't exists in the database the following traceback:
```py
File "/home/odoo/odoo18/community/odoo/api.py", line 496, in _model_create_multi
return create(self, arg)
File "/home/odoo/odoo18/community/addons/mail/models/mail_thread.py", line 268, in create
threads = super(MailThread, self).create(vals_list)
File "<decorator-gen-31>", line 2, in create
File "/home/odoo/odoo18/community/odoo/api.py", line 496, in _model_create_multi
return create(self, arg)
File "/home/odoo/odoo18/community/odoo/models.py", line 4968, in create
new_vals_list = self._prepare_create_values(vals_list)
File "/home/odoo/odoo18/community/odoo/models.py", line 5125, in _prepare_create_values
self._add_precomputed_values(result_vals_list)
File "/home/odoo/odoo18/community/odoo/models.py", line 5153, in _add_precomputed_values
records = self.browse().concat(*(self.new(vals) for vals in vals_list_todo))
File "/home/odoo/odoo18/community/odoo/models.py", line 5153, in <genexpr>
records = self.browse().concat(*(self.new(vals) for vals in vals_list_todo))
File "/home/odoo/odoo18/community/odoo/models.py", line 6861, in new
record._update_cache(values, validate=False)
File "/home/odoo/odoo18/community/odoo/models.py", line 6411, in _update_cache
raise ValueError("Invalid field %r on model %r" % (e.args[0], self._name))
ValueError: Invalid field 'duns' on model 'res.partner'
```
In this commit-
We fix the above traceback and the feature works as expected
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#205698Description of the issue this commits addresses: The Customer Statement button is shown too often and leads to empty customer statements in some scenarios. The banner warning the user that some entries are draft is also shown too often and should only appear if the selected partner(s) have draft entries. --- Desired behavior after this commit is merged: The button only shows when the customer statement it will lead to has values to show. This means both making sure the partner has
Original PR description
Description of the issue this commits addresses: The Customer Statement button is shown too often and leads to empty customer statements in some scenarios. The banner warning the user that some entries are draft is also shown too often and should only appear if the selected partner(s) have draft entries. --- Desired behavior after this commit is merged: The button only shows when the customer statement it will lead to has values to show. This means both making sure the partner has moves to show on the customer statement but also that the customer statement actually shows them. Same for the draft entries warning banner. It will only be shown when the selected parter(s) has(have) draft entries. --- task-4680249 Forward-Port-Of: odoo/enterprise#83260 Forward-Port-Of: odoo/enterprise#82531