*: pos_restaurant, pos_online_payment_self_order, pos_self_order

When self-ordering is enabled and in pay after each mode, the table
selection was handled via table_id fields, which caused issues when a
customer had an issue with its payment and wanted to pay later. It was
blocking the table with its order, so if another customer wanted to
scan the same QR code, it would not be able to add anything to the cart.

Now in pay after each mode, the table selection is handled via
floating_order_name, which allows the order to be processed without
blocking the table. This way, the table can be reused for another
customer, and the order can be paid later.

---

Regarding direct sale in `point_of_sale`, when a customer wanted to pay
by card the order was synced with the server when the waiter clicked on
the payment method, if the direct sale had no table and no floating
order name, when synching on other devices the order was blocking them.

Now if no table and no floating order name is set, when synching the
order, the pos_reference is set to the floating_order_name, which
prevents the order from blocking other devices.

---

Regarding self order cancellation from a PoS, when the waiter was
cancelling an order it was not synced with the self-order app, which
caused the self-order app to keep the order in the cart, preventing the
customer from starting a new order.

---

Regarding self order ticket printing, when an order arrives on the PoS
to be printed, we were trying to print the preparation ticket and
the customer ticket at the same time, which caused issues with the
printing. Now we printing them one after the other.

Forward-Port-Of: odoo/odoo#222180

[FIX] html_editor: prevent `o_editable_media` class to add `o_dirty`

Before this commit, when the `o_editable_media` class was added on an
element, its closest view was marked as dirty, because of the mutation
it was adding.

This commit fixes that by making this class a system class, so its
mutations are always filtered out.

Steps to reproduce:
- Go in edit mode with eCommerce installed.
- In the header, inspect the shopping cart button and see that its view
  does not have the `o_editable_media` and `o_dirty` classes.
- Change a header option and inspect the button again.
=> the `o_editable_media` class was added, as well as `o_dirty`, because
of that class addition.

task-4367641

---
[FIX] html_builder: prevent drag and drop to add unwanted `o_dirty`

Before this commit, drag and dropping elements from the sidebar or from
the page would add the `o_dirty` class on every views in which dropzones
appeared, creating many views in DB for no valid reason when saving.

This commit fixes this issue by:
- not observing the dropzones addition/removal anymore,
- preventing the drag mutations to mark elements as dirty until we
  finally drop the dragged element.

task-4367641

### Steps to reproduce:

- In the settings enable Multi-Steps Routes
- Put your warehouse in manufacture in 3 steps
- Create a storable product P
- Create and confirm an MO for 1 unit of P
- Go to Inventory > Operations > Procurement > Replenishment
- Create a new one for P in WH/stock
#### > The forecasted quantity in stock is still 0 but should be at 1, just as if the the MO had been generated using the    replenishment for 1 unit

### Cause of the issue:

When an MO is created using a procurement, a `location_final_id` is set to WH/Stock on the MO and propagated on the move for the finished product:
https://github.com/odoo/odoo/blob/8d4e6df0c0ac5ebc6362f3578ae8cc8edf4a76f7/addons/mrp/models/stock_rule.py#L165 https://github.com/odoo/odoo/blob/8d4e6df0c0ac5ebc6362f3578ae8cc8edf4a76f7/addons/mrp/models/mrp_production.py#L1169-L1175 As such, even if the manufacturing is now handled in push, this move will contribute positively to the forecast in the `virtual_available` quantity of the product in WH/Stock bevause of the `location_final_id`. By contrast, if hte MO is created by hand, it does not bear a `location_final_id` so that the MO can only contribute to the stock forecast has been processed and the related internal transfer `WH/post-prod -> WH/Stock` is created.

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

Forward-Port-Of: odoo/odoo#221462
Forward-Port-Of: odoo/odoo#221003

Currently below error occurs while archive/unarchive company:
- Company list is not being updated.
- In `hr_timesheet` KeyError will be encountered on unarchiving a company.
- In `l10n_it_pos` module an AccessError will be encountered on unarchiving a company.

**Root Cause:**
Since https://github.com/odoo/odoo/commit/22e9d822e8cab08114c006eb8c4054c4de0c40f2, the `session_info` method relies on `user_companies` at [1], which fetches only
active company IDs via `_get_company_ids()`. However, `_get_company_ids` uses caching as
shown at [2]. When a company is archived or unarchived, 'write' method is called. Now, here
the cache is invalidated before writing to the company as shown at [3]. Due to which
'_get_company_ids' method doesn't receive the updated list of companies, causing this issue.

