Notification messages in the mail app are now included in search results. This makes it easier for users to find important updates and communication records that were previously harder to locate.

Make the notification message searchable.

Task-4828780

The update prevents an unexpected system error when a sequence is configured with an invalid suffix. Instead, users receive a clear error message so administrators can correct the sequence format without disrupting sales order creation.

This error occurs when the user provides an invalid suffix in ir_sequence.

Steps to Reproduce:
- Install `sale_managment`.
- Open `Sequences` from `Technical` and open `Sales.Order.`
- Add Suffix as `S %(y)s %(y + 1)s 000`.
- Create a new sale order and save it.

`KeyError: 'y + 1'`

This error occurs when the system tries to generate a sequence at [1] but receives an invalid suffix format.

This commit resolves the error by raising a `user error` for an invalid sequence.

Link [1]
https://github.com/odoo/odoo/blob/0f452cab601350df1dd1a8322c91a9f7da736873/odoo/addons/base/models/ir_sequence.py#L236

Sentry- 6541044217

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

Description ----------- Upon importing contracts, in `_recompute_work_entries`, a wizard is created where we set the employee and a timeframe. The field `employee_ids` is a stored `Many2many` and upon reading its content, an active test is performed in `convert_to_record`, meaning that if the employee is archived, reading `employee_ids` would yield `[]`. This is problematic in `regenerate_work_entries` which therefore will search and write on *all* work entries in the timeframe, since readi

Description
-----------
Upon importing contracts, in `_recompute_work_entries`, a wizard is created where we set the employee and a timeframe. The field `employee_ids` is a stored `Many2many` and upon reading its content, an active test is performed in `convert_to_record`, meaning that if the employee is archived, reading `employee_ids` would yield `[]`.

This is problematic in `regenerate_work_entries` which therefore will search and write on *all* work entries in the timeframe, since reading `employee_ids` returns an empty list -> all employees.

This commit adds a context key to take archived records when regenerating work entries.

Reference
---------
opw-4813590


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

Forward-Port-Of: odoo/odoo#211748

Description of the issue/feature this PR addresses: Task ID: 4636082 This is a backport of: https://github.com/odoo/odoo/pull/207633 (to be forwarded up till 17.4) Current Behavior before PR: - When printing an invoice with a currency that is different than the company's currency. The amount value of each line is only printed in the invoice's currency and not the company's currency. - As per the FTA article 59, the line amount should also be expressed in AED. - The tax excluded amount

Description of the issue/feature this PR addresses:
Task ID: 4636082

This is a backport of: https://github.com/odoo/odoo/pull/207633 (to be forwarded up till 17.4)

Current Behavior before PR:
- When printing an invoice with a currency that is different than the company's currency. The amount value of each line is only printed in the invoice's currency and not the company's currency.
- As per the FTA article 59, the line amount should also be expressed in AED.
- The tax excluded amount was also always printed regardless of the company's setting. (something that was fixed in https://www.odoo.com/odoo/project.task/4625855?debug=1 but there seems to be no intention to backport this to 18.0).


Desired behavior after PR is merged:
- Add a new column to print the line amount in the company's currency if the invoice has a different currency than the company.
- Print tax excluded/include amount based on company's setting.

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

Forward-Port-Of: odoo/odoo#211158

## Description of the issue/feature this PR addresses: This PR is about fixing this issue: https://github.com/odoo/odoo/issues/182777 to avoid SMTPServerDisconnected ## Current behavior before PR: With some race condition got SMTPServerDisconnected ## Desired behavior after PR is merged: Do not get SMTPServerDisconnected while quitting non connect session and avoid to get non connected session using google oauth2 connection. --- I confirm I have signed the CLA and read the P

## Description of the issue/feature this PR addresses:

This PR is about fixing this issue: https://github.com/odoo/odoo/issues/182777 to avoid SMTPServerDisconnected

## Current behavior before PR:

With some race condition got SMTPServerDisconnected

## Desired behavior after PR is merged:
Do not get SMTPServerDisconnected while quitting non connect session and avoid to get non connected session using google oauth2 connection.



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

Forward-Port-Of: odoo/odoo#182817

Steps to reproduce =================== 1. Install l10n_pe or l10n_se 2. Switch to the newly installed company. 3. Open the contact form. The address fields are misaligned. Technical ========== With commit https://github.com/odoo/odoo/commit/4dd27bba346e50f40769d1412fbca0b5f65bb5a6, the contact form renders address fields dynamically based on the selected country. The `_view_get_address` method in the `format.address.mixin` replaces the default address `div` with the XML arch of the vi

