…ke lock date into account

If we have a payment in october and a statement in november and the lock date is 1st november, we can't reconcile both because we try to write statement_id on payment but there is the lockdate constraint. This is not correct and we should be able to reconcile both even after lock date as it is the case for other moves.

As portal users do not have access to activities it makes sense to
limit access to the various activity_* fields to employees only.

Purpose
=======

This chunk of code was badly converted in P3 on https://github.com/odoo/odoo/commit/01e35141479b8dfc4a390518f89fc52e7cec5396#diff-6ad3d62d2147f2fef519473f2576b459R94

Use `ir.default` for default taxes. Stop using `ir.config_parameter`.

Fixes #18943
opw-778010

Incomprehensibly broken with
https://github.com/odoo/odoo/commit/19b126210934bb3c8134f6f33417bd45104f4ecc?w=1#diff-caf4f49644744b1b91211fd12223dbd2R327

When a snippet is dropped into a page, all its animations are started.
The problem was that all its children's animations have to be started
and that was not the case anymore since recent big website refactoring.

Fortunately, this allows to improve and optimize animations start
function: now all animations are (re)started for a portion of a
given DOM (default to #wrapwrap) while it was only possible to
restart animation of a given DOM *element* before.

This commit closes #14058

This commit closes #20722

Update screenshot for v11

Give examples of Do/Don't

At this step, Order is not always confirmed

Without this patch, the user will see a button 'create a new page' on the 404
for the controller /event/<event_id>/page/<page>

Get the decoded body from requests (rather than the encoded one) and
process it as text throughput.

Fixes #21156

This commit closes #20836

Courtesy of @sswapnesh for help

Courtesy of Visti Kristensen, IT-konsulent

Closes #21034

Before this commit:
1. If user wrote text in the quantity field to add to his cart, it would crash
and show a server error.

Now, if the user insert a non-valid quantity in the field, we set it to 1

Step to reproduce:
With website_sale only
  - Go to a product page on the shop
  - Insert 'abc' in the quantity field and click 'Add to Cart'
  - Server will throw an error 'Can't parse float..'
With website_sale_options
  - Go to a product page on the shop
  - Insert 'abc' in the quantity field and click 'Add to Cart'
  - Popup confirmation with optional product will show with 'NaN' in the qty
  - Click 'Proceed to checkout'
  - Server will throw an error 'Can't parse int..'

2. On the checkout, if user typed text in qty field it would create infinite
quotations.
Some modules (eg: website_event_sale) would hide this behavior because they
override the RPC call to '/shop/cart/update_json' and throw an error on the
RPC.

Now, if user type incorrect integer quantity, we set the quantity to 1.

Step to reproduce:
1. On base (website_sale only)
  - Add an item to your cart
  - On checkout page, set qty to 'abcd' or whatever text
  - Check your browser console, every 500ms their will be a RPC call
  - Check your quotations in backend, their will be a new one every 500ms
2. On db-all
  - Add an item to your cart
  - Set qty to 'abcd' or whatever text
  - Check your browser console, it will throw an error on the second call

This closes #20482, closes #20904

courtesy from rlizana  

It's needed in phantomjs tests.

Without this commit it printed only error stack, which doesn't provide enough
information to fix it. This is a problem when the error is not reproduced on
running tours manually in browser.

Button to create new opp are reserved to graded partner.
Employees will use backend crm, and classis portal user cannot create lead for them.

+ fix 403 when create an opp because no access on crm activities.

This opw fixes #21222

[FIX] l10n_ch: only compute postal reference with sanitized number if no iban reference on the account

Before this revision, it was not possible to display a chatter inside a <sheet>.

As the chatter is reused (when switching in edit, records, etc.), it is detached
(to keep its handlers) before updating the form $el.

The problem here is that the chatter was detached in `_updateView` from
`$form.contents()` where the chatter is a root element ; when setting the form
view html, the chatter was thus still present. This was thus only working
correctly if the chatter was a direct child of <form>.

To keep it displayed in all cases, we now detach it at the chatter node
rendering.

Closes #20032

When launching in an empty db the following command:

 ./odoo-bin --addons-path=../enterprise/,addons --db-filter=11ent -d 11ent -i sale_timesheet --test-enable --stop-after-init

it raised a traceback because no sale journal was defined.

opw:783489

`_check_lock_date` is defined on a `account.move`, while in this case
`move` refers to a `stock.move`.

We re-implement a logic similar to the original commit 287b2932.

Fixes #20913
opw-782395

Closes #21234

Done at #21234

related to rev 0d19ee98

It was broken following the refactoring done in saas16, resulting in
barcodes being handled on all the displayed forms and it was problematic
in the case of a form dialog openned over a "fullscreen" form view.

This was particularily problematic for the scrap dialog in the
stock_barcode module.