Original PR description

[Runbot Error 107975](https://runbot.odoo.com/web#id=107975&model=runbot.build.error)

Original PR description

tax_group_id was not set since company_id was didn't have any country and class wasn't extending from common class.

runbot id: 105616

Original PR description

Before this commit, the invalid `many2many_tags_avatar` input has two layers of transparent background-color so the two colors stack one uppon the other one and so we had a inconsitancy color with others invalid field.

This commit adds the `.o_field_many2many_tags_avatar` so the following CSS rules are also apply like on the `.o_field_many2many_tags`. And so the child input has `background-color: transparent` when the input is invalid.
```css
.o_input {
  --o-input-background-color: transparent;
}
```

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

Original PR description

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

Forward-Port-Of: odoo/odoo#188077

Original PR description

Since [1], the _is_indexable_url() method was introduced to determine whether a website should be indexed. However, if a domain name contains uppercase letters, the method incorrectly returns a falsy value. This happens because browsers automatically convert URLs to lowercase, causing a mismatch.

Steps to reproduce the issue:

- Navigate to Website > Configuration > Website.
- Set a domain name with uppercase letters (e.g., http://TEST.localhost:8069).
- Go to settings and modify the robots.txt file.
- Visit http://TEST.localhost:8069/robots.txt and notice that the changes are not reflected.

This commit resolves the issue by handling uppercase letters in domain names correctly.

[1]: https://github.com/odoo/odoo/commit/49c226a243864a935b7f8e13c79247a1d9405afa

opw-4306840

Forward-Port-Of: odoo/odoo#187690

Original PR description

Since October 2024, the Facebook mobile site (m.facebook.com) uses an 'X-Frame-Options' header set to 'deny', preventing iframe embedding across different domains. This header enforces a security policy restricting cross-origin access to the content.
Meta has not provided any communication regarding this change. Until it is resolved, we have no choice but to hide the iframe on mobile to prevent users from seeing a "unavailable content" icon.

Steps to reproduce:

- In website edit mode.
- Drag and drop the "Facebook" snippet into the footer.
- Save the page.
- Open the dev tools and enable the mobile preview.
- Bug: The "Facebook" snippet crashes.

More info about the issue: https://developers.facebook.com/community/threads/550478830783215/

opw-4302563
opw-4309180
opw-4222359
opw-4277045

Forward-Port-Of: odoo/odoo#187815
Forward-Port-Of: odoo/odoo#186813

Original PR description

The previous code lead to cache-miss

Courtesy of Dawn Hwang

Forward-Port-Of: odoo/odoo#187772

Original PR description

Issue:

When printing the PDF of a Purchase Order, if the company has multiple address, those appear on the same line.

Steps to reproduce:

- Create a Mexican Company with 2 address lines
- Create a Purchase Order
- Print the PDF of the Purchase Order

Cause:

The separator between the 2 address lines in the address format is set as a blank space.

Solution:

Replace the blank space separator with a new line.

Ticket:

4221771

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

Forward-Port-Of: odoo/odoo#186926

Original PR description

The method _get_customization_ids is overriden in other modules to add their schema. The issue is that we call explicitely a specific model with _check_document_type_support. As we call it, the overrident part is not taken into account, as they are overriden in model that changed name. 
Ex: account.edi.xml.pint_jp is not account.edi.xml.ubl_21.

It causes issues if you create a company with an existing participant in the country of these other modules and with the default eas.

To reproduce:
Create a company with the module l10n_jp_ubl_pint and account_peppol installed. Put Japan as country and put as Tax number the endpoint of an existing participant When saving, it will traceback, as the key is not in the dict





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

Forward-Port-Of: odoo/odoo#188005

Original PR description

Versions
--------
- 17.0+

Steps
-----
1. Have 50% discount program;
2. have a deliverable $300 product;
3. have a $10 shipping method that's free for orders over $250;
4. in eCommerce, add the $300 product to your cart;
5. go to checkout;
6. remove the automatically applied discount;
7. proceed to payment;
8. select the $10 shipping method;
9. click the "Claim" button for the 50% discount.

Issue
-----
Shipping is still free despite the order being below $250.

Cause
-----
Delivery rate isn't recomputed after applying rewards.

Solution
--------
After applying a reward in eCommerce, update programs & rewards. If the reward isn't a payment program (gift card or eWallet), and the selected carrier has a `free_over` rule, recompute shipping costs.

opw-4319533

Forward-Port-Of: odoo/odoo#187296

Original PR description

When trying to add a DNI number from the user portal, the following error appears: The CUIT number [] does not seem to be valid. Note: the expected format is AR200-5536168-2 or 20055361682

How to reproduce the issue:
- Install the Argentinian localization
- Create a contact with an email, Identification Number on DNI
- Grant them portal access
- In users, change the password of the new contact
- Log in to the user portal with the new contact credentials
- In edit details, enter a DNI number and confirm

The solution is a backport of this commit: https://github.com/odoo/odoo/commit/caf6bbc0ed875f9fff0440331acb10506d87605e#diff-abaa067ec8ef765ce398468a0dd52d47ea3585a90fa61e5276daa1e603b3b232R67

opw-4267173

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#185948

Original PR description

Description of the issue this PR addresses:

Previously, selection using Shift + Arrow keys was not possible across contenteditable=false elements such as banners and clipboards. This commit makes sure now selection be done across these elements using Shift + Arrow keys.

task-3502724

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

Forward-Port-Of: odoo/odoo#182503

Original PR description

Currently, if the `quick_encoding_vals` field becomes visible in a view (e.g., by toggling "Show invisible elements" in Studio), the system crashes. This happens because the field is currently a Binary field that cannot be represented as a string.

### Fix

The `quick_encoding_vals` field is an **unstored computed** field that outputs a dictionary. To resolve the issue, we can safely convert it into a JSON field.

Note: Fix confirmed by WAN on the ticket.

opw-4241572

Forward-Port-Of: odoo/odoo#187050

Original PR description

Steps to reproduce:

- Enter in Website edit mode.
- Click on the "Contact Us" button in the header.
- In the text toolbar, select "Link" as the "Style" option.
- In the text toolbar, clear the URL input (remove "/contactus").
- Click anywhere on the page.
- Save the page.
- A traceback occurs: "Template fallback - An error occurred while rendering the template website.template_header_mobile"

The header's CTA button cannot be removed because it has the class "oe_unremovable". However, when the URL is cleared from the input field (see step 4 above), the "shouldUnlink" function in "link_tools.js" determines that the link around the "Contact Us" text should be removed.

In this commit, we prevent links with the "oe_unremovable" class from being removed in this situation.

opw-4308023

Forward-Port-Of: odoo/odoo#187947

Original PR description

**Problem**:
When items come from a different JavaScript context (e.g., an iframe, a web worker, or a shadow DOM), their prototype chain may not match the `Attr` class in the current global scope. This mismatch leads to issues in detecting node types correctly.

**Solution**:
Use `attr.nodeType === Node.ATTRIBUTE_NODE` to check for attribute nodes. This approach is more resilient and works across different JavaScript contexts.

**Steps to reproduce**:
1. Navigate to the Email Marketing app.
2. Copy text with a hyperlink from any website.
3. Paste the copied text into the email body.
4. Observe that the text is pasted, but the link is empty due to incorrect node type detection.

opw-4345535

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

Forward-Port-Of: odoo/odoo#187988

Original PR description

After discussion with Pagero support, the BIC of the Payee must be set, therefore we add a constraint to enforce it when invoicing to Chorus Pro.

opw-4139689

Forward-Port-Of: odoo/odoo#187535

Original PR description

Bank statement lines created from the form view won't have an `internal_index` value set yet.

Running balance computation should set a value also on manually deleted lines from the form view as the balance is a computed non-stored field.

@Tecnativa TT50906

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

Forward-Port-Of: odoo/odoo#182497

Original PR description

Current behavior before PR:

When a user posted a message in a group chat, the web notification displayed `#False` as the title. This occurred because `record_name` was used as the title but it was empty for channels with `channel_type = 'group'`, as the displayName name is calculated on the UI side when displaying chat in Discuss.
Before / After
<div style="display: flex;">
  <img src="https://github.com/user-attachments/assets/7ad2de52-8cef-41a7-8d63-b19d718725ff" width="48%" style="margin-right: 4%;" />
  <img src="https://github.com/user-attachments/assets/452fac6e-3a79-4e53-a09c-4fad57b44856" width="48%" />
</div>


Desired behavior after PR is merged:

The title of the web notification now correctly displays the group chat name, ensuring recipients see accurate and complete group titles in notifications.


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

Forward-Port-Of: odoo/odoo#186756

Original PR description

*: l10n_account_edi_ubl_cii_tests

Fix rounding issue with the early payment discount. I used the client's setup in the test to replicate the exact problem.

opw-4245127

Forward-Port-Of: odoo/odoo#186811

Original PR description

Problem: When both l10n_au and l10_nz are installed, the company form displays multiple labels for affected fields, vat and company_registry.

Solution: The company form should only display a label
per field to avoid confusions. Each view per localization
will make the affected field on the parent view invisible
and then add in the same affected fields but with a different label.


Steps to Reproduce on Runbot:
1. Install l10_au and l10_nz
2. Observe the forms for all companies
3. See that there's duplicate labels for fields, vat and company_registry

opw-4250742


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

Forward-Port-Of: odoo/odoo#184806

Original PR description

Steps to reproduce:
-------------------
- Make a sale order in the **Sale** app
- Confirm sale order
- Create invoice of Downpayment
- Type 50%
- Confirm invoice
> Observation: Access error: pos_order_line_ids (allowed for groups 'Point of sale / Users')

Why the fix:
------------
Users who do not belong to the point_of_sale.group_pos_user group get the error
when they try to confirm an invoice of downpayment.

User that have admin rights on accounting but are not users of pos should still
be able to invoice downpayments.

Introduced here:
https://github.com/odoo/odoo/commit/370f3bc

opw-[4352799](https://www.odoo.com/web#id=4352799&view_type=form&model=project.task)

Forward-Port-Of: odoo/odoo#188204

Original PR description

1. Show the image of the award in kanban view.
2. Add `Gift Responsible` to reward list view.
3. Update the reward buying message.

task-4296804

Original PR description

Problem
----------
The method "payslip._get_l10n_lt_taxable_amount" is used in salary rules that makes the computation non-transparent.

Objective
----------
Put this method in the python code field of salary rules directly

Solution
----------
Done, with the sick argument removed.

task-4134314

Original PR description

… other country's invoices

Forward-Port-Of: odoo/enterprise#74053
Forward-Port-Of: odoo/enterprise#74020

Original PR description

Manual fw-port of translations since they're not on transifex for saas versions. To do this properly, the following was also done:
- re-export pot files
- fill in translations for new terms added in this version
- remove leftover translation files from localizations they didn't make sense for
- fixed typo in `l10n_be_social_balance_sheet`

Note that within saas-17.4: `l10n_ch_hr_payroll_elm` was merged into `l10n_ch_hr_payroll`. Therefore the translations needed to be manually ported over from the previous version's module into the new merged po file. Because translations for IT and DE don't appear to be completed for 17.0's localzations on transifex, these translations were not ported over as it's a very painful manual job cross checking the po files of the former version.

Forward-Port-Of: odoo/enterprise#74129
Forward-Port-Of: odoo/enterprise#74111

Original PR description

…or the general ledger

In a previous pull request: https://github.com/odoo/enterprise/pull/46498, the columns date was switched to invoice date.

We want to revert back to the state before this commit. So using the accounting_date instead of the invoice_date on the general ledger.

task-4270453

Forward-Port-Of: odoo/enterprise#73862
Forward-Port-Of: odoo/enterprise#72673

Original PR description

Before This Commit:
- The `open_gst_return_period_form_view` method manually set context values for
`active_id` and `active_model` instead of relying on the active context.
- In `action_get_irn_data`, the logic directly accessed the configurations
without using `sudo`, resulting in access errors in certain cases.

After This Commit:
- The `open_gst_return_period_form_view` method now uses the active context
instead of manually setting context values.
- The `action_get_irn_data` method has been updated to use `sudo` when checking
`l10n_edi_production_env`, ensuring proper access rights and preventing
permission issues.

Forward-Port-Of: odoo/enterprise#74146

Original PR description

Since https://github.com/odoo/enterprise/commit/84cc09959d82dbceb4fe673b85464ef3d8630606 the cancellation no longer works with the PAC SW

opw-4349251

Forward-Port-Of: odoo/enterprise#74343

Original PR description

### After this PR
You can add new column to the account partner ledger
Example:
```
def _get_additional_column_aml_query_values(self):
    res = super()._get_additional_column_aml_query_values()
    res +="account_move_line.date as date,"
    return res
    
```

Forward-Port-Of: odoo/enterprise#74322
Forward-Port-Of: odoo/enterprise#74075

Original PR description

when an ir.default record with user_id is created, the result will be used as
the fallback value for undefined company-dependent column value. It will cause
user-dependent fallback which is logically wrong.

This commit forces the fallback value to be fetched with SUPERUSER to make
fallback always not user-dependent and increase the cache hit rate for
_get_model_defaults

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

Original PR description

Change the checkbox label of stacked charts from `stacked linechart` to `stacked line chart` in the chart configuration panel. Same for bar charts.

Also removed padding between `stacked` and `cumulative` checkboxes in the line chart panel.

Task: [4290275](https://www.odoo.com/web#id=4290275&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)

Original PR description

Recent commit c584a61697e4f4d196b4a485411135a96b0f6006 introduced a mechanism to avoid recomputing prices manually defined on sale order lines.  Nevertheless, it didn't consider zero-priced products.  If a product whose price was 0 (after pricelist computation) was set on the line, even if the price was manually changed to another amount, it was still recomputed when quantities or uom where changed.

opw-4329474

Original PR description

Steps to reproduce the issue:
=============================
- Go to chatter
- Write content on 2 lines
- Open composer
- Select first line and change the heading
- Both lines are changed

Origin of the issue:
====================
The content of the textarea sent to the server is `abc<br>efg`. 

In 17.4: We don't sanitize the content so it stays the same and we put that content into the editor. The editor will create the `p` elements to wrap the inline elements at root.

In 18.0: We sanitize the content and it will pass by `lxml.html.fromstring` and it will wrap the content in a `p` element. Now we put `<p> abc<br> efg</p>` in the editor which is valid but it's considered all as the same block. Applying block-level commands like list and heading will change the whole content.

Solution:
=========
Wrap the textarea content inside a div when we open the mail composer.

opw-4350430
opw-4346348

Original PR description

Since this commit [1], from which the scrolling element is no longer '#wrapwrap' but HTML, the test 'snippet_popup_and_animations' fails.

This is because during animations, 'overflow-x: hidden' is added to the scrolling element (HTML). At the time a modal shows, an 'overflow: hidden' style is briefly added to the 'body' element, which causes the page to scroll to the top when a modal shows while an animation is playing on the page.

To fix this unwanted behavior, we moved the 'overflow-x: hidden' rule added during animations from the HTML to the body."

[1]: https://github.com/odoo/odoo/commit/189a7c96e6e26825dc05c0c6466576fe63aa091e

task-4185877

Original PR description

Records in csv files also need an id column
to create a data entry, and to be able to load
the file in a mode other than init.

The file can be loaded on module installation
and all the records would be created without an
xmlid, but once the module is reloaded or upgraded
the file fails to load. It is a non blocking
error for the module but if someone is missing
the records then they will not be created.

This issue is also blocking the CI on upgrades.

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

Original PR description

See #181383, some methods were removed as unused anymore, but existing websites did rely on those apparently.


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

Original PR description

Before This Commit:
- The `open_gst_return_period_form_view` method manually set context values for
`active_id` and `active_model` instead of relying on the active context.
- In `action_get_irn_data`, the logic directly accessed the configurations
without using `sudo`, resulting in access errors in certain cases.

After This Commit:
- The `open_gst_return_period_form_view` method now uses the active context
instead of manually setting context values.
- The `action_get_irn_data` method has been updated to use `sudo` when checking
`l10n_edi_production_env`, ensuring proper access rights and preventing
permission issues.

Original PR description

**Steps:**
- Install the hr_appraisal module
- Open the employee appraisal form view

----

**Description of the issue/feature this PR addresses:**
In the appraisal form view, when feedback is unpublished, the feedback section overlaps with the chatter area.

----

**Cause:**
This issue arises due to unhandled overflow in cases where feedback is unpublished.

----

**Fix:**
This PR resolves the overlap by applying CSS overflow hidden, which hides the overflowing content and prevents overlap with the chatter section.

task-4320069

Original PR description

Backport of https://github.com/odoo/enterprise/pull/70278 

task-4345648

Original PR description

Purpose
=======
Fix the view scrollbar which isn't restored when the file preview is closed.

Specifications
==============
When a file is previewed, the view scrollbar is hidden so that
scrolling actions don't impact the view behind the file preview.
However when the preview is closed, the scrollbar isn't restored.
=> Calling the documentList onDeleteCallback method to correctly restore
the view and the scrollbar when closing the preview.

Task-4296803

Original PR description

Description of the issue/feature this PR addresses:
ADD cla for dianedelallee to be able to contribute

Current behavior before PR:
cla not signed for dianedelallee

Desired behavior after PR is merged:
cla signed for dianedelallee

thanks

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

Original PR description

Steps to reproduce:
-------------------
- Make a sale order in the **Sale** app
- Confirm sale order
- Create invoice of Downpayment
- Type 50%
- Confirm invoice
> Observation: Access error: pos_order_line_ids (allowed for groups 'Point of sale / Users')

Why the fix:
------------
Users who do not belong to the point_of_sale.group_pos_user group get the error
when they try to confirm an invoice of downpayment.

User that have admin rights on accounting but are not users of pos should still
be able to invoice downpayments.

Introduced here:
https://github.com/odoo/odoo/commit/370f3bc

opw-[4352799](https://www.odoo.com/web#id=4352799&view_type=form&model=project.task)

Forward-Port-Of: odoo/odoo#188204

Original PR description

Problem: When both l10n_au and l10_nz are installed, the company form displays multiple labels for affected fields, vat and company_registry.

Solution: The company form should only display a label
per field to avoid confusions. Each view per localization
will make the affected field on the parent view invisible
and then add in the same affected fields but with a different label.


Steps to Reproduce on Runbot:
1. Install l10_au and l10_nz
2. Observe the forms for all companies
3. See that there's duplicate labels for fields, vat and company_registry

opw-4250742


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

Forward-Port-Of: odoo/odoo#184806

Original PR description

*: l10n_account_edi_ubl_cii_tests

Fix rounding issue with the early payment discount. I used the client's setup in the test to replicate the exact problem.

opw-4245127

Forward-Port-Of: odoo/odoo#186811

Original PR description

Forward-Port-Of: odoo/odoo#187795
Forward-Port-Of: odoo/odoo#185343

Original PR description

Steps to reproduce:

- Enter in Website edit mode.
- Click on the "Contact Us" button in the header.
- In the text toolbar, select "Link" as the "Style" option.
- In the text toolbar, clear the URL input (remove "/contactus").
- Click anywhere on the page.
- Save the page.
- A traceback occurs: "Template fallback - An error occurred while rendering the template website.template_header_mobile"

The header's CTA button cannot be removed because it has the class "oe_unremovable". However, when the URL is cleared from the input field (see step 4 above), the "shouldUnlink" function in "link_tools.js" determines that the link around the "Contact Us" text should be removed.

In this commit, we prevent links with the "oe_unremovable" class from being removed in this situation.

opw-4308023

Forward-Port-Of: odoo/odoo#187947

Original PR description

**Problem**:
When items come from a different JavaScript context (e.g., an iframe, a web worker, or a shadow DOM), their prototype chain may not match the `Attr` class in the current global scope. This mismatch leads to issues in detecting node types correctly.

**Solution**:
Use `attr.nodeType === Node.ATTRIBUTE_NODE` to check for attribute nodes. This approach is more resilient and works across different JavaScript contexts.

**Steps to reproduce**:
1. Navigate to the Email Marketing app.
2. Copy text with a hyperlink from any website.
3. Paste the copied text into the email body.
4. Observe that the text is pasted, but the link is empty due to incorrect node type detection.

opw-4345535

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

Forward-Port-Of: odoo/odoo#187988

Original PR description

Currently, if the `quick_encoding_vals` field becomes visible in a view (e.g., by toggling "Show invisible elements" in Studio), the system crashes. This happens because the field is currently a Binary field that cannot be represented as a string.

### Fix

The `quick_encoding_vals` field is an **unstored computed** field that outputs a dictionary. To resolve the issue, we can safely convert it into a JSON field.

Note: Fix confirmed by WAN on the ticket.

opw-4241572

Forward-Port-Of: odoo/odoo#187050

Original PR description

Commit ab5b806ced3a72f04af9b92f1ec8c32e9a03f4d7 introduced a regression by moving the computation logic for the DIN 5008 layout from Python into the XML template report_purchaseorder_document. However, the same logic was not applied to report_purchasequotation_document, which is used for RFQs, causing discrepancies in the RFQ layout.

task-4089521

Forward-Port-Of: odoo/odoo#183953

Original PR description

The method _get_customization_ids is overriden in other modules to add their schema. The issue is that we call explicitely a specific model with _check_document_type_support. As we call it, the overrident part is not taken into account, as they are overriden in model that changed name. 
Ex: account.edi.xml.pint_jp is not account.edi.xml.ubl_21.

It causes issues if you create a company with an existing participant in the country of these other modules and with the default eas.

To reproduce:
Create a company with the module l10n_jp_ubl_pint and account_peppol installed. Put Japan as country and put as Tax number the endpoint of an existing participant When saving, it will traceback, as the key is not in the dict





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

Forward-Port-Of: odoo/odoo#188005

Original PR description

Issue:

When printing the PDF of a Purchase Order, if the company has multiple address, those appear on the same line.

Steps to reproduce:

- Create a Mexican Company with 2 address lines
- Create a Purchase Order
- Print the PDF of the Purchase Order

Cause:

The separator between the 2 address lines in the address format is set as a blank space.

Solution:

Replace the blank space separator with a new line.

Ticket:

4221771

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

Forward-Port-Of: odoo/odoo#186926

Original PR description

This commit fixes the direction of the arrows in the stock rules diagram if the user languange is right-to-left.

opw-4302429

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

Forward-Port-Of: odoo/odoo#187967
Forward-Port-Of: odoo/odoo#187921

Original PR description

Before this commit, adding products to the cart would become slow when there were several loyalty.card records and several pos.order.line records.

opw-4317125

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

Forward-Port-Of: odoo/odoo#186797

Original PR description

Since [1], the _is_indexable_url() method was introduced to determine whether a website should be indexed. However, if a domain name contains uppercase letters, the method incorrectly returns a falsy value. This happens because browsers automatically convert URLs to lowercase, causing a mismatch.

Steps to reproduce the issue:

- Navigate to Website > Configuration > Website.
- Set a domain name with uppercase letters (e.g., http://TEST.localhost:8069).
- Go to settings and modify the robots.txt file.
- Visit http://TEST.localhost:8069/robots.txt and notice that the changes are not reflected.

This commit resolves the issue by handling uppercase letters in domain names correctly.

[1]: https://github.com/odoo/odoo/commit/49c226a243864a935b7f8e13c79247a1d9405afa

opw-4306840

Forward-Port-Of: odoo/odoo#187690

Original PR description

Before this PR, one-letter domain (like https://x.com) would not be linkified. This PR allows one-letter domain.

Task-4344826

Forward-Port-Of: odoo/odoo#188037
Forward-Port-Of: odoo/odoo#187899

Original PR description

When new modules with coas are being installed, the matching coa based on country is autoinstalled if possible, but if multiple charts match then we overwrite the autoinstall and use the one from the last module.
Here we make sure we do not overwrite the chart if it is not associated with the company's country.

Using a chart not associated with any country (except generic_coa) during module installation will result in failure.
Problem is reproduced on:
1- CI when any syscohada module is installed
2- start a new db and do not set a country on your company, then try installing any syscohada module




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

Forward-Port-Of: odoo/odoo#187958
Forward-Port-Of: odoo/odoo#187271

Original PR description

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

Forward-Port-Of: odoo/odoo#188077

Original PR description

In #173866, the IoT configuration files were merged into one file. However, a logic check in `wireless_ap.sh` was inverted in the process, causing it not to wait for an IP. This PR simply restores the `!` to fix the check.

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

Forward-Port-Of: odoo/odoo#187862

Original PR description

The dependency `l10n_syscohada` doesn't get installed automatically when account is installed, therefore these l10n don't get installed either.

Each localization that had `countries` set in the manifest should have an `auto_install` containing the main app it is for.

Forward-Port-Of: odoo/odoo#187916

Original PR description

opw-4325300

Forward-Port-Of: odoo/odoo#187706
Forward-Port-Of: odoo/odoo#187285

Original PR description

Steps to reproduce:
- Modify the invoice mail template by adding a default attachment
- Create and confirm an invoice
- Send and Print: delete the attachment from the wizard

Issue:
Back to the mail template, you will see that the attachment has been deleted

Cause:
The attachment is not protected from deletion and is added to list of attahcments to be deleted https://github.com/odoo/odoo/blob/ef424a9dc22a5abbe7b0a6eff61cf113826f04c0/addons/account/static/src/components/mail_attachments/mail_attachments.js#L59-L63 and is deleted
https://github.com/odoo/odoo/blob/ef424a9dc22a5abbe7b0a6eff61cf113826f04c0/addons/account/static/src/components/mail_attachments/mail_attachments.js#L81-L82

Solution:
Make sure that attachements from template are protected

opw-4295826

Forward-Port-Of: odoo/odoo#187240

Original PR description

Forward-Port-Of: odoo/enterprise#74128
Forward-Port-Of: odoo/enterprise#72823

Original PR description

All the Colorado and Washington taxes rules should be above the Post Tax Deductions and should all be of the category Taxes.

Task: 4329645

Forward-Port-Of: odoo/enterprise#73762

Original PR description

… other country's invoices

Forward-Port-Of: odoo/enterprise#74020

Original PR description

### After this PR
You can add new column to the account partner ledger
Example:
```
def _get_additional_column_aml_query_values(self):
    res = super()._get_additional_column_aml_query_values()
    res +="account_move_line.date as date,"
    return res
    
```

Forward-Port-Of: odoo/enterprise#74201
Forward-Port-Of: odoo/enterprise#74075

Original PR description

Since odoo/enterprise@4f162e7e1ea, the `voip.mode` ICP has been replaced by `voip.provider`'s mode.

This commit update the neutralization script accordingly.

Forward-Port-Of: odoo/enterprise#74035

Original PR description

During the es_XX.po cleaning, the po file for l10n_co_reports was incorrectly not converted to es_419.po and only deleted. We now restore it + correctly rename it to es_419.po

As part of this cleaning, the pot file has been re-exported and the po re-synced with it. Missing translations were also added it. A sentence that was obviously incorrect in the original Spanish was also translated to a correct sentence.

opw-4336377

PR that deleted the original es_CO.po file: https://github.com/odoo/enterprise/pull/66317

Forward-Port-Of: odoo/enterprise#74248

Original PR description

An error will raise when users try to open a locked SO where taxes are
automatically computed

Set up Avatax on the current company
In Settings > Sales > Quotations& Orders active 'Lock Confirmed Sales'
Create a SO with fiscal position 'Automatic Tax Mapping (AvaTax)'
Add a partner and product having avatax category defined
Compute taxes
Confirm order, it will be automatically locked
- With only sale_external_tax installed: Click "Preview"
- With sale_subscription_external_tax installed: Click "Confirm"

Issue: Action will be blocked by User Error
```
It is forbidden to modify the following fields in a locked order
```

This occurs because the system attempt to recompute external taxes after confirming
the sale order, which has been locked, so the action will be blocked

opw-4261396

Forward-Port-Of: odoo/enterprise#74169

Original PR description

When extracting data from a ticket expressed in a currency that's inactive in the company, the code crashed with a KeyError, because the 'currency_id' was not in the vals dictionary.

This crashed some tests in hr_expense_extract when they were run in a db with only USD as active company.

Forward-Port-Of: odoo/enterprise#74207
Forward-Port-Of: odoo/enterprise#72941

Original PR description

Manual fw-port of translations since they're not on transifex for saas versions. To do this properly, the following was also done:
- re-export pot files
- fill in translations for new terms added in this version
- remove leftover translation files from localizations they didn't make sense for
- fixed typo in `l10n_be_social_balance_sheet`

Note that within saas-17.4: `l10n_ch_hr_payroll_elm` was merged into `l10n_ch_hr_payroll`. Therefore the translations needed to be manually ported over from the previous version's module into the new merged po file. Because translations for IT and DE don't appear to be completed for 17.0's localzations on transifex, these translations were not ported over as it's a very painful manual job cross checking the po files of the former version.

Forward-Port-Of: odoo/enterprise#74111

Original PR description

Let's say you have:
- One statement line of 3000 USD / 1000 MXN (rate 1:3)
- Three invoices of 1000 USD / 500MXN (rate 1:2)

=> If you reconcile in the bank widget, the statement entry amounts will be divided by 3 ending with 3 lines of 1000 USD and 333.33 MXN leaving a 0.01 unmatched. This can be an issue for the validation of payment EDI for localizations like Mexican one.

This PR gives more flexibility to user when dealing when bank reconciliation in multiple currencies by allowing to edit amounts on generated exchange moves to allocate this small difference.

opw-4128899

Forward-Port-Of: odoo/enterprise#72810
Forward-Port-Of: odoo/enterprise#72212

Original PR description

Introduced in https://github.com/odoo/enterprise/pull/73469

I made a mistake when checking module dependencies, `work_entry_source` attendance is not available in `hr_payroll`, the attendance module is separate. This move is needed to fix errors in runbot.

opw-4266880

Forward-Port-Of: odoo/enterprise#74251

Original PR description

Task id 4244702

Forward-Port-Of: odoo/enterprise#74287

Original PR description

Before this commit, attempting to print a bill early would result in an error because the account_move did not exist.

opw-4336405

Forward-Port-Of: odoo/enterprise#73913

Original PR description

Add some hooks and tweaks to improve the experience to customize/improve on top of this module.

Info: @wt-io-it

Forward-Port-Of: odoo/enterprise#72123

Original PR description

Following 81dce8461c7, when only some of the invoice lines have subscription start/end date, the commission generation crash when computing the maximum end date or minimal start start:

```
TypeError: '>' not supported between instances of 'bool' and 'datetime.date'
```

This commit ensure we only try to max/min non-falsy values.

Forward-Port-Of: odoo/enterprise#74112

Original PR description

This commit drastically reduces the spreadsheet thumbnails size.

Go to CRM lead and insert the pivot in a spreadsheet:

The size of the thumbnail:

| Description           | Size   |
|-----------------------|--------|
| Before               | 107Kb  |
| After quality=0.5    | 7.8Kb  |
| After quality=0      | 2.9Kb  |


Image quality is indeed reduced, but the thumbnails are always displayed so small that it doesn't really make any difference to the naked eye.

Note: I'm not backporting this fix to 16.0 because the code changed and webp was not supported at the time (even though we could use jpeg)

Task: 4337496

Forward-Port-Of: odoo/enterprise#73881

Original PR description

…or the general ledger

In a previous pull request: https://github.com/odoo/enterprise/pull/46498, the columns date was switched to invoice date.

We want to revert back to the state before this commit. So using the accounting_date instead of the invoice_date on the general ledger.

task-4270453

Forward-Port-Of: odoo/enterprise#73719
Forward-Port-Of: odoo/enterprise#72673

Original PR description

**Steps to reproduce the bug:**
- Create a tracked product by SN: “P1.”
- Create a storable product: "P2."
- Create a receipt for one unit of P1 and P2.
- Mark it as "To Do."
- Set the done quantity of P1 to 0.
- Attempt to perform the quality check.

**Problem:**
You must perform a quality check for P1 even though it has yet to be received.

Since the move_line is set to 0 rather than deleted in the original
picking, it will be linked to the backorder when it is created.
Therefore, to avoid unexpected behavior we can ignore linking its
quality check to the backorder.

https://github.com/odoo/odoo/blob/00057f8efd3c728e13a981290a725878e058d2c6/addons/stock/models/stock_picking.py#L832


opw-4187521

Forward-Port-Of: odoo/enterprise#73823
Forward-Port-Of: odoo/enterprise#73407