Currently, an error occurs when a user uploads an empty text file while attaching a bill in a purchase order.

**Steps to reproduce**:
- Install the `purchase` module.
- In the purchase order(form), click **Upload Bill** button.
- Upload an empty text file. (e.g; [sample here](https://drive.google.com/file/d/1z35T2NY03YVJJPaEL-WjlV8pjvqVCyBW/view?usp=sharing))
- Observe the error.

**Errors:**
- If the **'python-magic'** library is installed: 
 `TypeError - 'bool' object is not subscriptable`
- If not installed: 
  `AttributeError: 'bool' object has no attribute 'startswith'`


The issue occurs when the uploaded attachment is empty, `attachment.raw = False` at [1]. This is then passed to `guess_mimetype`, which expects binary data, resulting in an error.

[1] - https://github.com/odoo/odoo/blob/3e24ff8d3c36b4b924077933ef78a8289a435ee3/addons/account/models/ir_attachment.py#L120

This commit ensures `guess_mimetype` always receives binary input when the file is empty.

Sentry - 6654301906, 6749801114

**Current behavior before PR:**

**Issue 1:**

- Have a long text content in editable, making the container scrollable.
- Select first line of the text, in toolbar open color selector.
- Scroll down until the toolbar overflows and becomes hidden.
- Notice that the toolbar disappears when it overflows its container while color picker remains open, floating at the top of container.

**Issue 2:**

- Select a text having gradient text color.
- Open text color selector, switch to custom color picker.
- Notice that hex and rgba fields are empty and user is not able to apply color through it.

In colorpicker.js, the convertCSSColorToRgba method fails when attempting to convert a gradient color to RGBA. As a result,
colorComponents does not receive valid values and colorpicker doesn't work as expected.

**Issue 3:**

After merging commit [1], text color can be applied without removing or affecting the existing gradient color. In result, if gradient is fully selected then applying text color creates a new font tag inside gradient instead of replacing the gradient.

**Desired behavior after PR:**

**Issue 1:**

Now, when the toolbar overflows and gets hidden, the color selector becomes hidden along with toolbar.

**Issue 2:**

Now, if `convertCSSColorToRgba` fails to convert selected color to rgba color then default color `#FF0000`is assigned to color
components. This ensures that the colorpicker functions correctly.

**Issue 3:**

Now, if gradient is fully selected then,
- Applying text color removes existing text gradient.
- Applying background color removes existing background gradient.
- Applying text color doen't remove the existing background gradient.
- Applying background color doesn't remove the existing text gradient.

[1]: https://github.com/odoo/odoo/commit/938995744b15f345958a2d78a6c844dd5bf1ae6c

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

task-4581884

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

Forward-Port-Of: odoo/odoo#219508
Forward-Port-Of: odoo/odoo#202889

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/68ef49703 [REL] 18.3.16 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)
https://github.com/odoo/o-spreadsheet/commit/9a22c13bd [FIX] Pivot: sanitize measure id [Task: 4876828](https://www.odoo.com/odoo/2328/tasks/4876828)
https://github.com/odoo/o-spreadsheet/commit/b518d5b2a [FIX] Functions: OFFSET dependencies are not correctly added [Task: 5001405](https://www.odoo.com/odoo/2328/tasks/5001405)
https://github.com/odoo/o-spreadsheet/commit/fcf912e5b [FIX] ClickableCells: cache empty positions as well [Task: 5007745](https://www.odoo.com/odoo/2328/tasks/5007745)

Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com>
Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com>
Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com>
Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com>
Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com>
Co-authored-by: Ronak Mukeshbhai Bharadiya <rmbh@odoo.com>
Co-authored-by: Florian Damhaut (flda) <flda@odoo.com>
Co-authored-by: Rémi Rahir (rar) <rar@odoo.com>
Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com>
Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>

### Steps to reproduce:
	- Set Marc Demo's contract work entry source to attendances and working schedule to flexible hours.
	- Create a public holiday with generic time off work entry type.
	- Create one or multiple attendances for marc demo on the public holiday.
	- Regenerate work entries for marc demo for that day, the gaps in between the attendances created and the working hours will be filled with work entries with the right start/end time but duration will always be 8h.

### Cause:
This is happening because when getting the duration batch for the work entry we get the attendance intervals the employee should work in that period and if the employee is flexible we will get a fake attendance with the number of hours required per day ignoring if the period is just a small period of the day

### Fix:
We are checking now since the start date not monday so we don't set a fixed week start. We check if the period is less than the remaining hours we get it as it mostly means that it is less than one day

opw-4887933

Forward-Port-Of: odoo/odoo#218823

Currently, using special characters like backslashes `(\)` in the website name would cause a regex substitution error during website configuration.

**Steps to Reproduce:**
- Install the `website` module.
- Go to Settings and change the website name (e.g; "`test\`").
- Navigate to the URL: "http://localhost:8069/website/configurator"
- Select a theme and a color palette for the website, then apply the changes.

Error: `error - bad escape (end of pattern) at position 19`

**Cause:**
At [1], a backslash in the `website.name` string leads to a malformed replacement string in `re.sub()`, causing a regex syntax error due to an invalid escape sequence.

[1]: https://github.com/odoo/odoo/blob/b8edcd131b3288d037bee9ee03726153932d82f1/addons/website/models/website.py#L678

**Fix:**
This PR escapes the `website.name` using `re.escape()` before using it in regex substitution, prevents runtime errors during website configuration.

sentry-6651288996,6557563272

Forward-Port-Of: odoo/odoo#213083

**Steps to Reproduce :**

1. Install MRP.
2. Create a Bill of Materials (BOM) and add a component with lot tracking.
3. Create and confirm a Manufacturing Order (MO) with BOM.
4. Navigate to the shop floor and click on Generate Serials/Lots.
5. The error appears when trying to generate the lot .

**Issue :**

Error raised when try to Generate Serials/Lots during the manufacturing
process.

`TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'`

**Cause:**

This error occurs because the quantity field is undefined when
Generate Serials/Lots is triggered, the quantity field is not being passed in
the context, and its value is undefined, which is leading to a division by [none](https://github.com/odoo/odoo/blob/18.0/addons/stock/models/stock_move.py#L993).

**Solution:**

To fix this, we added the stock move’s demand quantity as a fallback.This ensures the 
quantity field value is present and its value correctly passed during lot generation.

opw-4763600

Enterprise: https://github.com/odoo/enterprise/pull/88739

Forward-Port-Of: odoo/odoo#220303
Forward-Port-Of: odoo/odoo#209860

### Problem:
When paying a PoS order using customer account, an account move line debiting Account Receivable will be created. Settling this amount inside the PoS (by depositing money) will create another account move line crediting Account Receivable (represents the payment). The second move line is considered, by Odoo, as an outstanding amount, and this amount can be used to pay another invoice (sale order invoice). The moves affecting Account Receivable are still correct. However, unreconciling the two lines created from PoS will cause a confusion for clients who may use this amount to pay other invoices.

### How to reproduce:
    * Open a PoS session.
    * Create an order and pay using customer account.
    * Settle this customer's account (inside PoS).
    * Create a Sale Order and invoice it (or just an invoice).
    * The amount settled can be used as outstanding amount and can be used to pay the created invoice.
enterprise PR: https://github.com/odoo/enterprise/pull/86114

opw-4794793

Forward-Port-Of: odoo/odoo#210619

The combination of the following recent changes prevented the OCR from filling the name of the expense:
- New expenses are named "Untitled Expense {date}" by default instead of the name of the attachment (see commit odoo/odoo@ca1f644).
- The OCR doesn't override the name if it's not set to the default value (see commit 5c813dc).

The first commit didn't update the default expense name that was used in the OCR code, it was still computed from the attachment name.

After the second commit, the OCR couldn't fill in the name of the expense anymore, since it was expecting the name to be the attachment name, but it was "Untitled Expense {date}" instead.

This is fixed by checking that the expense name contains "Untitled Expense" (and taking translation into consideration).

This commit also improves the tests in multiple ways:
- For the `test_auto_send_for_digitization` test, it now mimicks an upload of the document to force the creation of the expense with the default name, this should prevent this from happening again.
- It now uses an actual PDF document instead of "fake" attachments.
- Minor clean up.

task-[4684825](https://www.odoo.com/odoo/project/967/tasks/4684825)

Steps to reproduce:
- Create an Account Group
- Create a new Account Report as follows:
  * Name: any
  * Lines:
    1. [test line]
      * Group By: partner_id,account_id
      * Expressions:
        1. [test expression]
          * Computation Engine: Odoo Domain
          * Formula: [('account_id.account_type', '=', 'asset_receivable')]
          * Subformula: sum
- Actions > Create Menu Item
- Open the new report
- Try to unfold/fold a partner line

Issue:
Folding will not fold the first child (representing the created account group). Also, error will raise
```
Uncaught Promise > Got duplicate key in t-foreach: ~account.report~37|~account.report.line~255|{'groupby': 'partner_id'}~res.partner~4226|~account.group~90

Occured on odoo.nas.cpolar.cn on 2025-04-26 04:58:53 GMT

OwlError: Got duplicate key in t-foreach: ~account.report~37|~account.report.line~255|{'groupby': 'partner_id'}~res.partner~4226|~account.group~90
Error: Got duplicate key in t-foreach: ~account.report~37|~account.report.line~255|{'groupby': 'partner_id'}~res.partner~4226|~account.group~90
at AccountReport.template (eval at compile (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:13743:20), <anonymous>:138:49) (/web/static/lib/owl/owl.js:5752)
at App.callTemplate (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:11363:50) (/web/static/lib/owl/owl.js:3372)
at AccountReport.template (eval at compile (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:13743:20), <anonymous>:9:12) (/web/static/lib/owl/owl.js:5752)
at RootFiber._render (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:9774:38) (/web/static/lib/owl/owl.js:1783)
at RootFiber.render (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:9766:18) (/web/static/lib/owl/owl.js:1775)
at ComponentNode.render (https://odoo.nas.cpolar.cn/web/assets/debug/web.assets_web.js:10493:23) (/web/static/lib/owl/owl.js:2502)
```

Analysis:
Folding issues occurs because of a mismatch in the grouping markup quote escape. If we don't have the very same string the controller cannot properly recognize the parent line and then is unable to fold/unfold properly.
This eventually led to the mentioned error at unfold as the backend will try to generate the apparently missing lines to unfold, only to create duplicate lines

opw-4754241

Forward-Port-Of: odoo/enterprise#89726

### Steps to reproduce:
	- Set Marc Demo's contract work entry source to attendances and working schedule to flexible hours.
	- Create a public holiday with generic time off work entry type.
	- Create one or multiple attendances for marc demo on the public holiday.
	- Regenerate work entries for marc demo for that day, the gaps in between the attendances created and the working hours will be filled with work entries with the right start/end time but duration will always be 8h.

### Cause:
This is happening because when getting the duration batch for the work entry we get the attendance intervals the employee should work in that period and if the employee is flexible we will get a fake attendance with the number of hours required per day ignoring if the period is just a small period of the day

### Fix:
We are checking now since the start date not monday so we don't set a fixed week start. We check if the period is less than the remaining hours we get it as it mostly means that it is less than one day

opw-4887933

Forward-Port-Of: odoo/enterprise#90163

> note: this PR should only be FW'd till `saas~18.4`, after that for `saas~18.5` (i.e., `master`), [this PR](https://github.com/odoo/enterprise/pull/85557) should be merged.

### Steps to reproduce:
- Enable "Flexible Hours" in a working schedule.
- Assign the schedule to an employee.
- Generate a payslip for the employee.
- Observe that the "Working Schedule" section always shows `hours_per_week` from
the total hours calculated from the Work Schedule defined before turning on
"Flexible Hours"

### Description:
- the payslip incorrectly displayed the weekly working hours from the Work
Schedule regardless of whether the employee's schedule used flexible hours.

### Cause:
- the report template did not check for the `flexible_hours` flag and always
rendered the value from `contract_id.hours_per_week`.

### Fix:
- added a condition in the payslip template to check if `flexible_hours` is
enabled.
- if true, it displays `full_time_required_hours` from the working schedule
instead of the contract's `hours_per_week`.

task: 4719717

Forward-Port-Of: odoo/enterprise#83910

This [PR](https://github.com/odoo/odoo/pull/209860) adds a fallback to product_uom_qty when the quantity field is not present during
serial/lot generation from the shop floor.

Includes a tour and test case in mrp_workorder to validate the fix.

**Steps to Reproduce :**

1. Install MRP.
2. Create a Bill of Materials (BOM) and add a component with lot tracking.
3. Create and confirm a Manufacturing Order (MO) with BOM.
4. Navigate to the shop floor and click on Generate Serials/Lots.
5. The error appears when trying to generate the lot .

**Issue :**

Error raised when try to Generate Serials/Lots during the manufacturing
process.

`TypeError: unsupported operand type(s) for //: 'NoneType' and 'int'`

**Cause:**

This error occurs because the quantity field is undefined when
Generate Serials/Lots is triggered, the quantity field is not being passed in
the context, and its value is undefined, which is leading to a division by [none](https://github.com/odoo/odoo/blob/18.0/addons/stock/models/stock_move.py#L993).

**Solution:**

To fix this, we added the stock move’s demand quantity as a fallback.This ensures the 
quantity field value is present and its value correctly passed during lot generation.

opw-4763600

Community: https://github.com/odoo/odoo/pull/209860

Forward-Port-Of: odoo/enterprise#90879
Forward-Port-Of: odoo/enterprise#88739

### Problem:
When paying a PoS order using customer account, an account move line debiting Account Receivable will be created. Settling this amount inside the PoS (by depositing money) will create another account move line crediting Account Receivable (represents the payment). The second move line is considered, by Odoo, as an outstanding amount, and this amount can be used to pay another invoice (sale order invoice). The moves affecting Account Receivable are still correct. However, unreconciling the two lines created from PoS will cause a confusion for clients who may use this amount to pay other invoices.

### How to reproduce:
    * Open a PoS session.
    * Create an order and pay using customer account.
    * Settle this customer's account (inside PoS).
    * Create a Sale Order and invoice it (or just an invoice).
    * The amount settled can be used as outstanding amount and can be used to pay the created invoice.

commmunity PR: https://github.com/odoo/odoo/pull/210619#pullrequestreview-2853451890

opw-4794793

Forward-Port-Of: odoo/enterprise#86114