Steps to reproduce
===================
1. Install l10n_pe or l10n_se
2. Switch to the newly installed company.
3. Open the contact form. The address fields are misaligned.

Technical
==========
With commit https://github.com/odoo/odoo/commit/4dd27bba346e50f40769d1412fbca0b5f65bb5a6, the contact form renders address fields dynamically based on
the selected country. The `_view_get_address` method in the `format.address.mixin`
replaces the default address `div` with the XML arch of the view linked in the
current company's `address_view_id` field. Since this arch is wrapped within the
`<form>` tags, the JS framework adds an extra div element and `o_form_nosheet` class,
causing layout misalignment.

After this commit
==============
This commit only includes address `div` element inside the `<form>` tag.

Task-4744412

Forward-Port-Of: odoo/odoo#208965

[FIX] website: update sitemap lastmod on website page view changes Before this commit, since the introduction of the website page model at commit [1], the lastmod for pages indicated in the sitemap was not entirely accurate: it only considered *page record* changes, not their internal *view changes*. Steps to reproduce: - Create a new website page and publish it - Go to /sitemap.xml, see the page is mentioned with correct lastmod - Wait for one day ** - Update the page URL - Go to

[FIX] website: update sitemap lastmod on website page view changes

Before this commit, since the introduction of the website page model at
commit [1], the lastmod for pages indicated in the sitemap was not
entirely accurate: it only considered *page record* changes, not their
internal *view changes*.

Steps to reproduce:
- Create a new website page and publish it
- Go to /sitemap.xml, see the page is mentioned with correct lastmod
- Wait for one day **
- Update the page URL
- Go to /sitemap.xml, see the lastmod was updated
- Wait for one day **
- Update the page content
- Go to /sitemap.xml
=> The lastmod was unchanged

**: the lastmod does not show the hours. You will need to update the
    write_date manually in your database to test this. Also, when
    visiting the sitemap, you need to first delete the cached version
    in the backend (Debug -> Settings -> Technical -> Attachments).

[1]: https://github.com/odoo/odoo/commit/4ecbacaf59576a22ff45615a5aa5c67244e4fb93

Forward-Port-Of: odoo/odoo#211749

Description of the issue/feature this PR addresses: Cash control is a basic operation in a point of sale and it shouldn't require permissions as big as Accounting/Billing to be performed Current behavior before PR: - A Point of Sale user with no Accounting/Billing permission can't do cash operations. Desired behavior after PR is merged: - Recover the paradigm present in versions <=v15: a pos user can record a cash in / out operation without the need of elevated permissions. TT5

Description of the issue/feature this PR addresses:

Cash control is a basic operation in a point of sale and it shouldn't require permissions as big as Accounting/Billing to be performed

Current behavior before PR:

- A Point of Sale user with no Accounting/Billing permission can't do cash operations.

Desired behavior after PR is merged:

- Recover the paradigm present in versions <=v15: a pos user can record a cash in / out operation without the need of elevated permissions.

TT51987 cc @Tecnativa


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

Forward-Port-Of: odoo/odoo#188798

After a recent change in German EDI, the data exported in CSV from the EC Sales List can no longer be uploaded because the expected structure has changed Steps to reproduce (with a DE Company): - Make an invoice to an EU Partner - Open EC Sales List - Export CSV When uploading the file on the Elster portal it will be rejected with an explicit error message, saying that we're using an old CSV format now deprecated, and prompts the user to refer to the new specifications Original mes

After a recent change in German EDI, the data exported in CSV from the EC Sales List
can no longer be uploaded because the expected structure has changed

Steps to reproduce (with a DE Company):
- Make an invoice to an EU Partner
- Open EC Sales List
- Export CSV

When uploading the file on the Elster portal it will be rejected with an explicit error message,
saying that we're using an old CSV format now deprecated, and prompts the user to refer to the new specifications

Original message:
Ihre CSV-Datei wurde für eine ältere Version der CSV-Schnittstelle erstellt.
Bitte informieren Sie sich in der Versionstabelle der Importhilfe über die aktuellste Version der Schnittstelle sowie Änderungen.
Sind die Versionsangaben korrekt, prüfen Sie bitte das Encoding Ihrer CSV-Datei. Das zulässige Encoding ist UTF-8.

Sources:
https://www.elster.de/eportal/helpGlobal?themaGlobal=zmdo_import_eop
https://www.datev-community.de/t5/Betriebliches-Rechnungswesen/Import-CSV-Daten-nacvh-Elster-f%C3%BCr-ZM/td-p/480079

opw-4751667
opw-4674533

Forward-Port-Of: odoo/enterprise#85992