**Steps to reproduce:**
- Sign into one user
- Go to his `Preferences` menu
- Set notification to `Handle in Odoo` (`notification_type='inbox'`)
- Enable push notification in the browser
- Go to another window / browser (at the same time as the first one is opened)
- Log in with another user
- Go to any record with a chatter, then ping the first user with a message
- Two push notifications are received by the first user, for the same message
(This only happens if the receiving user tab is still open)

**Issue:**
When using default `notification_type='email'`, notification is created by
the mail part and sent with a web_push.
(`_notify_thread_by_email` and `_notify_thread_by_web_push`)

When using `notification_type='inbox'`, it is triggered as a bus notification and
a web_push, which led to duplicates on the user side.
(`_notify_thread_by_inbox` and `_notify_thread_by_web_push`)

Also, we can't just remove any of the two as they serve different purposes.

```
-> (backend) -> mail.thread
    -> _notify_thread_by_inbox -> user with mail.thread -> bus.bus
        -> (frontend) -> bus_service -> mail.out_of_focus -> notify -> serviceWorker -> "message" event -> browser web_push
    -> _notify_thread_by_web_push -> stored devices -> push_to_end_point
        -> (frontend) -> device -> serviceWorker -> "push" event -> browser web_push
```

**Fix:**
Reapply this fix https://github.com/odoo/odoo/commit/4fc16a3cc469dbdc206260487693a572ba62cbbe
to explicitly check for redundant notification when `this.store.self.notification_preference === inbox`.

The service worker only shows a push notification if no open tab refuses it, this is done
by sending a `notification-display-request` and if any tab answers with a
`notification-display-response` the notification is removed.

Seems to kind of work, but the notification might be rethrown in edge cases (quick refresh ?).

The fix ensures the browser ignore duplicate inbox push notifications since
they're already handled by `mail.message/inbox` bus notifications, and
the `modelsHandleByPush` heuristic in `out_of_focus_service.js` isn't reliable
enough to detect these cases. The logic should probably be improved in master.

opw-4639507

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

Forward-Port-Of: odoo/odoo#221259

…xported pdf

#### Issue
In the Trial Balance when using a filter if hierarchy is enabled, the exported report filters only on the account name, not on the group name.

#### Step to reproduce:
- Create an account group (e.g Group_101 from 101 to 101)
- Create some AML in an account related to the previously created group (e.g. in 101501 Cash)
- Go to the Trial Balance ( Accounting > Reports > Audit Reports > Trial balance )
- In the Options select "Hierarchy and subtotals"
- Add a filter including your group name (e.g. Group_101)
- Export to pdf

#### Current behavior:
- No lines are displayed in the pdf as the backend uses only the account name to apply the filter

#### Expected behavior:
- Lines are displayed using account name and group name to filter

#### Cause:
- Filter was applied only on account name

#### Solution:
- If hierarchy is enabled, display accounts where filter appears on either account or group

opw-4906593

Forward-Port-Of: odoo/enterprise#96338
Forward-Port-Of: odoo/enterprise#90403

Description of the issue/feature this PR addresses:
When an exception is raised on the access check, the OutdatedPageWatcherService runs into a reconnect loop, resulting in lots of log entries. 

<img width="1190" height="435" alt="image" src="https://github.com/user-attachments/assets/8634e254-344f-4f4f-a46e-c0b3674de303" />

Each reconnect attempt causes a log entry: 
```
2025-08-22 11:30:17,770 4 INFO db18_test_access odoo.addons.base.models.ir_rule: Access Denied by record rules for operation: write on record ids: [25], uid: 6, model: crm.lead 
2025-08-22 11:30:17,779 4 WARNING db18_test_access odoo.http: Uh-oh! Looks like you have stumbled upon some top-secret records.

Sorry, Marc Demo (id=6) doesn't have 'write' access to:
- Lead/Opportunity, Modern Open Space (crm.lead: 25)

Blame the following rules:
- Personal Leads

If you really, really need access, perhaps you can win over your friendly administrator with a batch of freshly baked cookies. 

```



