Specification: The time should not be reset when dragging an event in the month view. Observed behavior: Time is reset when dragging an event in month mode. Task-3432065 Forward-Port-Of: odoo/odoo#171402

Specification:
The time should not be reset when dragging an event in the month view.
    
Observed behavior:
Time is reset when dragging an event in month mode.
   
Task-3432065

Forward-Port-Of: odoo/odoo#171402

### Steps to reproduce: - Enable Multi-Step Routes and Batch Transfers in the settings - Inventory > Configuration > Warehouse Management > Operation Types - Click on internal transfer: Enable Auomatic batches group by dest - Create a internal transfer with two moves: 1 x screw and 1 x bolt - Mark the transfer as Todo, duplicate it and `mark as Todo` > the two transfers should be added to a batch - In the barcode app, batch transfers, go on your batch - Add a single screw and validate

### Steps to reproduce:

- Enable Multi-Step Routes and Batch Transfers in the settings
- Inventory > Configuration > Warehouse Management > Operation Types
- Click on internal transfer: Enable Auomatic batches group by dest
- Create a internal transfer with two moves: 1 x screw and 1 x bolt
- Mark the transfer as Todo, duplicate it and `mark as Todo`
> the two transfers should be added to a batch
- In the barcode app, batch transfers, go on your batch
- Add a single screw and validate
> A pop up appears to tell you that the rest will be backordered
- Validate

### Bug:

Instead of being redirected to the barcode app, you are left on the old version of the batch. If you go back the barcode app you will see that your old batch is actually empty (0 lines) and its state is "in progress" instead of being done. If you click on the the empty batch you get a traceback since its picking_type is nowhere to be found by owl

### Cause of the issue:

When you added your screw via the barcode app, you marked the move of the picking as picked. When you validated the batch, you are going to mark this move as done and to back order its picking since only part of it was completed. However, since one of its move is 'done' and the other one is 'assigned', its state will not be done and the picking to backorder will be removed from the original batch y these lines: https://github.com/odoo/odoo/blob/686e0f40f28b81ec99ad41f784a06d0ff231b01c/addons/stock_picking_batch/models/stock_picking.py#L140-L144 It would make sense if the the other pickings were to stay in the batch, which is what the "any" part of the if condition is trying to check. However the other picking of the batch is going to be removed later by these lines (since none of its move are picked so that it is considered to be empty):
https://github.com/odoo/odoo/blob/686e0f40f28b81ec99ad41f784a06d0ff231b01c/addons/stock_picking_batch/models/stock_picking_batch.py#L233-L234 https://github.com/odoo/odoo/blob/686e0f40f28b81ec99ad41f784a06d0ff231b01c/addons/stock_picking_batch/models/stock_picking.py#L120-L121 This is the cause of all the issues since the old batch is now emptied from all of its picking so that its state will stay in progress and its picking_type_id can't be found from its pickings.

### Expected behavior:

The part of the picking that was marked as done should have stayed in the old batch.

### Fix:

The any part of this if condition should take into account the pickings that are going to be detached from the batch.
https://github.com/odoo/odoo/blob/686e0f40f28b81ec99ad41f784a06d0ff231b01c/addons/stock_picking_batch/models/stock_picking.py#L140-L144

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

Forward-Port-Of: odoo/odoo#176121

Denmark government need a way to get ec sales. So now we have a report dedicated to denmark with an export to a CSV format This require us to add the triangular sales tax task-4080107 Backporting: https://github.com/odoo/odoo/pull/157211/commits/a6bd4048a20fada2822692107b57dbcd20d2baf9 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174810

Denmark government need a way to get ec sales. So now we have a report dedicated to denmark with an export to a CSV format This require us to add the triangular sales tax

task-4080107

Backporting: https://github.com/odoo/odoo/pull/157211/commits/a6bd4048a20fada2822692107b57dbcd20d2baf9

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

Forward-Port-Of: odoo/odoo#174810

