When printing a check, the pop-up window remains on the screen even after the user has already printed the check and this can confuse the user and print the check multiple times. So, closing the pop-up when a check is printed and downloaded. Task ID: 3860354 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#162067

When printing a check, the pop-up window remains on the screen even after the user has already printed the check and this can confuse the user and print the check multiple times. So, closing the pop-up when a check is printed and downloaded.

Task ID: 3860354

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#162067

Box 49 of the Swedish tax report should be the total of the amounts in boxes 10, 11, 12, 30, 31, 32, 60, 61 and 62 minus the amount in box 48. See [doc](https://skatteverket.se/servicelankar/otherlanguages/inenglishengelska/businessesandemployers/startingandrunningaswedishbusiness/declaringtaxesbusinesses/vat/vatitemsboxbybox.4.3dfca4f410f4fc63c8680004502.html#:~:text=Here%20you%20enter%20the%20VAT%20that%20you%20will%20pay%20or%20have%20refunded%20for%20the%20period%2C%20meaning%20the%20total%2

Box 49 of the Swedish tax report should be the total of the amounts in boxes 10, 11, 12, 30, 31, 32, 60, 61 and 62 minus the amount in box 48. See [doc](https://skatteverket.se/servicelankar/otherlanguages/inenglishengelska/businessesandemployers/startingandrunningaswedishbusiness/declaringtaxesbusinesses/vat/vatitemsboxbybox.4.3dfca4f410f4fc63c8680004502.html#:~:text=Here%20you%20enter%20the%20VAT%20that%20you%20will%20pay%20or%20have%20refunded%20for%20the%20period%2C%20meaning%20the%20total%20of%20the%20amounts%20in%20boxes%2010%2C%2011%2C%2012%2C%2030%2C%2031%2C%2032%2C%2060%2C%2061%20and%2062%C2%A0minus%20the%20amount%20in%20box%2048.%20%C2%A0).

Currently, Box 49 is defined as `Block B + Block I + Block D + Block F`, with:
```
Block B = (box 10 + box 11 + box 12)
Block I = (box 60 + box 61 + box 62)
Block D = (box 30 + box 31 + box 32)
Block F = (box 48)
```

Therefore, Box 49 should be `Block B + Block I + Block D - Block F`.

Enterprise PR: https://github.com/odoo/enterprise/pull/61525

opw-3860025

Forward-Port-Of: odoo/odoo#164780
Forward-Port-Of: odoo/odoo#162006

### [FIX] mail: rm invalid recipient on m2x popup close Before this change incorrect records with invalid/lacking emails were added to tag field (they were not displayed) and user was prompted to fix invalid email. The issue was that discarding the popup didn't remove the invalid records from the tag field. ### [Reproduce] - Install contact (or crm,sale... whatever with a composer) - Create a contact C without an email - Open a full screen composer: 1. Select a contact 2. Click

### [FIX] mail: rm invalid recipient on m2x popup close

Before this change incorrect records with invalid/lacking emails 
were added to tag field (they were not displayed) and user was prompted 
to fix invalid email. The issue was that discarding the popup didn't remove
the invalid records from the tag field.

### [Reproduce]
- Install contact (or crm,sale... whatever with a composer)
- Create a contact C without an email
- Open a full screen composer:
	1. Select a contact
	2. Click "Send message" on the chatter
	3. Click the expand button, to bring up full-screen composer
- In the "Recipients":
	1. Select recipient C, this will open a popup asking to fill in missing email
	2. Close the popup without filling the email
	3. Select another recipient, with an email
	4. BUG: popup asking to fill in email for C is showed

Note: issue exists in every composer view, not specyfic to crm

opw-3829741

## BEFORE

https://github.com/odoo/odoo/assets/33809926/ff04beab-51a1-4405-b535-0c9869556947



## AFTER

https://github.com/odoo/odoo/assets/33809926/6f493ceb-99a8-4b49-9043-02ef929b7d14

Forward-Port-Of: odoo/odoo#162850

This traceback occurs when the user tries to edit the website searchbar To reproduce this issue:- 1) Install `website_sales` 2) open `website` and click on the `search icon` 3) A `website search box` will popup 4) Now open the `editor` and try to change the `inline text` 5) Save the record 6) A traceback appears Error:- ``` ValueError: not enough values to unpack (expected 1, got 0) ``` The issue is occurring because on `web search box` we are getting section_xpath - `/d

This traceback occurs when the user tries to edit the website searchbar

To reproduce this issue:-

1) Install `website_sales`
2) open `website` and click on the `search icon`
3) A `website search box` will popup
4) Now open the `editor` and try to change the `inline text` 
5) Save the record
6) A traceback appears

Error:- 
```
ValueError: not enough values to unpack (expected 1, got 0)
```

The issue is occurring because on `web search box`  we are getting 
section_xpath - `/data/xpath[3]/form/t[1]/div[1]/button[1]/i[1]` and 
we are not getting any value in root from this `section_xpath` 

over here -

https://github.com/odoo/odoo/blob/cdedc1752b845bed9acc0dd4bfeb4b343b675326/addons/web_editor/models/ir_ui_view.py#L121

To fix this issue `o_not_editable` class has been used on that website search bar

sentry-3933794130

Forward-Port-Of: odoo/odoo#164129

Before this commit, users were not allowed to activate the bridge to the documents app to work on Bank and Cash journals. This commit allows Bank and Cash journal documents to be centralized the same way other journals are. There does not seem to be particular reason about excluding Bank and Cash journals from the documents bridge. The potential of showing unwanted bank account numbers in a general repository can always be managed by other means such as access rights. The exclusion was add

Before this commit, users were not allowed to activate the bridge to the documents app to work on Bank and Cash journals.
This commit allows Bank and Cash journal documents to be centralized the same way other journals are.

There does not seem to be particular reason about excluding Bank and Cash journals from the documents bridge.
The potential of showing unwanted bank account numbers in a general repository can always be managed by other means such as access rights.
The exclusion was added in this PR https://github.com/odoo/enterprise/pull/10141 but it seems unnecessary and needs to be removed.

task-3839839

Forward-Port-Of: odoo/enterprise#62088

Community PR: https://github.com/odoo/odoo/pull/162006 opw-3860025 Forward-Port-Of: odoo/enterprise#62124 Forward-Port-Of: odoo/enterprise#61525

Community PR: https://github.com/odoo/odoo/pull/162006

opw-3860025

Forward-Port-Of: odoo/enterprise#62124
Forward-Port-Of: odoo/enterprise#61525

Avatax support confirmed to us that they now require a modeDescription for "Other" payment methods. There are other required attributes we can't easily add, so instead we change the cardTpIntegration type to one that doesn't need these new attributes. opw-3915009 Forward-Port-Of: odoo/enterprise#62161

Avatax support confirmed to us that they now require a modeDescription for "Other" payment methods. There are other required attributes we can't easily add, so instead we change the cardTpIntegration type to one that doesn't need these new attributes.

opw-3915009

Forward-Port-Of: odoo/enterprise#62161