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

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
8. 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/1f3e7556-2ffc-4cb4-8c61-9bee4248650c" />


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

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

Currently, an error occurs when a user tries to create a new warehouse, but the referenced stock location (record: **Physical Locations**) has been deleted.

**Steps to reproduce:**
- Install the `stock` module without the demo data.
- Enable **Multi-Step Routes** in Inventory settings.
- Delete all Stock Rules and then the existing warehouses.
- Navigate to `Inventory > Reporting > Locations` and delete the **Physical Locations**.
- Try to create a new warehouse.

**Error:**
`ValueError: External ID not found in the system: stock.stock_location_locations`

Here, an error occurs when the system tries to fetch `stock.stock_location_locations` during warehouse creation [1], but the record has been deleted, resulting in a parse error.

[1] - https://github.com/odoo/odoo/blob/834eff6e770280e911bb99e2abab4ea42d4ca8ff/addons/stock/models/stock_warehouse.py#L123-L125

This commit prevents the error by assigning `False` to `location_id`, if the reference is missing.

Sentry - 6577063404

#### Step to reproduce:
- Go to Inventory > Configuration > Settings  and enable Packages
- Go to Inventory > Configuration > Package Types
- Inverse the order of two packages types. The goal is for the sequence order to differ from the id order. (you can display id with studio)
- Go to Inventory > Overview > Delivery Orders
- Create a new delivery order
- Add a line
- In 'Additional Info' add a Carrier
- Go to Barcode > Operations > Delivery Orders
- Select the delivery order (you might need to remove filters)
- With the 'Add Product' button add a product
- Click on 'Put in Pack'
- A 'Package Details' wizard should have opened. In this wizard there is a field 'Delivery Package Type'.

#### Current behavior:
- In the delivery package type dropdown list, packages are ordered by id

#### Expected behavior:
- In the delivery package type dropdown list, packages should be ordered by sequence

#### Cause of the issue:
As no order was defined, stock.package.type was ordered by id which is the default behavior

opw-4824064

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

Forward-Port-Of: odoo/odoo#220327

Currently, an error is produced when loading sample data if a referenced skill type record in the skill level has been deleted by the user.

**Steps to Reproduce:**
- Install the `hr_appraisal` module without demo data.
- Navigate to `Employee > Skills Types` and delete the `Languages` record.
- Load the sample data for appraisal.
- Observe the error.

`ValueError: ParseError('while parsing /home/odoo/src/odoo/saas-18.2/addons/hr_skills/data/scenarios/hr_skills_scenario.xml:19...`

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

[1] - https://github.com/odoo/odoo/blob/547327f30d2d4bf778b9d358dbea4b133d55188a/addons/hr_skills/models/hr_employee.py#L49
[2] - https://github.com/odoo/odoo/blob/547327f30d2d4bf778b9d358dbea4b133d55188a/addons/hr_skills/data/scenarios/hr_skills_scenario.xml#L23

This commit ensures that all the referenced data is loaded properly, preventing errors due to missing references.

Sentry - 6533879252

Currently, an error occurs when clicking the optimize SEO button for the livechat page.

**Steps to reproduce:**
- Install the `website_livechat` module.
- Add menuitem with url `/livechat/channel/yourwebsite-com-1` as `livechat`.
- Go to the **Home** page and publish it using the `Published` button (shows `Optimize SEO` popup).
- Change the page to `livechat` and click the `Optimize SEO` button before it disappears.
- Observe the error.

**Error:**
`ValueError: Invalid field 'website_meta_title' on 'im_livechat.channel'`

The error occurs because the system attempts to update the default `fields` [1] on the current model at [2] who doesn't have the fields.

This commit ensures that if any required SEO fields are missing from the model, the system will return early with `can_edit_seo` set to `False`, thereby preventing the error.

[1] - https://github.com/odoo/odoo/blob/c87acdcfa48b1d8aa66bb5d27d58e3edb70a86ba/addons/website/controllers/main.py#L810

[2] - https://github.com/odoo/odoo/blob/c87acdcfa48b1d8aa66bb5d27d58e3edb70a86ba/addons/website/controllers/main.py#L824

Sentry - 6330105753

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

Currently, a traceback is occurring when the user clicks on the update button 
of GST warning after removing the vat.

To reproduce this issue:

1) Install l10n_in
2) Open the Indian company
3) Change the VAT to get the GST warning
4) After getting the GST warning remove the VAT and click the `update it` button

Error:- 
```
TypeError: 'bool' object is not subscriptable
```

On company, VAT is not a required field, so the user can indeed remove it.

When the user removes the vat and clicks on the `update it` button from GST warnings, the `action_update_state_as_per_gstin` method triggers.

https://github.com/odoo/odoo/blob/c96d2b1d1ee917b1c665842010c56c23df91ccd3/addons/l10n_in/models/res_partner.py#L99-L101

From the above method we try to access the vat value. Here in our case, the `VAT` value is False. So it leads to the above traceback.

We can resolve this issue by adding check, which makes the code more robust.

sentry-6151570042

