**Steps to reproduce:**
- Open "Configure Document Layout" in settings.
- Add only an image in the company_details section.

**Issue:**

- The customer added only an image to company_details in their production version 15.2. However, after migrating to version 17, the image appears in company_details but does not show up in the document preview. In version 15.2, there were some changes to company details that caused this issue https://github.com/odoo/odoo/pull/122438. 
- Due to these changes, company_details is processed with the html2plaintext() function, which removes all the tags from company_details and only links and text will remain.
- This function does not recognize the image element and removes it along with other elements. I have prepared a fix that recognizes the image element from company_details and prevents it from getting discarded.
- Video reference from RunBot version 17: https://drive.google.com/file/d/1Ml62xIV1mhwKwU8KRHdc-qfTFCZhEqY0/view?usp=sharing
- I have also added a test case for html2plaintext function in test_html2plaintext function by backporting this method from 
master.

OPW : [3945490](https://www.odoo.com/odoo/my-tasks/3945490?cids=2)

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

Forward-Port-Of: odoo/odoo#171440
Forward-Port-Of: odoo/odoo#169027

When the grid mode was added in commit [1], the "Padding" grid option was impacting all the grid items at the same time. This was not looking good in the "Masonry" snippet, because the images would have the same padding as the text grid items, while it would look better if they could take the whole space. The padding was therefore forced to 0 px for this snippet images (see commit [2]), preventing this option from having an impact on them.

However, the "Padding" option was improved in commit [3], allowing the padding to be set on the grid items individually. There is therefore no need to block this option for the "Masonry" images anymore.

This commit removes the CSS rules preventing the "Padding" option from being applied on "Masonry" images. Note that the default padding is still set to 0 px, as it looks better, but it can now be modified with the option. Also note that the CSS rule about not showing the padding highlights was not working, as it was forgotten and not adapted when doing commit [3].

[1]: https://github.com/odoo/odoo/commit/cc406afcea7bf5846233a9f97a4a8ac5f618f3ec
[2]: https://github.com/odoo/odoo/commit/85b352af319edec84407f2046cf795b4e5503460
[3]: https://github.com/odoo/odoo/commit/11418cc6f0afcc8e14869f4f38ae0d6d462ac712

task-3970022

Forward-Port-Of: odoo/odoo#168013

Problem:
For an Italian public company, when sending an invoice there is no warning triggered when the field "Origin Document Type" is empty

Steps to reproduce:
- Install "Contacts" and "Accounting" apps
- Create an Italian company and set its fiscal localization
- Create a new Italian contact and fill out the "Destination Code" with a six-digit code
- Create an invoice for this contact, in the "Electronic Invoicing" tab, leave the field "Origin Document Type" empty
- Confirm the invoice and click on "Send & Print", there is no warning saying that the field "Origin Document Type" must be filled out

Cause:
Errors in the conditions

Note:
Modification in the get_records_action because self.id returns an id of type NewId which raise an error (see below) in this fix workflow because it is called in an onchange function. self.ids[0] returns an id of type int

Error raised: TypeError: Object of type NewId is not JSON serializable

Steps to reproduce:
- Do the 4 first steps as above
- Create a second invoice with another customer which is not a public italian administration (can be from another country)
- Select the invoices and click on "Send & Print" in the "Actions" button

opw-3844664

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

Forward-Port-Of: odoo/odoo#162776

This error occurs when the user drag & drop the newly created calendar event and select ``This and Following events`` in ``Edit Recurrent event``

Steps to reproduce:
- Install ``Calendar`` module
- Create a new event from the Calendar view
- Edit event -> Enable ``Recurrent``
- Now click on any day from ``Repeat on`` and remove the day which is selected by 
  default (eg: if Tuesday is the default then select Monday and unselect Tuesday)
- Save and Unarchive it and go back to the calendar view
- Now drag & drop the newly created event to anywhere and select 
  ``This and Following events`` in ``Edit Recurrent event``

Traceback: 
``ValueError: not enough values to unpack (expected 1, got 0)``

The error on line [1] occurs because ``recurrence_id`` is not found in ``self``. This issue stems from a change made in commit [2], where ``recurrency`` was set to ``True``. Consequently, when an event is archived, ``recurrency`` remains ``True``, but the event lacks a ``recurrence_id``. This absence of ``recurrence_id`` in ``self`` at line [1] triggers an error. However, before this commit, the expected behavior was that when an event is archived, ``recurrency`` should be set to ``False``.

This commit will fix the error by passing ``false`` for ``update_recurrence`` when ``recurrence_id`` is not present.

[1]: https://github.com/odoo/odoo/blob/d7cfef9c51461a595f3f46c7b91e5c56241d4af3/addons/calendar/models/calendar_event.py#L1196
[2]: https://github.com/odoo/odoo/commit/48e3f725a2506ca63336a131661542cacc6f1ab5

sentry-5462902179

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

Forward-Port-Of: odoo/odoo#169040

**Traceback:**
```python
('helpdesk.helpdesk_team_menu', 393, 'Helpdesk > Configuration > Helpdesk Teams', 559):
 Traceback (most recent call last):
   File "/tmp/tmpkjz256np/migrations/base/tests/test_mock_crawl.py", line 255, in crawl_menu
    self.mock_action(action_vals)
   File "/tmp/tmpkjz256np/migrations/base/tests/test_mock_crawl.py", line 412, in mock_action
    mock_method(model, view, fields_list, domain, group_by)
   File "/tmp/tmpkjz256np/migrations/base/tests/test_mock_crawl.py", line 441, in mock_view_form
    [data] = record.read(fields_list)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 3540, in read
    return self._read_format(fnames=fields, load=load)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 3751, in _read_format
    vals[name] = convert(record[name], record, use_display_name)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 6631, in __getitem__
    return self._fields[key].__get__(self, self.env.registry[self._name])
   File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 1207, in __get__
    self.compute_value(recs)
   File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 1389, in compute_value
    records._compute_field_value(self)
   File "/home/odoo/src/odoo/17.0/addons/mail/models/mail_thread.py", line 424, in _compute_field_value
    return super()._compute_field_value(field)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 4875, in _compute_field_value
    fields.determine(field.compute, self)
   File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 102, in determine
    return needle(*args)
   File "/home/odoo/src/enterprise/17.0/helpdesk_timesheet/models/helpdesk_team.py", line 22, in _compute_total_timesheet_time
    [('helpdesk_ticket_id', 'in', helpdesk_timesheet_teams.ticket_ids.filtered(lambda x: not x.stage_id.fold).ids)],
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 6110, in filtered
    return self.browse([rec.id for rec in self if func(rec)])
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 6110, in <listcomp>
    return self.browse([rec.id for rec in self if func(rec)])
   File "/home/odoo/src/enterprise/17.0/helpdesk_timesheet/models/helpdesk_team.py", line 22, in <lambda>
    [('helpdesk_ticket_id', 'in', helpdesk_timesheet_teams.ticket_ids.filtered(lambda x: not x.stage_id.fold).ids)],
   File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 2907, in __get__
    return super().__get__(records, owner)
   File "/home/odoo/src/odoo/17.0/odoo/fields.py", line 1182, in __get__
    recs._fetch_field(self)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 3777, in _fetch_field
    self.fetch(fnames)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 3827, in fetch
    fetched = self._fetch_query(query, fields_to_fetch)
   File "/home/odoo/src/odoo/17.0/odoo/models.py", line 3920, in _fetch_query
    rows = self.env.cr.fetchall()
 MemoryError
```
**Summary of changes:**
Previously, the code `helpdesk_timesheet_teams.ticket_ids.filtered( lambda x: not x.stage_id.fold).ids)` generating O(n) queries leading to a memory error when dealing with large numbers of tickets (e.g., 60k+ for this customer).

This commit refactors the code to use the search method instead. this approach reduces the number of queries to O(1) and significantly improves performance for customers with a large number of helpdesk tickets.

UPG - [1776915](https://upgrade.odoo.com/web#id=1776915&cids=1&menu_id=107&action=150&model=upgrade.request&view_type=form)
TASK - [3995988](https://www.odoo.com/odoo/my-tasks/3995988?cids=2)

Forward-Port-Of: odoo/enterprise#65615

This commit's purpose is to disable the helpdesk ticket creation command when there are no teams available for the current connected user. Currently, using this command this way will create a new ticket without any team attached, rendering it useless.

step to reproduce:
- install helpdesk application
- open helpdesk
- open confifuration menu, select helpdesk team
- select 'customer care'
- activate the livechat option and saves
- leave helpdesk
- change from the current active company to any other company that doesn't have any helpdesk team with the livechat feature enabled
- open the discuss app and select the 'general' discussion
- type /helpdesk your_ticket a new ticket will be created without any team linked to it.

source of the issue:
when a team has the livechat option enable, the command is added to the livechat regardless of the connected user's access right to the team.

solution:
Only add the command to the list of livechat command if the user has access to at least one team with the livechat feature enable.

affected version : 15.0 - master
task - 3631682
https://www.odoo.com/web#id=3631682&menu_id=4720&cids=1&action=333&active_id=4105&model=project.task&view_type=form

Forward-Port-Of: odoo/enterprise#65137
Forward-Port-Of: odoo/enterprise#53510

This PR introduces a `l10n` test over the Balance Sheet reports.

Each Balance Sheet report in the `LOC_DATA` global at the head of the file will be tested.
The test generates a journal entry with a line in every account that is not `off_balance`.
It then checks whether the Balance Sheet is balanced.
The test does this both for debits and for credits.

The test will give a warning for any installed Balance Sheet report which is not specified in the LOC_DATA global. The aim is to change this to an error once all existing Balance Sheets are tested, to make this test mandatory for any new localizations.

For each localization with a Balance Sheet, the test needs to know the XMLIDs of:
- the CoA
- the Balance Sheet report
- the Total Assets line of the Balance Sheet
- the Total Liabilities line of the Balance Sheet
- the Total Equity line of the Balance Sheet (if applicable)

Setting the global `IDENTIFY_INCORRECT_ACCOUNTS` to `True` switches the behaviour of the test: it identifies the accounts that cause the imbalance using a binary search. This is off by default for runbot. 

**Performance impact**
- For each Balance Sheet, the test does the following:
     - load the chart template
     - create an account.move with 4 AMLs for each account (one debit and credit in the account; and one debit and credit in the counterpart account)
     - generate the report once.
- The Binary Search (which can be toggled when testing locally) is quite efficient: 
    - If there is just one incorrect account, then the report needs to be generated `log2(<number of accounts>)` times.
    - If there are `X` incorrect accounts, then in the worst-case the report may need to be generated `X * log2(<number of accounts>)` times.

On the Belgian CoA, with no incorrect accounts, the test takes 14s on my PC. With 4 incorrect accounts, the test takes 33s.

Task: 3060790

Forward-Port-Of: odoo/enterprise#65863
Forward-Port-Of: odoo/enterprise#36838

### Original issue:
When creating a debit note on a bill from a purchase order with the option 'copy_lines', the field 'Purchase Order' in the lines is not populated.

### Steps to reproduce:
- Install Purchase, Inventory apps and the l10n_co_edi module
- Switch to a Colombian company
- Go to Accounting > Configuration > Accounting > Journals
- In the Vendor Bill journal > Advanced Settings, uncheck the 'Electronic invoicing UBL 2.1 (Colombia)' option
- Go to Purchase > Orders > Purchase Orders, create a new one and confirm it
- 'Receive Products' and 'Validate'
- Go back to the Purchase order
- 'Create Bill' and 'Confirm'
- From actions, choose 'Debit Note'
- In the wizard, tick 'Copy Lines', select a 'Concepto Nota de Débito' and 'Create Debit Note'
- Display the Purchase Order field in the Invoice Line tab is visible, it should not be populated

### Cause:
This bug is due to another fix that have been badly made because no tests were there. Most of the content of enterprise/l10n_co_edi/wizards/account_debit_note.py:_prepare_default_values is not called when it is supposed to and called when it's not. 

In the 'Create Debit Note' wizard view there is an option to copy the lines and so, autopopulate them. This option is not displayed for Debit Notes generated from Credit Notes because the lines would be negative. 
(https://github.com/odoo/odoo/blob/47eff65afdba3a2a8283342d8b636657f1fac317/addons/account_debit_note/wizard/account_debit_note_view.xml#L16) 

The logic of this option is located in the module account_debit_note: https://github.com/odoo/odoo/blob/2a02ba4de1c823bcdef0e8b6b6373fa27b5587a1/addons/account_debit_note/wizard/account_debit_note.py#L64, the line_ids value is filled with a default value if copy_lines is False. If left empty, the lines are copied from the original account.move. 

In this commit, https://github.com/odoo/enterprise/commit/c738f14d4ac88d508b6b75747788f5867eb71a68 we are trying to manually populate the lines of a debit note when it is generated from a credit note. But the code is made so that the lines are always copied. 

So in this other commit https://github.com/odoo/enterprise/commit/fa65a1ff8cb7333a3339438513d1eeb5d5f9690e there is a correction to take the copy_lines into consideration. But it breaks the precedent fix as Debit Notes of Credit Notes always have copy_lines to False. So the code to copy the lines manually is actually never called for Debit Notes of Credit Notes (which is the only case we want it to be called in). But is called every time copy_lines is set to True therefore ignoring the actual code to copy the lines in the module account_debit_note. 

In the context of the bug of this PR, the problem comes from the manual copying of lines that is missing the value purchase_order_id.

### Solution:
Changing the logic of the _prepare_default_values function:
- if not a Colombian company or not a debit note of a credit note, stop here
       - we let the logic in account_debit_note copy the lines (or not) depending on copy_lines.
- if the debit note comes from a credit note, we copy the lines and return

With this flow, the lines will not be copied manually so the value purchase_order_id will be populated.

opw-3962301

Forward-Port-Of: odoo/enterprise#65528
Forward-Port-Of: odoo/enterprise#64689