**Solution:**
This commit prevents error by ensuring companies are stored before invalidating
the cache.

[1]- https://github.com/odoo/odoo/blob/d3482e32f7dbe273125de84f1bbc434ac3c9ffc3/addons/web/models/ir_http.py#L146

[2]-
https://github.com/odoo/odoo/blob/7db62d6d65bd57f6ed43ce52a820cf03df19efdd/odoo/addons/base/models/res_users.py#L927-L931

[3]-
https://github.com/odoo/odoo/blob/3173a5f993a3ffa3d3a14d29713142e5b6b314d9/odoo/addons/base/models/res_company.py#L343-L367

Sentry-6251348500

Forward-Port-Of: odoo/odoo#222251
Forward-Port-Of: odoo/odoo#219044

Steps to Reproduce:
1. Go to the website.
2. Create a new menu (e.g., 'Test 1') using the 'Edit Menu' option and add it under another menu (e.g., 'Contact Us'), creating a sub-menu. 
3. Turn on the developer mode.
4. Go to Configuration -> Menus and add two menus (e.g., 'menu 1' and  'menu 2') under the new sub-menu (e.g., 'Test 1').
5. Notice that the two menus ('menu 1' and 'menu 2') are not visible on the website.

Description:
As per functional specifications, creation of multi-level sub-menus should not be allowed.

Key Changes:
raises a `UserError` if a menu exceeds the two-level hierarchy by checking the parent and grandparent levels.
- Implements mega menu restrictions:
    - A mega menu cannot have a parent menu.
    - A mega menu cannot have child menus.
    - Any menu cannot be a child of a mega menu.
- Prevents menus with child menus from being added as submenus to existing menus.

This ensures that the website menu structure adheres to the defined functional specifications, providing a consistent and predictable user experience.

task-3901371

Forward-Port-Of: odoo/odoo#222254
Forward-Port-Of: odoo/odoo#168801

Steps:
-------------------------------------------------
- Set up a database without demo data.
- Open Cloth Shop POS.
- Click on load sample data.

Issue:
-------------------------------------------------
Data doesn't load.
(Traceback in terminal for not found external ID)

Cause:
-------------------------------------------------
Commit https://github.com/odoo/odoo/commit/ffb976c3ed5fbcff2e5d06a3183bab2fbe0307ff moved demo data from point_of_sale to product. The issue is that point_of_sale uses a custom 'scenario' flow where demo data gets loaded for a specific scenario. As a consequence, any reference to demo data from the product will cause an error.

Solution:
-------------------------------------------------
- Move the shoe size attribute back to the pos cloth scenario from product.
- Load attribute from the product when we click on Load Sample Data in the cloth shop.

task - 5002430


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

If the editing element has no `oeContactOptions`, the selector would compare against the string `"undefined"`. That selector is supposed to select the ones with a different option, but in that case, other fields without contact options would get selected. The selector was ported from the previous builder during the intial [website builder refactor]

This caused the editing element to be present twice in the loop if it had no contact options (in addition to contain extra elements). And setting twice the same text content triggers a bug in the history, which behaves incorrectly when it is undone. (the bug is known and described in the code by a comment `@todo: this removes mutation records that change the node reference. Fix this`)

Steps to reproduce:
- On `/blog`, open website builder
- Change a post's category (name next to the folder icon under summary)
- Undo
- Bug: the text content is the concatenation of both category

[website builder refactor]: 9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2
task-4367641

When tax integrations are sent from a credit note (of a vendor bill) they should have a negative value, as it is the reversal operation. However, currently the amounts are positive, so it appears to be a second Bill rather than its reverse.

**Steps to reproduce (with an IT Company)**

- Create a non-eu [PARTNER] with complete address and VAT
- Create a Vendor Bill with:
  - Partner: [PARTNER]
  - Electronic Invoicing > Document Type set to TD18
  - A line having Reverse charge tax (ie. 22% G RC)
- Confirm and send tax integration
- Reverse move
- Ensure the document type is set to TD18 as well
- Confirm and send tax integration
- Check the generated xml

**Issue**

Credit note tax integration will have a positive amounts, while being a credit note it should have negative amounts This occurs because when generating the xml, the document type is recomputed from the invoice features, even if the user set it manually