Forward-Port-Of: odoo/odoo#190840

When the user clicks on Load sample data button after deleting the stages,
A traceback will appear.

Steps to reproduce the error:
- Install ``hr_recruitment`` module
- Go to Recruitment > Configuration > Stages > Delete all stages
- Go to Recruitment > Applications > By Job Positions > Load sample data

Traceback:
```
ValueError: External ID not found in the system: hr_recruitment.stage_job3

ParseError: while parsing /home/odoo/src/odoo/addons/hr_recruitment/data/scenarios/hr_recruitment_scenario.xml:94, somewhere inside <record id="scenario_applicant_macm_enrique" model="hr.applicant">
    <field name="candidate_id" ref="scenario_candidate_enrique" />
    <field name="priority">2</field>
    <field name="linkedin_profile">www.example.linkedin.com/in/enrique.jones</field>
    <field name="job_id" ref="job_marketing" />
    <field name="user_id" ref="base.user_admin" />
    <field name="medium_id" ref="utm.utm_medium_direct" />
    <field name="department_id" ref="dep_marketing" />
    <field name="salary_expected">2900</field>
    <field name="stage_id" eval="ref('stage_job3ob3', raise_if_not_found=False)" />

    <field name="create_date" eval="DateTime.today() - relativedelta(months=2)" />
    <field name="date_last_stage_update"
       eval="DateTime.today() - relativedelta(days=1)" />
 </record>
```

This commit resolves the error by ``raise_if_not_found=False`` for the field if the stage is missing.

sentry-6530485438

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

An UnboundLocalError was occurring due to referencing the variable `activity` before it was assigned a value.

Traceback : 
---
```
UnboundLocalError: cannot access local variable 'activity' where it is not associated with a value
  File "odoo/http.py", line 2416, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1942, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 2006, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 137, in retrying
    result = func()
  File "odoo/http.py", line 1973, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2224, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 335, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 741, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/rpc/controllers.py", line 177, in jsonrpc
    return dispatch_rpc(service, method, args)
  File "odoo/http.py", line 397, in dispatch_rpc
    return dispatch(method, params)
  File "odoo/service/model.py", line 85, in dispatch
    res = execute_kw(db, uid, *params[3:])
  File "odoo/service/model.py", line 108, in execute_kw
    return execute(db, uid, obj, method, *args, **kw or {})
  File "odoo/service/model.py", line 115, in execute
    res = execute_cr(cr, uid, obj, method, *args, **kw)
  File "odoo/service/model.py", line 99, in execute_cr
    result = retrying(partial(call_kw, recs, method, args, kw), env)
  File "odoo/service/model.py", line 137, in retrying
    result = func()
  File "odoo/service/model.py", line 62, in call_kw
    result = getattr(recs, name)(*args, **kwargs)
  File "<decorator-gen-44>", line 2, in create
  File "odoo/orm/decorators.py", line 317, in _model_create_multi
    return create(self, [arg])
  File "addons/mail/models/mail_activity.py", line 303, in create
    activity.user_id._bus_send("mail.activity/updated", {"activity_created": True})
```

The error occurs at [1] because `activity` is used in the `_bus_send` call without being properly initialized within that scope.

This commit will resolve the above error by passing `todo_activities` instead of `activity`, ensuring that all users linked to overdue activities are properly notified.

[1]- https://github.com/odoo/odoo/blob/f82f768729d897fa54b04789f4e0637ed1bb27f4/addons/mail/models/mail_activity.py#L306-L308

sentry-6273716627

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

**Steps to reproduce:**

1. Install delivery_sendcloud.
2. Create a new shipping method (Inventory -> Configuration)
   - Provider: sendcloud
   - Put the public and secret key
   - Assign Delivery Product
3. Create a sales order with a deliverable product
4. Confirm the sale order
5. Go to the delivery
6. Manually enter a random tracking reference.
7. Make sure carrier is set to the Sendcloud delivery method
8. Click on "tracking," or get back to the sales order (click "preview").
9. A traceback occurs.

**Issue:**

`A TypeError: 'bool' object is not subscriptable`

when accessing sendcloud_parcel_ref, which is expected to be a list or JSON but is instead a boolean.

**Causes:**

The code assumes the presence of valid Sendcloud parcel reference data, but manually entering a tracking reference bypasses the [_send_shipment](https://github.com/odoo/enterprise/blob/6ecf0af6b6874460d300ede6cc7c092927607810/delivery_sendcloud/models/sendcloud_service.py#L102) method that populates this field. As a result, sendcloud_parcel_ref can remain False.

https://github.com/odoo/enterprise/blob/df924ef8adffb3e42419a44ecf22fec3059917c4/delivery_sendcloud/models/delivery_carrier.py#L196

**Solution:**
Return None if there is no Sendcloud parcel reference, which will
raise a UserError from the below line
https://github.com/odoo/odoo/blob/17.0/addons/stock_delivery/models/stock_picking.py#L288

Co-Author By - alsh@odoo.com

opw-4894677

Forward-Port-Of: odoo/enterprise#89444