The domain was syntactically wrong. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#204532

The domain was syntactically wrong.

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

Forward-Port-Of: odoo/odoo#204532

Currently, a traceback occurs when the user tries to send multiple invoices to sign in the list view, which includes draft invoices. Error:- ``` TypeError: the JSON object must be str, bytes or bytearray, not bool ``` Cause:- When the user resets an Egyptian invoice to draft status, the value of `l10n_eg_eta_json_doc_id` is set to False as seen in the following line https://github.com/odoo/odoo/blob/26d8a505ab540dfff3ee20e9c83f43b61dc743a8/addons/l10n_eg_edi_eta/models/accoun

Currently, a traceback occurs when the user tries to send multiple invoices 
to sign in the list view, which includes draft invoices.

Error:- 
```
TypeError: the JSON object must be str, bytes or bytearray, not bool
```

Cause:-

When the user resets an Egyptian invoice to draft status, the value 
of `l10n_eg_eta_json_doc_id` is set to False as seen in the following line

https://github.com/odoo/odoo/blob/26d8a505ab540dfff3ee20e9c83f43b61dc743a8/addons/l10n_eg_edi_eta/models/account_move.py#L66-L67

After that when the user attempts to sign the document through the list view, it leads to the  traceback.

This happens because we are passing self instead of the invoices to the method `action_sign_invoices`.
https://github.com/odoo/odoo/blob/26d8a505ab540dfff3ee20e9c83f43b61dc743a8/addons/l10n_eg_edi_eta/models/account_move.py#L73
https://github.com/odoo/odoo/blob/26d8a505ab540dfff3ee20e9c83f43b61dc743a8/addons/l10n_eg_edi_eta/models/account_move.py#L106
As a result, self contains all draft invoices (if selected by the user), leading to the traceback since the value of l10n_eg_eta_json_doc_id is False for the reset draft invoice.

https://github.com/odoo/odoo/blob/26d8a505ab540dfff3ee20e9c83f43b61dc743a8/addons/l10n_eg_edi_eta/models/eta_thumb_drive.py#L34-L35

sentry-6448238266

Forward-Port-Of: odoo/odoo#203064

One issue remained for the 'Multiple choice: multiple answers allowed' option in this task: https://www.odoo.com/odoo/project.task/4663115 Task- 4663115 Forward-Port-Of: odoo/odoo#204603

One issue remained for the 'Multiple choice: multiple answers allowed' option in this task:
https://www.odoo.com/odoo/project.task/4663115

Task- 4663115

Forward-Port-Of: odoo/odoo#204603