Ticket [link](https://www.odoo.com/odoo/project/967/tasks/4788529)
opw-4788529

Forward-Port-Of: odoo/odoo#221672
Forward-Port-Of: odoo/odoo#220878

Before this change, the VAT Content section in Argentinean Legal PDF was always shown as "VAT Content" although the user has Spanish as its language.

With this change will show the correct translation: "IVA Contenido" when printing the PDF report in Spanish.

### **Description of the issue/feature this PR addresses:**
Missing Spanish translation of "VAT Content" column in the Argentinean Legal PDF Report

1. Install Argentinean - Accounting module
2. Install Spanish language
3. Log into to one of the demo Argentinean Companies: (AR) Responsable Inscripto
4. Create a customer invoices of type "B"
5. Go to the partner and change the Language to Spanish
6. Return to the invoice and print the PDF
7. Check that the VAT Content section is not translated.

### **Current behavior before PR:**
<img width="572" height="407" alt="image" src="https://github.com/user-attachments/assets/e28e609e-2cd2-4ace-9509-f969692ec893" />

### **Desired behavior after PR is merged:**
The "VAT Content section should appear as "IVA Contenido" when printing the report in Spanish.


opw-4938520

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

Forward-Port-Of: odoo/odoo#221832
Forward-Port-Of: odoo/odoo#219912

Currently a below occurs or content is not receiving to odoo WhatsApp when the user uploads a large file (tried with > 35 MB).

Stack Trace:
```
MemoryError: null
  File "odoo/http.py", line 2383, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1913, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1976, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1943, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2187, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 227, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 757, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/controller/main.py", line 42, in webhookpost
    wa_account_id._process_messages(value)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/models/whatsapp_account.py", line 206, in _process_messages
    datas = wa_api._get_whatsapp_document(messages[message_type]['id'])
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 236, in _get_whatsapp_document
    file_response = self.__api_requests("GET", file_url, auth_type="bearer", endpoint_include=True)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 46, in __api_requests
    if 'error' in res.json():
  File "requests/models.py", line 971, in json
    return complexjson.loads(self.text, **kwargs)
  File "requests/models.py", line 928, in text
    encoding = self.apparent_encoding
  File "requests/models.py", line 793, in apparent_encoding
    return chardet.detect(self.content)["encoding"]
  File "__init__.py", line 49, in detect
    detector.feed(byte_str)
  File "chardet/universaldetector.py", line 274, in feed
    if prober.feed(byte_str) == ProbingState.FOUND_IT:
  File "chardet/charsetgroupprober.py", line 70, in feed
    state = prober.feed(byte_str)
  File "chardet/hebrewprober.py", line 240, in feed
    byte_str = self.filter_high_byte_only(byte_str)
  File "chardet/charsetprober.py", line 73, in filter_high_byte_only
    buf = re.sub(b"([\x00-\x7F])+", b" ", buf)
  File "__init__.py", line 186, in sub
    return _compile(pattern, flags).sub(repl, string, count)
```

At line [1], the code `'error' in res.json()` is used, which reads all the json content of `res`, but at times users upload large files, it will cause the above error because the `json()` tries to read all bytes from res, which is a very large amount to handle in memory.

This commit will fix the above issue by returning a response if the response
contains content_length more than 10 MB.

[1] - https://github.com/odoo/enterprise/blob/aca7ae2a7cf4aad5427a60d5cad60d08774357d0/whatsapp/tools/whatsapp_api.py#L46

sentry-5810101850

Forward-Port-Of: odoo/enterprise#70001

This PR is divided in 2 commits:

A first commit is an implementation AU specific and will create the lines related to tax on
salary in the tax return closing entry. Before this commit, these lines
weren't taken into account in the closing entry.
The condition to select the account.move.line are the following:
- The journal item has a "W2", "W3" or "W4" (Withholding Tax) tax grid 
whose journal entry is linked to an hr.payslip.
- The journal item does not have an originating tax record (i.e.,
tax_line_id is empty).
- The journal item is posted to a tax provision account (i.e., a balance
sheet one) as defined on the salary rule.

A second commit fixes a bug: the manifest of the l10n_au_hr_payroll_account module was having a
'countries': ['au'] dependency, that was adding a condition to the
dependencies to auto install the module: we expect an existing AU
company in DB. But for example if the user installs l10n_au, the
condition is evaluated at the moment he clicks on install, and no AU
company exists at that time.

Task-4921992

Forward-Port-Of: odoo/enterprise#90422

Issue:
When the "Lock Confirmed Sales" setting is enabled, adding a product to a Field Service task would lock the associated sales order before its picking could be created. The confirmation process locks the order first , and the subsequent step to create stock moves (`_action_launch_stock_rule`) explicitly skips locked orders.

Reproducible on 17.0~master
[Task](https://www.odoo.com/odoo/action-4043/4633977)
Odoo 17:
https://drive.google.com/file/d/1qmAYhSu6gU91efuJEDF-Irn2cLGUQP0A/view?usp=drivesdk

Odoo 18:
https://drive.google.com/file/d/1x8IeXwT7ZFM7Av9Vp6GSvGIbOaEGfmVx/view?usp=drivesdk


Steps to reproduce:
1. In Sales > Configuration > Settings, enable "Lock Confirmed Sales".
2. Go to a Field Service task.
3. In the kanban view via the "Products" smart button, add a product.
4. Come back to the task, refresh the browser, open the linked Sales Order from the smart button.
5. **Before this fix:** The SO is locked, no picking is created, and SO lines will have delivered_qty set even though we haven't delivered anything.
6. **After this fix:** The SO is not locked, and a Delivery smart button is correctly displayed, linking to the generated picking.

This behavior left the sales order in an inconsistent state: it was locked, but had no corresponding delivery order. As a result, users were blocked from removing or modifying the products added to the task, as the system prevented edits on a locked order with no picking to cancel.

Let's step through what's going on here;

0. We enable "Lock Confirmed Sales" option.
1. Add a product to the Field Service(FS) task https://github.com/odoo/enterprise/blob/4256ea170c31209b83ff808e51145757571f8556/industry_fsm_sale/controllers/catalog.py#L19-L42
https://github.com/odoo/enterprise/blob/4256ea170c31209b83ff808e51145757571f8556/industry_fsm_sale/controllers/catalog.py#L38
2. set_fsm_quantity() is invoked, which will create a SO for the FS task https://github.com/odoo/enterprise/blob/35e1f47160d5840e8701fc0ad43ec42bbfaf9e36/industry_fsm_sale/models/product_product.py#L144
3. `_fsm_create_sale_order()` will immediately `action_confirm()` the new SO, because of the reasons in the function description. 
( Since we are immediately confirming newly created SO, I think we should consider not applying the "Lock Confirmed Orders" option to FSM SOs.)
https://github.com/odoo/enterprise/blob/2347dac2568dbcf83578f044f8fe41ab70a20f47/industry_fsm_stock/models/project_task.py#L124-L134 https://github.com/odoo/enterprise/blob/2347dac2568dbcf83578f044f8fe41ab70a20f47/industry_fsm_stock/models/project_task.py#L134
4. `odoo/addons/sale/models/sale_order.py/action_confirm()` will lock SO because we enabled 'Lock Confirmed Sales'
https://github.com/odoo/odoo/blob/863c064fd911cb4eeedad0abec82adb4690128f6/addons/sale/models/sale_order.py#L964
6. `_action_launch_stock_rule()` is invoked, is in charge of creating Pickings for SOs 
https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L303
https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L343-L344
7. But, since `line.order_id.locked` , the system do not create Pickings for the SOs. https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L315-L316
The line was introduced by
https://github.com/odoo/odoo/commit/17bece3e797913bcba8dd7e07fc8541c0a45e3f7

This commit resolves the issue by passing a context key `fsm_create_sale_order=True` when confirming a sales order that is being created from a Field Service task. The `_should_be_locked` method on the sale order is overridden to check for this context key. If the key is present, it prevents the order from being locked within that specific transaction, allowing the stock rules to execute correctly and create the necessary picking. The order will be locked for any subsequent operations as intended.

Tradeoff here;
We are sacrificing the universal application of one feature (automatic lock on confirmed sales order) to fix a critical bug that makes the entire FSM delivery process unusable.

---
EDIT: 
Without this change, all of [test_fsm_stock](https://github.com/odoo/enterprise/blob/17.0/industry_fsm_stock/tests/test_fsm_stock.py)'s test cases that use `_fsm_ensure_sale_order()` will fail if the setting is on. (around ~20 test cases). 

[In the past, similar issue occurred for Subscription Orders, and the PO confirmed that the "Lock Confirmed Order" setting should never affect the subscriptions. ](https://github.com/odoo/enterprise/commit/e4f9d76c0a58f3cc226a2372f3936cea4547312e). This commit takes the same approach to ignore the setting upon SO confirmation. 

opw-4633977
opw-4749653
opw-4880664

Forward-Port-Of: odoo/enterprise#91799
Forward-Port-Of: odoo/enterprise#88855