Search
Navigate
Branch
Sunday, September 29, 2024
11 changes
1 change
Miscellaneous changes
When a snippet is in grid mode, the grid items horizontal padding can be modified with the "Padding (Y, X)" option. When we are in mobile view, the display is back to `flex`, in order for the layout to look like the snippets in normal mode. However, while the normal mode columns all have the same padding, which depends on the `--gutter-x` CSS variable, the grid items still keep the horizontal grid padding, making them misaligned with the other contents. An other inconsistency in grid mode
Original PR description
When a snippet is in grid mode, the grid items horizontal padding can be modified with the "Padding (Y, X)" option. When we are in mobile view, the display is back to `flex`, in order for the layout…
When a snippet is in grid mode, the grid items horizontal padding can be modified with the "Padding (Y, X)" option. When we are in mobile view, the display is back to `flex`, in order for the layout to look like the snippets in normal mode. However, while the normal mode columns all have the same padding, which depends on the `--gutter-x` CSS variable, the grid items still keep the horizontal grid padding, making them misaligned with the other contents. An other inconsistency in grid mode is the `--gutter-x` variable: in order for the container to be well aligned with the header, it was set to 0 (except when the container is full-width, where it is 30px). The issue is that this rule is applied on mobile too, making the container inconsistent with the normal snippets. This commit fixes these issues by blocking the horizontal grid padding in mobile view, and by setting the `--gutter-x` variable rule only for the desktop view. This commit also moves the rule added in commit [1], which is used to compensate the margins of the rows that are direct children of grid items. Indeed, now that the padding is not variable in mobile view, this rule is only needed in desktop view. [1]: https://github.com/odoo/odoo/commit/d7c2f8b4a3535f5c15043226a296d10be4208cec task-4194685 Forward-Port-Of: odoo/odoo#180665 Forward-Port-Of: odoo/odoo#180649
3 changes
Miscellaneous changes
Before this commit, when account_online_payment was installed and no payment initiation was configured on a bank journal, the batch validation and export buttons never appeared on the batch payments made on this journal. Forward-Port-Of: odoo/enterprise#70952
Original PR description
Before this commit, when account_online_payment was installed and no payment initiation was configured on a bank journal, the batch validation and export buttons never appeared on the batch payments made on this journal. Forward-Port-Of: odoo/enterprise#70952
6 changes
Enhancements to existing features
A problematic automated test in the Loans module has been temporarily disabled to avoid false failures in the development process. This helps keep validation pipelines moving while the underlying test issue is investigated and fixed.
1 change
Resolved issues and error corrections
Branch companies can now export OSS (One-Stop Shop) tax reports to XML format. Previously, this export option was restricted and unavailable for branch companies, but it is now enabled to support specific business scenarios where branches need to export their tax reports in XML format.
Original PR description
Description of the issue this commit addresses: Branches companies are not allowed to export to XML the OSS reports while this is a use case that should be allowed for specific scenarios. --- Desired behavior after this commit is merged: The XML export button is usable by any branch company. --- Community PR: https://github.com/odoo/odoo/pull/181954 task: no-task
Steps to reproduce the error: - Install "contacts" and "whatsapp" module - Configure WhatsApp Business Account and create a whatsapp template - Go to Contacts > Create a new contact > add mobile number > click on whatsapp button > select template > send message - reply to message from mobile number - Delete contact - Go to Discuss > open channel of contact > send message Traceback: ``` IndexError: tuple index out of range File "odoo/http.py", line 2256, in __call__ response
Original PR description
Steps to reproduce the error: - Install "contacts" and "whatsapp" module - Configure WhatsApp Business Account and create a whatsapp template - Go to Contacts > Create a new contact > add mobile…
Steps to reproduce the error:
- Install "contacts" and "whatsapp" module
- Configure WhatsApp Business Account and create a whatsapp template
- Go to Contacts > Create a new contact > add mobile number >
click on whatsapp button > select template > send message
- reply to message from mobile number
- Delete contact
- Go to Discuss > open channel of contact > send message
Traceback:
```
IndexError: tuple index out of range
File "odoo/http.py", line 2256, in __call__
response = request._serve_db()
File "odoo/http.py", line 1832, in _serve_db
return self._transactioning(_serve_ir_http, readonly=ro)
File "odoo/http.py", line 1852, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 134, in retrying
result = func()
File "odoo/http.py", line 1830, in _serve_ir_http
return self._serve_ir_http(rule, args)
File "odoo/http.py", line 1837, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2062, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 742, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "home/odoo/src/enterprise/saas-17.2/whatsapp/controller/main.py", line 41, in webhookpost
request.env['whatsapp.message']._process_statuses(value)
File "home/odoo/src/enterprise/saas-17.2/whatsapp/models/whatsapp_message.py", line 413, in _process_statuses
whatsapp_message_id._update_message_fetched_seen()
File "home/odoo/src/enterprise/saas-17.2/whatsapp/models/whatsapp_message.py", line 426, in _update_message_fetched_seen
channel_member = channel.channel_member_ids.filtered(lambda cm: cm.partner_id == channel.whatsapp_partner_id)[0]
File "odoo/models.py", line 6580, in __getitem__
return self.browse((self._ids[key],))
```
https://github.com/odoo/enterprise/blob/a134bea9c6fa1a0806c5501046e358c82d7a3fe5/whatsapp/models/whatsapp_message.py#L428
Here, when user deletes the contact, channel.whatsapp_partner_id will be False,
and channel_member will become an empty tuple,
So when it tries to access the index of an empty tuple,
It will lead to the above traceback.
sentry-5314291061
Forward-Port-Of: odoo/enterprise#62262Forward-Port-Of: odoo/enterprise#71009
Original PR description
Forward-Port-Of: odoo/enterprise#71009
Resolved issues and error corrections
This update fixes minor visual issues in the website loading screen, including animation sizing problems in Firefox and misplaced text when messages are long. It helps make the loading experience look more consistent and polished across browsers.
Original PR description
This PR resolves several minor `website_loader` visual glitches. The first fix addresses Firefox miscalculating fixed image sizes in the "filmstrip" animation. Fixed image sizes were necessary to achieve a seamless looping effect. However, since the animation doesn't last long enough for a full loop and the approach isn't fully cross-browser compatible, fine-tuned classes and sizes were removed. The flex layout now adjusts image sizes based on available space. The second fix resolves a layout misplacement for the `currentWaitingMessage` when rendering long strings in a flex layout. Additionally, this commit scopes the `o_website_loader_container_content` max-width property to only apply when the animation block is visible. task-4214353 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
[Real Decreto-ley 4/2024] of June 26, 2024 introduces some changes to the tax rates to address the economic and social consequences arising from the conflicts in Ukraine and the Middle East. The VAT reductions of 5% (pasta and seed oils) and 0% (basic foodstuffs and olive oils) previously introduced will be increased to 7.5% and 2%, respectively, starting on October 1, 2024. The rates of the equivalence surcharge applicable to these products will increase from 0.6% and 0%, to 1% and 0.26%,
Original PR description
[Real Decreto-ley 4/2024] of June 26, 2024 introduces some changes to the tax rates to address the economic and social consequences arising from the conflicts in Ukraine and the Middle East. The VAT reductions of 5% (pasta and seed oils) and 0% (basic foodstuffs and olive oils) previously introduced will be increased to 7.5% and 2%, respectively, starting on October 1, 2024. The rates of the equivalence surcharge applicable to these products will increase from 0.6% and 0%, to 1% and 0.26%, respectively. An upgrade script is provided that automatically disables the deprecated VAT of 5% and Rec. Eq. of 0.62% when upgrading the `l10n_es` module. [Real Decreto-ley 4/2024]: https://www.boe.es/buscar/act.php?id=BOE-A-2024-12944 [task-4147046](https://www.odoo.com/odoo/all-tasks/4147046) Related to https://github.com/odoo/enterprise/pull/69736 Forward-Port-Of: odoo/odoo#181944 Forward-Port-Of: odoo/odoo#179797
Following the same optimization as in [1], we can bypass the canvas drawing of spreadsheet in the tests (as long as) we don't need it. This revision adds a generic patch that will disable the major part of the grid drawing of a spreadsheet while letting it enabled in debug mode for.. debug reasons. Currently, the time spent in drawGrid is around 12~14% (depending on the screen size) when executing spreadsheet edition related tests (see task). This revision makes it drop to 0.5%. [1]: https
Original PR description
Following the same optimization as in [1], we can bypass the canvas drawing of spreadsheet in the tests (as long as) we don't need it. This revision adds a generic patch that will disable the major part of the grid drawing of a spreadsheet while letting it enabled in debug mode for.. debug reasons. Currently, the time spent in drawGrid is around 12~14% (depending on the screen size) when executing spreadsheet edition related tests (see task). This revision makes it drop to 0.5%. [1]: https://github.com/odoo/o-spreadsheet/commit/d3036999989bb0d611ff8c3a05c7e0c2aa60dd49 task-4214049 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#181826
The Modelo 303 has been updated according to [Orden HAC/819/2024] of July 30, 2024. Changes starting from periods 09 and 3T 2024: --------------------------------------------- * Box 108 was added to allow for manually entering those rectifications for which there is no specific box in the form. * Box 111 was added to differentiate refund requests that arise from the application of tax regulations from those that may correspond to a request for undue income. * 3 boolean fields were added i
Original PR description
The Modelo 303 has been updated according to [Orden HAC/819/2024] of July 30, 2024. Changes starting from periods 09 and 3T 2024: --------------------------------------------- * Box 108 was added to…
The Modelo 303 has been updated according to [Orden HAC/819/2024] of July 30, 2024. Changes starting from periods 09 and 3T 2024: --------------------------------------------- * Box 108 was added to allow for manually entering those rectifications for which there is no specific box in the form. * Box 111 was added to differentiate refund requests that arise from the application of tax regulations from those that may correspond to a request for undue income. * 3 boolean fields were added in case we are submitting a rectification to indicate that: - we want to cancel/modify the direct debit made before; - the rectification is due to a discrepancy with administrative criteria; - the rectification is due to another reason. Changes starting from periods 10 and 4T 2024: --------------------------------------------- * Boxes 153, 154 and 155 were changed to reflect the updated VAT rate of 7.5%. * Boxes 16, 17 and 18 were changed to reflect the updated Rec. Eq. rate of 1%. * Boxes 165 to 170 were added to report the new VAT rate of 2% and the new Rec. Eq. rate of 0.26%. * Box 27 was updated to take into account the new boxes 167 and 170 in its computation. (See also [Real Decreto-ley 4/2024]) The BOE file export was updated accordingly. > [!IMPORTANT] > In order to use this, you need to update both the `l10n_es`, `l10n_es_reports` modules and install the new `l10n_es_reports_2024` module. [Orden HAC/819/2024]: https://www.boe.es/eli/es/o/2024/07/30/hac819 [Real Decreto-ley 4/2024]: https://www.boe.es/buscar/act.php?id=BOE-A-2024-12944 [task-4147046](https://www.odoo.com/odoo/all-tasks/4147046) Related to https://github.com/odoo/odoo/pull/179797 Forward-Port-Of: odoo/enterprise#70975 Forward-Port-Of: odoo/enterprise#69736
Steps to reproduce the error: - Install "contacts" and "whatsapp" module - Configure WhatsApp Business Account and create a whatsapp template - Go to Contacts > Create a new contact > add mobile number > click on whatsapp button > select template > send message - reply to message from mobile number - Delete contact - Go to Discuss > open channel of contact > send message Traceback: ``` IndexError: tuple index out of range File "odoo/http.py", line 2256, in __call__ response
Original PR description
Steps to reproduce the error: - Install "contacts" and "whatsapp" module - Configure WhatsApp Business Account and create a whatsapp template - Go to Contacts > Create a new contact > add mobile…
Steps to reproduce the error:
- Install "contacts" and "whatsapp" module
- Configure WhatsApp Business Account and create a whatsapp template
- Go to Contacts > Create a new contact > add mobile number >
click on whatsapp button > select template > send message
- reply to message from mobile number
- Delete contact
- Go to Discuss > open channel of contact > send message
Traceback:
```
IndexError: tuple index out of range
File "odoo/http.py", line 2256, in __call__
response = request._serve_db()
File "odoo/http.py", line 1832, in _serve_db
return self._transactioning(_serve_ir_http, readonly=ro)
File "odoo/http.py", line 1852, in _transactioning
return service_model.retrying(func, env=self.env)
File "odoo/service/model.py", line 134, in retrying
result = func()
File "odoo/http.py", line 1830, in _serve_ir_http
return self._serve_ir_http(rule, args)
File "odoo/http.py", line 1837, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "odoo/http.py", line 2062, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
result = endpoint(**request.params)
File "odoo/http.py", line 742, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "home/odoo/src/enterprise/saas-17.2/whatsapp/controller/main.py", line 41, in webhookpost
request.env['whatsapp.message']._process_statuses(value)
File "home/odoo/src/enterprise/saas-17.2/whatsapp/models/whatsapp_message.py", line 413, in _process_statuses
whatsapp_message_id._update_message_fetched_seen()
File "home/odoo/src/enterprise/saas-17.2/whatsapp/models/whatsapp_message.py", line 426, in _update_message_fetched_seen
channel_member = channel.channel_member_ids.filtered(lambda cm: cm.partner_id == channel.whatsapp_partner_id)[0]
File "odoo/models.py", line 6580, in __getitem__
return self.browse((self._ids[key],))
```
https://github.com/odoo/enterprise/blob/a134bea9c6fa1a0806c5501046e358c82d7a3fe5/whatsapp/models/whatsapp_message.py#L428
Here, when user deletes the contact, channel.whatsapp_partner_id will be False,
and channel_member will become an empty tuple,
So when it tries to access the index of an empty tuple,
It will lead to the above traceback.
sentry-5314291061
Forward-Port-Of: odoo/enterprise#62262