When a menu link is defined towards an anchor, the scroll effect of the browser does not trigger from within the translated pages where the URL contains the additional path element about the used locale. This scrolling is achieved by the browser itself, it is not related to `scroller_service.js`. The URL is not transformed by `website.menu`'s `clean_url` method. The language is added in `ir.http`'s `url_lang` method, but we cannot always know the current URL at that point, nor during the tem

When a menu link is defined towards an anchor, the scroll effect of the browser does not trigger from within the translated pages where the URL contains the additional path element about the used locale.

This scrolling is achieved by the browser itself, it is not related to `scroller_service.js`.
The URL is not transformed by `website.menu`'s `clean_url` method. The language is added in `ir.http`'s `url_lang` method, but we cannot always know the current URL at that point, nor during the template rendering - making it impossible to determine if the rendered anchor is local.

This commit solves this client-side by replacing link's `href` values with their anchor only whenever they are targeting the current page.

Steps to reproduce:
- Install a second language on the website.
- Put some content in the Home page so that the bottom section requires scrolling to be seen.
- Add a menu element that targets `#bottom`.
- Either be a visitor or a connected user.
- Go to the default language Home page.
- Click on the new link. => Page scrolls to the bottom.
- Switch to the second language Home page.
- Click on the new link.

=> Page reloads targeting the bottom instead of scrolling.

opw-3956066

Forward-Port-Of: odoo/odoo#176077
Forward-Port-Of: odoo/odoo#169944

