If the user somewhat removes the 'Applicable Code' text, the call to
`safe_eval` will crash.

opw-769267

Correct rendering of 70 and 90 in french
And manage inversion [unit]-en-[tens] in nl

opw 757048

closes #19297

- Set the TZ as 'America/Martinique'
- In the calendar (month view), click on a date D.
- Fill in the topic, then click on "Edit"

The date is set to D-1.

Commit 09066fbb makes the date consistent when the user sets an
event as an all day event by taking into account the appropriate
timezone.

However, in the case of an event created from the month view, this TZ
modification should not be applied.

opw-766638

Before this commit, we could temporarily change cashier from A to B, and back to A seamlessly just by refreshing the page.
This could be a security issue for a cashier is held responsible for its sales.

This commit stores the cashier in localstorage, and with the right sets of methods, corrects the issue.

OPW 767827

closes #19207

The default size limits set in base.sql are eventually superseded by the
actual limits (or absence of) when the DB schema is synchronized with
the Python model definitions.

However the list of modules (name, authors, descriptions, dependencies)
is loaded before this can happen. The length of the author field is one
case that can easily crash the database bootstrap process at that point,
should a module with a long author name be present in the addons path.

After schema sync, that size limit is lifted entirely (although Odoo Apps
does limit the max author name length to 512 at the moment, to prevent
abuse).

Fixes #5850

Closes #19231

Before this commit, a message received through the contact us form did create a Lead, but any notification was impossible (even if a user was a follower of the relevant sales team.
This was because the default sales team is integrated in the values for create in models.py, which mail_thread can't see, but needs in order to notify

This commit corrects the behavior which now converge with standard lead creation by adding the default sales_team earlier in the values for create

OPW 762651

closes #19180

Backport of commit c00267bc

opw-767538

task: https://www.odoo.com/web#id=22700&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PR: #19064 

task: https://www.odoo.com/web#id=22558&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PR: #19102 

task: https://www.odoo.com/web#id=22600&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PR: #19099 

task: https://www.odoo.com/web#id=22598&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PR: #19101 

task: https://www.odoo.com/web#id=22597&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720

PR: #19104 

Before this commit, when the amount of rows was above xls format threshold (>65535), the xlwt library threw an obscure Traceback to the user.

We now test the amount of rows before even calling the library, raising a more helpful message to the user

OPW 767319

closes #19035

Make it easier to add taxes in odoo by using one tag per tax grid.

task: https://www.odoo.com/web#id=22696&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PR: #19103 

A tax can be mapped to nothing, so first check if
_map_tax_fiscal_position actually returned something.

Fixes #17963

In the reconciliation widget, create a counterpart line. No domain is
applied on the "Account" field regarding the company, meaning that we
can select an account from any company.

opw-694149

Done at #19025

When refunding an invoice with the option: "Cancel: create refund and reconcile",
it raised a warning: "You are trying to reconcile some entries that are already reconciled!"
because in some cases the refund is linked to several entries which match the same
account of the invoice. So it tried to reconcile several times the same entries.

opw:765673

The action was tagged multi but crashed if executed on more than one order.
Courtesy of Andrius Laukavičius

Allows removing default taxes. It was supposed to solve PR 11498, but
the solution brings more problems than the original issue.

opw-766720

Closes #18852

Do not remove fields from models except for custom fields.  Removing a base
field from a model screws up the model cache: that field may be required to
speed up the setup of the model in another registry.

Otherwise if payment is before lock date, user will get an error as he can't change the move value before lock date.

If a google application has no client_id or client_secret during the update
process (e.g. was configured but the API keys have been removed and the tokens
have expired), the method will crash.

Instead of continuously try and produce a traceback, return a proper error message

Closes #18613
Closes #18614

Before 9.0, it was possible to display aggregate values in grouped
Kanban view (like sum, average...). The aggregate was displayed in
the header of the column (see for example in 8.0 in Project >
Tasks).

This feature has been dropped in 9.0 because it didn't work
correctly, but the documentation hasn't been updated accordingly.

Before this commit there were two issues:
- The date "from and to" set in the wizard weren't working, as in not used at all
- The lines in the report did not have a date range, making the understanding of the report difficult

after this commit, only the budget lines which dates overlap at least one day of the report's dates will be selected.
Also, the first line of the report, containing the budget name also contains the dates on which it applies

OPW 743441

Closes #18737