Saturday, October 12, 2024
5 changes · saas-17.4
Enhancements to existing features
A test-only attachment model was moved from the enterprise mail test area to the shared mail test module, aligning it with its existing backend definition. This makes attachment-related tests easier to reuse and maintain without affecting end users.
Original PR description
The JavaScript definition of the model mail.test.simple.main.attachment was removed from the test_mail_enterprise module. It was move to the test_mail module because it's python definition already lies there, and because it was needed in the attachment_view test. task-4032316
Resolved issues and error corrections
Attachment preview controls now remain usable after opening an attachment in a separate window and closing it in Chromium-based browsers. This prevents users from getting stuck when browsing attachments and improves reliability in the mail preview experience.
Original PR description
In chromium based browsers, after poping out the attachment and closing the new window, the buttons (next, previous, popout) in the attachment preview are not clickable any more. This was happening because the mail_popout_service was relying on DOM manipulations instead of using owl framework. This commit fixes this problem. task-4032316 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Steps to reproduce: - use ODOO.BALANCE("1",,1) (make sure it returns some value) - switch to another company (company 1 should not be active) => the balance doesn't appear even though the company_id is provided and set to 1 Issue introduced with a707f8345cec8f40407 Task: 4223319 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.
Original PR description
Steps to reproduce:
- use ODOO.BALANCE("1",,1) (make sure it returns some value)
- switch to another company (company 1 should not be active) => the balance doesn't appear even though the company_id is provided
and set to 1
Issue introduced with a707f8345cec8f40407
Task: 4223319
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#182344When sending a document to the government, we have to put a certain document type. The document type are computed depending on what's on the lines of the move, the type of the move, etc The mapping was wrongly done. For the moment when doing an invoice with a service, it will be mapped as a TD03 which was wrong. It should still be TD01. We misinterpreted the professional fees by just checking if there is more service than goods product but now we will add a tag that can be used on account for
Original PR description
When sending a document to the government, we have to put a certain document type. The document type are computed depending on what's on the lines of the move, the type of the move, etc The mapping was wrongly done. For the moment when doing an invoice with a service, it will be mapped as a TD03 which was wrong. It should still be TD01. We misinterpreted the professional fees by just checking if there is more service than goods product but now we will add a tag that can be used on account for that. task:4244462 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183337
Before this commit, when some extension in chrome threw an unhandledrejection event, Chrome apparently redacts it. The error popped into Odoo as very generic one. The error Dialog was spawned, intempestively. After this commit, we use a heuristic to block that kind of errors: Apparently, the error event is a CustomEvent, with no `reason`. opw-4246402 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I
Original PR description
Before this commit, when some extension in chrome threw an unhandledrejection event, Chrome apparently redacts it. The error popped into Odoo as very generic one. The error Dialog was spawned, intempestively. After this commit, we use a heuristic to block that kind of errors: Apparently, the error event is a CustomEvent, with no `reason`. opw-4246402 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#183408 Forward-Port-Of: odoo/odoo#183327