Description of the issue/feature this PR addresses: As per ZATCA, `For electronic invoices generated in PDF/A-3 format: while the PDF content will be the representation of the XML invoice in a human readable format, the XML invoice itself will still be added as an attachment as specified in ISO 19005-3 titled "Document management - Electronic document file format for long -term preservation - Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)", and contain the compliant

Description of the issue/feature this PR addresses:

As per ZATCA, 

`For electronic invoices generated in PDF/A-3 format: while the PDF content will be the representation of the XML invoice in a human readable format, the XML invoice itself will still be added as an attachment as specified in ISO 19005-3 titled "Document management - Electronic document file format for long -term preservation - Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)", and contain the compliant XML invoice as an embedded object.`

Current behavior before PR:
- Generated Saudi Localization PDF Invoice had not embedded attached EDI XML documents
- Generated Saudi Localization PDF Invoice was not PDF-A Compliant
- Generated Saudi Localization PDF Invoice file name did not adhere to ZATCA business rules of the following:
`Seller Vat Number (BT-31), Date (BT-2), Time (KSA-25), Invoice Number (BT-1)`

Desired behavior after PR is merged:
- Generated Saudi Localization PDF Invoice has the XML  EDI documents embedded as an attachment
- Generated Saudi Localization PDF Invoice is PDF-A Compliant
- Generated Saudi Localization PDF Invoice is named as per the ZATCA business rules

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

opw-4528551

Forward-Port-Of: odoo/odoo#203228
Forward-Port-Of: odoo/odoo#198158

Steps to reproduce the issue: - Enter Website edit mode. - Click on the "Theme" tab. - Pick a black color for the website background (4th color button). - Click on a link in the website navbar to make the link popover appear. - Bug: The popover background is black, and its buttons are not visible as they are also black. Bug introduced by this commit [1], where popover colors were updated to match the website's theme. The goal was to align popovers, such as the one for the e-commerce ca

Steps to reproduce the issue:

- Enter Website edit mode.
- Click on the "Theme" tab.
- Pick a black color for the website background (4th color button).
- Click on a link in the website navbar to make the link popover appear.
- Bug: The popover background is black, and its buttons are not visible as they are also black.

Bug introduced by this commit [1], where popover colors were updated to match the website's theme. The goal was to align popovers, such as the one for the e-commerce cart button, with the theme colors. However, the change unfortunately also affected the link editing popover, which should remain neutral as it is part of the interface elements.

[1]: https://github.com/odoo/odoo/commit/0d96be06faf8aad1a92183bd2b6371253980c7e6

task-4422810

| Before  | After |
| ------------- | ------------- |
| ![image](https://github.com/user-attachments/assets/a217c886-9521-4347-a0db-7d6cd7b6029b)  | ![image](https://github.com/user-attachments/assets/f06e4618-e896-430c-8063-bbe3dd534055)  |

Forward-Port-Of: odoo/odoo#203958

Purpose ======= The Indian government updated its UOM code https://einvoice1.gst.gov.in/Others/MasterCodes (select UQC Codes) So In this commit, I have updated `l10n_in_code` in UOM Mili Meter and Square Foot. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#204598

Purpose
=======
The Indian government updated its UOM code
https://einvoice1.gst.gov.in/Others/MasterCodes (select UQC Codes)

So In this commit, I have updated `l10n_in_code` in UOM  Mili Meter and Square Foot.

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

Forward-Port-Of: odoo/odoo#204598

Description of the issue this commit addresses: In january 2025, updates were made to some sections of the LU tax report and chart of accounts. Therefore, the version we use is out of date. --- Desired behavior after this commit is merged: The COA and VAT reports use the new values updated in 2025. --- Enterprise PR: https://github.com/odoo/enterprise/pull/81644 task-4587067 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-P

Description of the issue this commit addresses:

In january 2025, updates were made to some sections of the LU tax report and chart of accounts. Therefore, the version we use is out of date.

---

Desired behavior after this commit is merged:

The COA and VAT reports use the new values updated in 2025.

---

Enterprise PR: https://github.com/odoo/enterprise/pull/81644
task-4587067

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

Forward-Port-Of: odoo/odoo#204232
Forward-Port-Of: odoo/odoo#202228

In a form snippet, enabling the "Description" option for a field and then undoing this action caused the field to lose its styling and available customization options. Steps to reproduce: - Enter Edit mode. - Add a Form snippet. - Select any field (e.g., "Your Name"). - Enable the "Description" option from the customization panel. - Undo the action (Ctrl+Z). This results in the field losing its padding and the "Description" and other options being removed. Cause: A redundant line

In a form snippet, enabling the "Description" option for a field and then undoing this action caused the field to lose its styling and available customization options.

Steps to reproduce:
- Enter Edit mode.
- Add a Form snippet.
- Select any field (e.g., "Your Name").
- Enable the "Description" option from the customization panel.
- Undo the action (Ctrl+Z).

This results in the field losing its padding and the "Description" and other options being removed.

Cause:
A redundant line of code was adding an extra step in the mutation history. When undoing, this extra step caused the removal of essential classes from the field, leading to the loss of styling and options.

Fix:
Removed the redundant line to ensure undoing the action correctly restores the previous state without affecting the field’s styling or customization options.

task-4013551

Forward-Port-Of: odoo/odoo#179858

Versions -------- - 16.0+ Steps ----- 1. Have a payment token saved via Flutterwave; 2. use token to pay for an order. Issue ----- Error: Provide a valid redirect url Cause ----- Flutterwave now mandates authorization for tokenized flows. They provide an authorization url for this, and expect to receive a redirect url value to return to afterwards. Solution -------- Solution partially based on the Ogone redirect flow added in 0ed92bcc9791 The authorization url is provid

Versions
--------
- 16.0+

Steps
-----
1. Have a payment token saved via Flutterwave;
2. use token to pay for an order.

Issue
-----
Error: Provide a valid redirect url

Cause
-----
Flutterwave now mandates authorization for tokenized flows. They provide an authorization url for this, and expect to receive a redirect url value to return to afterwards.

Solution
--------
Solution partially based on the Ogone redirect flow added in 0ed92bcc9791

The authorization url is provided in the notification data. Store this in the `provider_reference` field if the transaction is pending.

When processing the pending transaction, initiate a redirect flow, which redirects the user to the authorization url.

opw-4669110

Forward-Port-Of: odoo/odoo#204599
Forward-Port-Of: odoo/odoo#204322

In a previous PR https://github.com/odoo/odoo/pull/203445 we added a dependency on fiscal position in l10n_in on the gst treatment. The problem, is that gst treatment depends on the state and this way it is possible that fiscal position changes when confirming an invoice. In any case, it is also better that the gst treatment of the invoice does not depend on the state as you do not want it to suddenly change when you reset to draft. So, we removed to dependency of the state for the l10

In a previous PR https://github.com/odoo/odoo/pull/203445 we added a dependency on fiscal position in l10n_in on the gst treatment.

The problem, is that gst treatment depends on the state and this way it is possible that fiscal position changes when confirming an invoice.

In any case, it is also better that the gst treatment of the invoice does not depend on the state as you do not want it to suddenly change when you reset to draft.

So, we removed to dependency of the state for the
l10n_in_gst_treatment on invoice.

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

Improve references computation, notably when message history consists mainly in note-like messages (tracking with subtypes, ...). After odoo/odoo#197127 threads are split in email readers are references are missing. Task-4677717 Forward-Port-Of: odoo/odoo#204227 Forward-Port-Of: odoo/odoo#203739

Improve references computation, notably when message history consists
mainly in note-like messages (tracking with subtypes, ...). After odoo/odoo#197127
threads are split in email readers are references are missing.

Task-4677717

Forward-Port-Of: odoo/odoo#204227
Forward-Port-Of: odoo/odoo#203739

Steps to reproduce: - Activate developer mode - Install website Google Maps module - Navigate to Website in edit mode - Drop the google maps snippet - Enter a correct API key - The dialog closes but the snippet is removed This is due to a promise not resolved when confirming the API key. Forward-Port-Of: odoo/odoo#204139

Steps to reproduce:

- Activate developer mode
- Install website Google Maps module
- Navigate to Website in edit mode
- Drop the google maps snippet
- Enter a correct API key
- The dialog closes but the snippet is removed

This is due to a promise not resolved when confirming the API key.

Forward-Port-Of: odoo/odoo#204139

**Problem**: Commit [f523cb8](https://github.com/odoo/odoo/commit/f523cb85174687856d2c93fbc3c2f52a307f6761) did not properly handle background images, leading to issues when retrieving the correct attachment source. **Solution**: Use `el.dataset.bgSrc` to get the correct attachment source for background images. **Steps to reproduce**: 1. Add a "Banner" block. 2. Update the image. 3. Save. - **Issue**: image lost. **opw-4686236** --- I confirm I have signed the CLA and read

**Problem**:
Commit [f523cb8](https://github.com/odoo/odoo/commit/f523cb85174687856d2c93fbc3c2f52a307f6761) did not properly handle background images, leading to issues when retrieving the correct attachment source.

**Solution**:
Use `el.dataset.bgSrc` to get the correct attachment source for background images.

**Steps to reproduce**:
1. Add a "Banner" block.
2. Update the image.
3. Save.
   - **Issue**: image lost.

**opw-4686236**

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

Forward-Port-Of: odoo/odoo#204812
Forward-Port-Of: odoo/odoo#204662

According to the DATEV Format documentation, the VAT needs to be split into two columns instead of one. The first column being the country code (ISO 3166), and the second one being the remaining numbers. task-4600047 runbot : https://runbot.odoo.com/runbot/bundle/16-0-datev-export-roto-352476 Forward-Port-Of: odoo/enterprise#82104 Forward-Port-Of: odoo/enterprise#80843

According to the DATEV Format documentation, the VAT needs to be split into two columns instead of one. The first column being the country code (ISO 3166), and the second one being the remaining numbers.

task-4600047

runbot : https://runbot.odoo.com/runbot/bundle/16-0-datev-export-roto-352476

Forward-Port-Of: odoo/enterprise#82104
Forward-Port-Of: odoo/enterprise#80843

Description of the issue this commit addresses: In january 2025, updates were made to some sections of the LU tax report and chart of accounts. Therefore, the version we use is out of date. --- Desired behavior after this commit is merged: The COA and VAT reports use the new values updated in 2025. --- Community PR: https://github.com/odoo/odoo/pull/202228 task-4587067 Forward-Port-Of: odoo/enterprise#82627 Forward-Port-Of: odoo/enterprise#81644

Description of the issue this commit addresses:

In january 2025, updates were made to some sections of the LU tax report and chart of accounts. Therefore, the version we use is out of date.

---

Desired behavior after this commit is merged:

The COA and VAT reports use the new values updated in 2025.

---

Community PR: https://github.com/odoo/odoo/pull/202228
task-4587067

Forward-Port-Of: odoo/enterprise#82627
Forward-Port-Of: odoo/enterprise#81644

Currently, an error is produced when updating payroll data if a referenced partner record in salary rules has been deleted by the user. **Steps to reproduce:** - Install the `account` and `l10n_hr_payroll` modules. - Navigate to the **Vendors** view and delete the `Register for State Labour Welfare Fund Deduction` record. - In **Scheduled Actions**, manually execute `Payroll: Update data`. - Observer the backend error. **Error:** `ValueError - ParseError('while parsing /home/odoo/src/

Currently, an error is produced when updating payroll data if a referenced partner record in salary rules has been deleted by the user.

**Steps to reproduce:**
- Install the `account` and `l10n_hr_payroll` modules.
- Navigate to the **Vendors** view and delete the `Register for State Labour Welfare Fund Deduction` record.
- In **Scheduled Actions**, manually execute `Payroll: Update data`.
- Observer the backend error.

**Error:**
`ValueError - ParseError('while parsing /home/odoo/src/enterprise/saas-18.2/l10n_in_hr_payroll/data/salary_rules/hr_salary_rule_ind_emp_data...`

The error occurs because the method at [1] attempts to load the `hr_salary_rule_ind_emp_data.xml` file that references a deleted `partner_id` [2], leading to a parsing error.

[1] - https://github.com/odoo/enterprise/blob/46f838403c8d60760a5b37cb5fe8d052d2307999/l10n_in_hr_payroll/models/hr_payslip.py#L44-L54
[2] - https://github.com/odoo/enterprise/blob/46f838403c8d60760a5b37cb5fe8d052d2307999/l10n_in_hr_payroll/data/salary_rules/hr_salary_rule_ind_emp_data.xml#L364

This commit ensures that `res_partner_data.xml` is loaded before `hr_salary_rule_ind_emp_data.xml`, preventing errors due to missing partners.

Sentry - 6429993371

Forward-Port-Of: odoo/enterprise#81917