Original PR description

This update ensures that the correct employee and parent IDs are fetched depending on whether the widget is displayed in a `res.users`, `hr.employee` or `hr.employee.public` form. The `onWillStart` was removed since `useRecordObserver` is triggered in `onWillStart`, and both used to have the same logic.

task-5039701

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

Forward-Port-Of: odoo/odoo#224456

Original PR description

Before this commit, an error would occur if a header setting did not contain an attribute string or field. This was because the code tried to infer the label. However, the label should be optional.

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

Original PR description

Opening the Employee form on mobile and tapping the gear icon could crash because `PresenceActionItems` was undefined. Initialize it and guard the template.

task-5055564

Original PR description

Currently, an error occurs when refreshing a live session's `Thank You` page 
after deleting a survey question.

**Steps to reproduce:**

- Install the `survey` module.
- Create a `new survey`, `add a question` and click on `Create Live Session`.
- Complete the survey and leave it on the `Thank You` page.
- Switch back to the `first tab`, delete the question and `save` the survey.
- Return to the `Thank You` tab and `refresh` the page.

**Error:**
`IndexError: list index out of range`

**Root Cause:**
At [1], the controller assumes the question exists and tries to access 
`index [0]`, but when the question has been deleted, the recordset is 
empty, causing an `error`.

[1]
https://github.com/odoo/odoo/blob/ffd9c0f96bda1bad1ad2059d9be2fae54b60eace/addons/survey/controllers/survey_session_manage.py#L236

This commit prevents a crash when refreshing a live session if the question was 
deleted.

sentry-6736648824

Forward-Port-Of: odoo/odoo#218312

Original PR description

When a user tries to save a view with an invalid tag, an error occurs.

**Steps to produce:-**
1. Go to Settings > Technical > User Interface > Views.
2. Click on New.
3. Add the view name. In architecture -> add `<template></template>`.
4. Try to save the changes.

**Error:-**
`ValueError:Wrong value for ir.ui.view.type: 'template'`.

**Root cause:-**
- The view type in `ir.ui.view` is automatically inferred from the 
  `root tag` of the XML defined in the `arch` field.
- In this case, `<template>` becomes the inferred view type, 
  which is not part of the valid selections for the type field in the 
  model `ir.ui.view`.

**Solution:-**

 - Before calling `super().create(vals_list)`, add a validation check to ensure
  `values['type']` is in the allowed types. If not, raise a ValidationError.

sentry-6561028171

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

Original PR description

PR [1] aimed at fixing a double-click issue with the delete button in x2many lists. In standard views, it works fine. However, there are customizations (e.g. project sub tasks, product attributes...) that add a confirmation step before actually removing the row. If the user cancelled the deletion, clicking on the delete icon of that row afterwards had no effect at all.

This commit fixes the issue by re-enabling the button after 500ms, thus only preventing double clicks.

[1] https://github.com/odoo/odoo/pull/173481

opw~5019621

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

Description of the issue/feature this PR addresses:
The document layout wizard (base.document.layout) attempts to write the partner’s bank account number even if it has not been changed. If the first bank account is marked as trusted, Odoo blocks the write and raises an error. This PR prevents that error by only writing the account number when it has actually changed.

Current behavior before PR:
- The wizard shows the account_number field.
- On saving, _inverse_account_number always writes to the first partner bank account.
- Trusted bank accounts trigger an error: “You cannot change the account number or partner of a trusted bank account.”

Desired behavior after PR is merged:
- The wizard still shows the account_number field.
- On saving, _inverse_account_number only writes if the value changed.
- Trusted bank accounts that are not modified do not cause an error.



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

Original PR description

**Steps to reproduce**
- On a fresh DB, have multiple companies
- Install documents_sign
- With a company other than the main one, go to Settings > Documents >
try to change a setting (e.g. Spreadsheets Workspace)
- Error: "Invalid fields: Sign Base Folder"

**Cause**
The `documents_sign_folder_id` is only set on the main company and since
it is invisible and required on the view, saving it is impossible.

**Change**
Since the folder serves no purpose, make it non required in the view.

opw-5048447

Original PR description

After the switch to Weblate, we now only use the `.weblate.json` file instead of the previous `.tx/config` file.

Meanwhile added a new entry that was still added to the `.tx/config`.

Forward-Port-Of: odoo/odoo#225179