Current behavior before PR:
Reconnect loop.

Desired behavior after PR is merged:
Do not add channels without sufficient rights.


Related to: https://www.odoo.com/de_DE/my/tasks/5026412

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

Forward-Port-Of: odoo/odoo#231599
Forward-Port-Of: odoo/odoo#223890

Cherry pick of two commits from 18.4

Commit 1: 379d324

Previously, the link popover did not support frontend website pages
(e.g., /contactus, /shop, etc.).

Steps to reproduce:
- Enter edit mode.
- Click on a link to a frontend page, such as "Contact Us".
- An error was thrown in the browser console.
- Also, the link popover did not show the page description (even if it
  existed).

This commit:
- Fixes the error that occurred in the browser console.
- Adds support for frontend website pages in the link popover.
- Displays the page description in the linkpopover, if available.
  (The page description refers to the SEO field that can be set via:
  Site > This Page > Optimize SEO > Description)

Commit 2: b8908f3

Before this commit: the condition to check if an url is internal is not complete
as the user could user the odoo instance domain instead of the real domain. The
check if an internal url is a frontend one is rather naive as there are cases
where the url ends with a number but actually not leading to a record.

Reproduction for the second use case:
1. create a link with frontend url for example `/shop/category/16`
2. click on the link, when it loads the preview, a warning pops up

After this commit, the cases explained above are included.

task-4971829



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

Forward-Port-Of: odoo/odoo#232537

The system crashes when a user tries to edit a website form field and that field has already been deleted from the model.

**Steps to produce:-**
- Install the `website` module.
- Create a `new custom field` on a model(for example, a field on the `mail.mail` model).
- Website > edit > `add Form` widget to a page, and configure it to use the `mail.mail` model.
- Add the newly created custom field to the form and save the page.
- Now, `delete` the custom field which is created previously.
- Return to the website page > edit > mark the deleted field as required, and attempt to save the changes.

**Error:-**
`ValueError: Unable to whitelist field(s) [''] for model 'mail.mail'.`

**Root cause:-**
- At [1], we can see that in the current version, it `only logs an error` using the logger, but in later versions, it `raises a ValueError` instead.

**Solution:-**
- This fix prevents a field from being deleted if it is actively used in any website form.
- It adds a validation check that blocks the deletion and raises an error, forcing the user to remove the field from the form first.

[1]: https://github.com/odoo/odoo/blob/d4f424d731fa93ccd232d0def0a7612997345ef7/addons/website/models/website_form.py#L123-L126

**sentry-5689731444**

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

Forward-Port-Of: odoo/odoo#219590

Currently, when a user uses the 'Set Account' button to reconcile a
statement line, the system may also create a reconciliation model
for fees for the given journal/account combination, based on the
previous statement line reference pattern.

To extract a patter from the references, the system computes the
normalised longest common substring. This will be used as regex
matching pattern of the newly created reconciliation rule.

However, the common substring may end up with '\\', which is not a valid
termination of a regex, leading to the error:
`Invalid operation. The regex is invalid.`

Steps to reproduce:

- Have an account '646000 Test Account'
- Create a Bank statement with label 'TEST REFERENCE BNK 2024'
- Set Account 646000
- Create a Bank statement with label 'TEST REFERENCE BNK.OTHER'
- Set Account 646000

Issue:

Error `Invalid operation. The regex is invalid.` will raise
blocking the action

[opw-5086638](https://www.odoo.com/odoo/project.task/5086638)
[opw-5062965](https://www.odoo.com/odoo/project.task/5062965)
[opw-5123963](https://www.odoo.com/odoo/project.task/5123963)
[opw-5166160](https://www.odoo.com/odoo/project.task//5166160)
[opw-5159871](https://www.odoo.com/odoo/project.task/5159871)
[opw-5160108](https://www.odoo.com/odoo/project.task/5160108)
[opw-5109454](https://www.odoo.com/odoo/project.task/5109454)
[opw-5086638](https://www.odoo.com/odoo/project.task/5086638)
...