Before this commit: While generating an ewaybill we get the following traceback: ```log File "/home/odoo/odoo/community/addons/l10n_in_ewaybill_stock/models/l10n_in_ewaybill.py", line 418, in _generate_ewaybill_direct 'ewaybill_expiry_date': self._indian_timezone_to_odoo_utc( File "/home/odoo/odoo/community/addons/l10n_in_ewaybill_stock/models/l10n_in_ewaybill.py", line 433, in _indian_timezone_to_odoo_utc local_time = datetime.strptime(str_date, time_format) TypeError: strpti

Before this commit:
While generating an ewaybill we get the following traceback:
```log
  File "/home/odoo/odoo/community/addons/l10n_in_ewaybill_stock/models/l10n_in_ewaybill.py", line 418, in _generate_ewaybill_direct
    'ewaybill_expiry_date': self._indian_timezone_to_odoo_utc(
  File "/home/odoo/odoo/community/addons/l10n_in_ewaybill_stock/models/l10n_in_ewaybill.py", line 433, in _indian_timezone_to_odoo_utc
    local_time = datetime.strptime(str_date, time_format)
TypeError: strptime() argument 1 must be str, not None
```

After this commit:
We resolve the traceback it was caused due to
string to datetime conversion because we were
receving `None` value instead of datetime string

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

Forward-Port-Of: odoo/odoo#176183

Before this commit, when using a product in a kit with a smaller unit of measure than the base product UoM, and the conversion resulted in a zero quantity, an unclear error message was displayed upon closing the PoS session: "Quantity or Reserved Quantity should be set." This error message lacked sufficient information, making it difficult to diagnose the issue, especially with multiple orders. This commit enhances the error message to clearly indicate the cause of the problem, providing spec

Before this commit, when using a product in a kit with a smaller unit of measure than the base product UoM, and the conversion resulted in a zero quantity, an unclear error message was displayed upon closing the PoS session: "Quantity or Reserved Quantity should be set." This error message lacked sufficient information, making it difficult to diagnose the issue, especially with multiple orders.

This commit enhances the error message to clearly indicate the cause of the problem, providing specific details about the UoM conversion that resulted in a zero quantity.

To reproduce the issue:
1. Create a product with a base UoM in kilograms (kg).
2. Include this product in a kit with a UoM of grams (g).
3. Set the rounding precision for both UoMs to 0.01.
4. Sell one kit through the PoS.

The error would occur due to the quantity conversion from grams to kilograms resulting in zero, given the rounding precision settings.

opw-4084783

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

Forward-Port-Of: odoo/odoo#175007

A field from sale was used in point_of_sale. Introduced here https://github.com/odoo/odoo/pull/173389 opw-4005925-1 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176265

A field from sale was used in point_of_sale. Introduced here https://github.com/odoo/odoo/pull/173389

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

Forward-Port-Of: odoo/odoo#176265

Before this commit, searching for a sale order with a partner name containing special characters (e.g., &) would fail to correctly filter the sale orders. This commit ensures that partner names with special characters are properly handled, allowing for accurate sale order searches. opw-4062365 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#174225

Before this commit, searching for a sale order with a partner name containing special characters (e.g., &) would fail to correctly filter the sale orders. This commit ensures that partner names with special characters are properly handled, allowing for accurate sale order searches.

opw-4062365

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

Forward-Port-Of: odoo/odoo#174225

Description of the issue/feature this PR addresses: - i found that context is never passed in [_duplicateRecords()](https://github.com/odoo/odoo/blob/bd922d14051e5cf09628ad20087d5a78c6588919/addons/web/static/src/model/relational_model/dynamic_list.js#L210) function for list views, when making 'orm' calls from js side, while it is passed in [duplicate](https://github.com/odoo/odoo/blob/bd922d14051e5cf09628ad20087d5a78c6588919/addons/web/static/src/model/relational_model/record.js#L191) functi

Description of the issue/feature this PR addresses:

- i found that context is never passed in [_duplicateRecords()](https://github.com/odoo/odoo/blob/bd922d14051e5cf09628ad20087d5a78c6588919/addons/web/static/src/model/relational_model/dynamic_list.js#L210) function for list views, when making 'orm' calls from js side, while it is passed in [duplicate](https://github.com/odoo/odoo/blob/bd922d14051e5cf09628ad20087d5a78c6588919/addons/web/static/src/model/relational_model/record.js#L191) function of record.js, which is called when duplicating record from form view.

**use case:**
- In `sale_renting` module, There is difference in the result, when a `sale_order` is duplcated from form view(duplicated properly) and when it is duplicated from list view(unexpected result). When duplicating a sale_order, its lines are also being duplicated, and at that time [_compute_is_rental](https://github.com/odoo/enterprise/blob/10006504139abc706ccdb00f71c16846414731eb/sale_renting/models/sale_order_line.py#L56) is being computed, which relies on context key `in_rental_app`. 'in_rental_app' is set in the related action yet was not available when duplicating the sale_order from list view (which resulted in unexpected behaviour).

Current behavior before PR:
- Context is not passed when duplicating Records from list view.

Desired behavior after PR is merged:
- Context is passed when duplicating Records from list view.

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

Forward-Port-Of: odoo/odoo#174137

This commit fixes an issue regarding down-payment calculation. ZATCA defines one rule to govern the way prepaid amounts (down-payment) is calculated, where PrepaidAmount = SUM([LINE.TaxableAmount + LINE.TaxAmount for LINE in invoice.invoice_line_ids]), obviously this poses a problem when we have a mix of down-payment and normal lines on our invoice since the formula does not differentiate between those. To fix this, we make sure that only down-payment lines actually include a Tax Subtotal breakd

This commit fixes an issue regarding down-payment calculation. ZATCA defines one rule to govern the way prepaid amounts (down-payment) is calculated, where PrepaidAmount = SUM([LINE.TaxableAmount + LINE.TaxAmount for LINE in invoice.invoice_line_ids]), obviously this poses a problem when we have a mix of down-payment and normal lines on our invoice since the formula does not differentiate between those. To fix this, we make sure that only down-payment lines actually include a Tax Subtotal breakdown (TaxableAmount & TaxAmount)

Description of the issue/feature this PR addresses:
PrepaidAmount value in invoice XML, representing down-payment amounts, is Wrong, both on the XML and QR code associated, even though ZATCA returns a Valid submission status

Current behavior before PR:
PrepaidAmount value in invoice XML, representing down-payment amounts, is Wrong, both on the XML and QR code associated, even though ZATCA returns a Valid submission status

Desired behavior after PR is merged:
PrepaidAMount is calculated correctly on the XML invoice submitted to ZATCA and also represented correctly on the QR code




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

Forward-Port-Of: odoo/odoo#174960

Set Company country to India Create a TAX as follows - Amount: 15% - Included in price: False - Tax repartition line: - 100.00% of tax to 100560 Tax Receivable - -100.00% of tax to 999999 Undistributed Profits/Losses Open Bank Reconciliation Widget Create a statement Match with Manual operation Select created tax Issue: created tax lines have no amount This occurs because when computing the tax amounts with compute_all if the configuration of tax is price included (enforced

Set Company country to India
Create a TAX as follows
- Amount: 15%
- Included in price: False
- Tax repartition line:
  - 100.00% of tax to 100560 Tax Receivable
  - -100.00% of tax to 999999 Undistributed Profits/Losses
 
Open Bank Reconciliation Widget
Create a statement
Match with Manual operation
Select created tax

Issue: created tax lines have no amount
This occurs because when computing the tax amounts with compute_all
if the configuration of tax is price included (enforced from context)
and the tax is in cache we use the computed amount.
Unfortunately in this particular configuration the amount is 0

opw-3986439

Forward-Port-Of: odoo/odoo#173674

Steps to reproduce: - In website edit mode. - Drop enough blocks into the page to have a vertical scrollbar. - Click on the header. - Select the "Vertical" template in the options of the header. - Select the "Fixed" scroll effect in the options of the header. - click on the logo in the header. - Enter "80px" in the "Height" input in the options of the "Navbar Logo". - Scroll the page to the bottom. - Then, scroll the page to the top. - Bug: the "Navbar Logo" overlaps the navbar links

Steps to reproduce:

- In website edit mode.
- Drop enough blocks into the page to have a vertical scrollbar.
- Click on the header.
- Select the "Vertical" template in the options of the header.
- Select the "Fixed" scroll effect in the options of the header.
- click on the logo in the header.
- Enter "80px" in the "Height" input in the options of the "Navbar Logo".
- Scroll the page to the bottom.
- Then, scroll the page to the top.
- Bug: the "Navbar Logo" overlaps the navbar links.

This bug occurred because the header size was calculated before the transition animation for the header height was completed.

opw-4078173

Forward-Port-Of: odoo/odoo#175653

Before this commit, replying to a message from email author lead to a crash. Steps to reproduce: - Set notification preferences to "Handle in Odoo", in user preferences - Follow a record with chatter - Send a message on the followed record so that it's received by another follower by email - Follower replies to message from email client - Open Inbox in Discuss app and click on "Reply" action on that message => Crash `Cannot read property of undefined (reading 'name')` This happens bec

Before this commit, replying to a message from email author lead to a crash.

Steps to reproduce:
- Set notification preferences to "Handle in Odoo", in user preferences
- Follow a record with chatter
- Send a message on the followed record so that it's received by another follower by email
- Follower replies to message from email client
- Open Inbox in Discuss app and click on "Reply" action on that message => Crash `Cannot read property of undefined (reading 'name')`

This happens because the reply-to text above composer when using the message reply feature assumed that the author is necessarily a partner. This is not necessarily the case: some message just have an email address as author.

This commit fixes the issue by correctly showing the address email when replying to such a message.

opw-4092015

Forward-Port-Of: odoo/odoo#176139

Description of the issue this commit addresses: Wrong invoice label for the tax 25.5 which shows 25%. --- Desired behavior after this commit is merged: The tax has the label 25.5% on invoices. --- no task-feedback --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#175908

Description of the issue this commit addresses:

Wrong invoice label for the tax 25.5 which shows 25%.

---

Desired behavior after this commit is merged:

The tax has the label 25.5% on invoices.

---

no task-feedback

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

Forward-Port-Of: odoo/odoo#175908

Since [1], Werkzeug 3.0.1 is used depending on the python version. Unlike its previous versions, Werkzeug 3.0.1's `url_quote` does not escape the single quote character to `%27` anymore. This causes an issue for cover images that use the computed `image_src` in a `background-image` CSS property using `url(...)` or `url('...')`. This commit restores the former behavior of `_compute_image_src` to avoid issues when its output is used in inadequately quoted CSS properties. Steps to rep

Since [1], Werkzeug 3.0.1 is used depending on the python version.
Unlike its previous versions, Werkzeug 3.0.1's `url_quote` does not
escape the single quote character to `%27` anymore.

This causes an issue for cover images that use the computed `image_src`
in a `background-image` CSS property using `url(...)` or `url('...')`.

This commit restores the former behavior of `_compute_image_src` to
avoid issues when its output is used in inadequately quoted CSS
properties.

Steps to reproduce:
- Use python_version >= '3.12' so that Werkzeug is 3.0.1.
- Create a new blog post.
- Set a cover image.
- Save.

=> Image is not displayed anymore because URL contains `'`.

[1]: https://github.com/odoo/odoo/commit/4a019ae9de64b260fe6b18d21f4624902b3bb880

task-4099056

Forward-Port-Of: odoo/odoo#175815

Since commit odoo/odoo@adb5357e7f93f2cba70acc576a597ea78bd1de42, we have added a new DIV (`o_form_view_container`) around the form view. But the CSS selector for the sticky control panel was not adapted so the feature was not working anymore. This commit fixes the CSS selector. Steps to reproduce: * Open Odoo on small screen * Open the Contact App * Select a contact * Try to scroll down and up into the form view => Bug the control panel is not sticky Note : backport of PR 176015

Since commit odoo/odoo@adb5357e7f93f2cba70acc576a597ea78bd1de42, we have added a new DIV (`o_form_view_container`) around the form view.

But the CSS selector for the sticky control panel was not adapted so the feature was not working anymore.

This commit fixes the CSS selector.

Steps to reproduce:
* Open Odoo on small screen
* Open the Contact App
* Select a contact
* Try to scroll down and up into the form view => Bug the control panel is not sticky

Note : backport of PR 176015

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

Forward-Port-Of: odoo/odoo#176164

[Test](https://runbot.odoo.com/runbot/build/66575239) was failing as website module is not dependency for test_assetsbundle, but we were trying to call website model. As a solution, test was moved from test_assetsbundle to website. The test was always failing, but we didn't catch it before as we were not testing said module. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#175894

[Test](https://runbot.odoo.com/runbot/build/66575239) was failing as website module is not dependency for test_assetsbundle, but we were trying to call website model. As a solution, test was moved from test_assetsbundle to website.

The test was always failing, but we didn't catch it before as we were not testing said module.
 



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

Forward-Port-Of: odoo/odoo#175894

Mistakenly backported. Needed from saas-17.4 up to master Forward-Port-Of: odoo/odoo#175011

Mistakenly backported.

Needed from saas-17.4 up to master

Forward-Port-Of: odoo/odoo#175011

Denmark government need a way to get ec sales. So now we have a report dedicated to denmark with an export to a CSV format task: 4080107 Backporting: https://github.com/odoo/enterprise/pull/58413/commits/d9f7ccdfd062fdc4e372951ff65a5f09046ad7b7 Forward-Port-Of: odoo/enterprise#67517

Denmark government need a way to get ec sales. So now we have a report dedicated to denmark with an export to a CSV format

task: 4080107

Backporting: https://github.com/odoo/enterprise/pull/58413/commits/d9f7ccdfd062fdc4e372951ff65a5f09046ad7b7

Forward-Port-Of: odoo/enterprise#67517

This commit refactors the generation of pretty printed raw xml string to a helper function in `l10n_mx_edi.document` for `l10n_mx_edi` and `l10n_mx_reports`. It modifies the xml declaration to be a custom generated string, which only difference from the normal one is that it uses double quoted string rather than single quoted string in it. This way, the top file of the generated xml string will look like this: ```xml <?xml version="1.0" encoding="UTF-8"?> ``` This ensures as mu

This commit refactors the generation of pretty printed raw xml string
to a helper function in `l10n_mx_edi.document` for `l10n_mx_edi` and
`l10n_mx_reports`.

It modifies the xml declaration to be a custom generated string, which
only difference from the normal one is that it uses double quoted string
rather than single quoted string in it.

This way, the top file of the generated xml string will look like this:

```xml
<?xml version="1.0" encoding="UTF-8"?>
```

This ensures as much support as possible from third party vendors
because some do not consider single quoted string to be valid (even
though it should be).

related opw-4085399
task-id: no task

Forward-Port-Of: odoo/enterprise#67963

1. Add a button in the dashboard to view the number of drafts SODA entries for the CodaBox Soda journal. This button opens the SODA draft entries 2. Add a new non-stored field on the validation wizard to verify that the user has correctly copied the Accounting Firm password. If not, the 'Validate connection' button will be disabled 3. Add a link to the documentation in the connection wizard task-id 4008140 Forward-Port-Of: odoo/enterprise#65440

1. Add a button in the dashboard to view the number of drafts SODA entries for the CodaBox Soda journal. This button opens the SODA draft entries

2. Add a new non-stored field on the validation wizard to verify that the user has correctly
copied the Accounting Firm password.
If not, the 'Validate connection' button will
be disabled

3. Add a link to the documentation in the connection wizard

task-id 4008140

Forward-Port-Of: odoo/enterprise#65440

### Fixes in ATS report: - Remove foreign documents '15' and '110'. SRI DIMM returns a validation error  - In sales, filter by commercial partner and not by partner because there may be different addresses (the ATS validates by ID number). - In sales, change the emission point to entity point (tag "codEstab" and "numEstabRuc"). As it says the Technical Sheet of ATS ![image](https://github.com/

### Fixes in ATS report:

- Remove foreign documents '15' and '110'. SRI DIMM returns a validation error

    ![image](https://github.com/user-attachments/assets/02b9ef2b-73b1-4cb9-bf2f-9b58ae6d0358)

- In sales, filter by commercial partner and not by partner because there may be different addresses (the ATS validates by ID number).
- In sales, change the emission point to entity point (tag "codEstab" and "numEstabRuc"). As it says the Technical Sheet of ATS
![image](https://github.com/user-attachments/assets/33d4196d-1849-4281-be75-9eb7dab45e29)


- In sales, Get all the establishments registered at the SRI (tag "ventasEstablecimiento"). As it says the Technical Sheet of ATS
![image](https://github.com/user-attachments/assets/7a648240-d11e-43fa-901d-7e82ea25da41)

- Fix Unit tests

Forward-Port-Of: odoo/enterprise#67060

### Steps to reproduce * install python 3.12 * install odoo's python required libraries (requirements.txt) * install `l10n_ar_edi` * switch to an Argentinean company * in the Invoicing settings, under the AFIP Web Services section, click 'Test Connections' You should be met with the following error: `AttributeError: module 'lib' has no attribute 'PKCS7_sign'` ### Cause `PKCS7_sign()` was removed in recent version of `pyopenssl`. opw-4085411 opw-4085389 Forward-Port-Of: odoo/ent

### Steps to reproduce
* install python 3.12
* install odoo's python required libraries (requirements.txt)
* install `l10n_ar_edi`
* switch to an Argentinean company
* in the Invoicing settings, under the AFIP Web Services section, click 'Test Connections'

You should be met with the following error: `AttributeError: module 'lib' has no attribute 'PKCS7_sign'`

### Cause
`PKCS7_sign()` was removed in recent version of  `pyopenssl`.

opw-4085411
opw-4085389

Forward-Port-Of: odoo/enterprise#68024

Current behaviour: --- When settings the user's language as hebrew, the user cannot open any documents Steps to reproduce: --- 1. My profile > Language > Hebrew 2. Go to Documents 3. Open any documents 4. Traceback Cause of the issue: --- file_extension would be literally translated Fix: --- Setting t-translation as off opw-3938083 Forward-Port-Of: odoo/enterprise#66688

Current behaviour:
---
When settings the user's language as hebrew, the user cannot open any documents

Steps to reproduce:
---
1. My profile > Language > Hebrew
2. Go to Documents
3. Open any documents
4. Traceback

Cause of the issue:
---
file_extension would be literally translated

Fix:
---
Setting t-translation as off

opw-3938083

Forward-Port-Of: odoo/enterprise#66688

Before this commit: Having a quality control point using "Print label" with an IoT printer will not print anything and download the file. This happened due to the JS function `iotReportActionHandler` ignoring the device sent as it expected it to be a list, see: https://github.com/odoo/enterprise/blob/1412cd3edc6005b05d43d42828e6647ee58594ae/iot/static/src/iot_report_action.js#L21 Therefore, defaulting to the behavior of downloading the file After this commit: Print the label automa

Before this commit:
 Having a quality control point using "Print label" with an IoT printer will not print anything and download the file.
 This happened due to the JS function `iotReportActionHandler` ignoring the device sent as it expected it to be a list, see:
 https://github.com/odoo/enterprise/blob/1412cd3edc6005b05d43d42828e6647ee58594ae/iot/static/src/iot_report_action.js#L21
  Therefore, defaulting to the behavior of downloading the file

After this commit:
 Print the label automatically to the IoT like expected

opw-4032741,4017327,3895056

Forward-Port-Of: odoo/enterprise#68100

Before this commit: An exception was raised if the location was failing to retrieve necessary information. Example: ``` ElementTree.SubElement(ship_from_, 'AddressFieldOne').text = location_.street[:180] TypeError: 'bool' object is not subscriptable ``` After this commit: A more user-friendly error message is shown indicating more clearly the problematic record and missing information opw-3936775 Forward-Port-Of: odoo/enterprise#62967

Before this commit:
An exception was raised if the location was failing to retrieve necessary information. Example:
```
ElementTree.SubElement(ship_from_, 'AddressFieldOne').text = location_.street[:180]
TypeError: 'bool' object is not subscriptable
```

After this commit:
A more user-friendly error message is shown indicating more clearly the problematic record and missing information

opw-3936775

Forward-Port-Of: odoo/enterprise#62967

Before this commit: Some softwares do not follow the specification. Our users cannot import the generated XAF file in other softwares because the docRef length is more than 35 characters. After this commit: We allow our users to create a system parameter to change the docRef length if they need to import the XAF file in another software. opw-3792115 opw-3829459 Forward-Port-Of: odoo/enterprise#68053 Forward-Port-Of: odoo/enterprise#66551

Before this commit:
Some softwares do not follow the specification.
Our users cannot import the generated XAF file in other softwares because the docRef length is more than 35 characters.

After this commit:
We allow our users to create a system parameter to change the docRef length if they need to import the XAF file in another software.

opw-3792115
opw-3829459

Forward-Port-Of: odoo/enterprise#68053
Forward-Port-Of: odoo/enterprise#66551

This traceback arises when the user adds an existing attendee email to a guest email while adding a guest. To reproduce this traceback: 1) Install `website_appointment` 2) Choose any `appointment` from the website 3) Click on `Appointment Type` in the right corner and on the `options page` enable `Allow Guests` 4) Get back to the website and select one user, date & time 5) Now give Email value as email in Guests 6) Confirm Appointment Error:- ``` ValueError: Expected single

This traceback arises when the user adds an existing attendee email to a guest email while adding a guest.

To reproduce this traceback:

1) Install `website_appointment`
2) Choose any `appointment` from the website
3) Click on `Appointment Type` in the right corner
   and on the `options page` enable `Allow Guests`
4) Get back to the website and select one user, date & time 
5) Now give Email value as email in Guests
6) Confirm Appointment

Error:- 
```
ValueError: Expected singleton: calendar.attendee(4762, 4763)
```

When the user adds a guest with the current user email, multiple attendees will be 
created with the same partner ID in a calendar event (see below)

https://github.com/odoo/enterprise/blob/1aff50d91fad45221377591b80ca8b1df2ecb593/appointment/models/appointment_type.py#L944-L955

This leads to the above traceback from here

https://github.com/odoo/enterprise/blob/1aff50d91fad45221377591b80ca8b1df2ecb593/appointment/controllers/calendar.py#L103

This commit will resolve the issue by filtering out the existing attendees 
while creating a new attendee from the guest email.

sentry-5646921453

Forward-Port-Of: odoo/enterprise#67516