As the unit of measure is displayed it makes sense to display the quantity too.
Closes #13703

Closes #13680

These data should be in no update. Else at next update, it can change the configuration
of the production.

This commit closes #13404
Courtesy of @bealdav

Since Chrome 53.0.2785, the input select is hover the existing tag.
With this fix, the existing tag are displayed at the right side of
the input to create a new one.

This commit closes #13655

Courtesy of @8cells

When a user registers for an event on the front-end, the confirmation of
the associated SO will also confirm the registration. However, if a SO
is created manually and a ticket event is added to it, the confirmation
of the SO will not trigger the confirmation of the registration.

In the second case, the registration simply doesn't exist yet at
confirmation and is created by the method `default_get` of
`registration.editor`.

We make sure to confirm these registration when we make the final
reservation.

opw-688665

* Clich -> Click
* Yoru -> Your

In a multi-company environment, we need to make sure to copy the company
of the PO to the company of the picking. Otherwise, it might happen than
the PO as a different company than the picking.

Closes #13129

closes #13693

If a model uses nested sets to maintain a hierarchical record
ordering, then bulk inserts (e.g. via a CSV import) are likely to
suffer from an O(n^2) performance penalty, since there is a high
chance that each new record will require many of the existing records'
parent_left and parent_right fields to be updated.

The context parameter 'defer_parent_store_computation' may be passed
to the load() method, in order to defer updating the parent_left and
parent_right fields until after the bulk operation is complete.  This
appears to have last been fully supported in version 7 (via the old
import_data() method).

It is still possible to specify 'defer_parent_store_computation',
e.g. via an XML-RPC call such as

  m.execute_kw(dbname, uid, password, 'stock.location', 'load', [],
               {'fields': fields, 'data': data,
                'context': {'defer_parent_store_computation': True}})

This will currently defer the recalculation of parent_left and
parent_right, but does not correctly call _parent_store_compute()
after the bulk operation is complete.

Add the missing call to _parent_store_compute() to perform a one-time
update of the parent_left and parent_right fields if needed after the
import operation is complete.

Also fix the child_of_domain() and parent_of_domain() expression
methods, so that the 'child_of' and 'parent_of' operators give correct
answers when updates to parent_left and parent_right have been
deferred.

Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>

Closes #13688 (part 2/2)

The expression context is currently passed to to_ids() but is missing
from all calls to child_of_domain() or parent_of_domain().  These
methods are effectively always passed a context of None.

Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>

Closes #13688 (part 1/2)

Bulk inserts of product definitions (e.g. via a CSV import) will
suffer from an O(n^2) performance penalty due to an unfortunate cache
invalidation bug.  The underlying cause is difficult to determine due
to the labyrinthine nature of the relationship between product.product
and product.template, but some key elements are:

- The "product_variant_count" field is a non-stored computed field,
  and so gets invalidated by the call to recs.modified(upd_todo) in
  BaseModel.create()

- Field.determine_value() will call _prefetch_field() to repopulate
  "product_variant_count" by refetching all records from the database,
  despite the fact that "product_variant_count" is not stored in the
  database.

Using the length of "product_variant_ids" directly (instead of going
via "product_variant_count") seems to avoid this problem, possibly
because the definition of "product_variant_ids" conveys more
information about the circumstances in which its value must be
invalidated.

An alternative solution of making product_variant_count a stored field
(using the same trigger as for other variant-derived fields such as
volume and weight) works but still results in some unnecessary fetches
and invalidations.

Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>

Closes #13689

Documentation to help developers use the following classes:
- utm.mixin
- rating.mixin
- website.published.mixin
- website.seo.metadata
- mail.thread
- mail.alias.mixin

After careful consideration, the ir.needaction.mixin was
not included in this doc page since it is no longer displayed
anywhere and will be dropped quite soon.

The options table displays the following columns:
Product name | Description | Price
while the pricing table ommits this first column. This is quite a
good idea as products are not always accessible to portal/public
users depending on what modules are installed (notably website_sale
which introduce the published/unpublished record rule on products).

To avoid introducing an extra-sudo simply for display reasons,
this commit simply remove the product name column and harmonizes
the options display with the main pricing display.

Somehow in the migration to the new api, it was decided that the
acquirers would be browser as sudo only for token access. This caused
portal users to have a crash when trying to view their quotation since
some fields from acquirers are set the specific groups for security.

This commit reintroduces the old behaviour, which was to browse as
SUPERUSER in all cases for the rendering of the buttons.

`customer_email_data` can be undefined.
It must therefore be checked before testing
its length

e.g. use the /helpdesk command with an anonymous visitor
of the livechat

opw-690301

Change color #a24689 to #875A7B

Commit https://github.com/odoo/enterprise/commit/8ac1c19fac7615fecd51e670f798d13158a4e53c
changed the odoo interface violet by changing the main LESS variable
but forgot there was many direct occurences in XML/HTML/... (for
example for the mobile browser color).

Even if it's community the odoo interface violet is used at many places
(module description, XML demo data, ...).

A customer can confirm a quotation only once `website_quote` is
installed. Without it, this isn't possible, and by default
this is not installed with the installation of the `sale` module.

Courtesy of fgi@odoo.com.

Commit 48a1eaf7 adapt the welcome
message on website so that it fits the page height. But this does
only worked for large screens as the height was forced to main
height... which is smaller than the default welcome message height
on small screen. The fix only had to use min-height instead of height.

Commit 5f980404 in saas-12 changed
some "saved" event to "save" event but forgot to adapt new features
which depend on this in 10.0 after forward port.

The blog_cover JS code is only available on blog pages. So the option
can only be activated on blog pages (which was not the case if the
snippet latest post was used on a random page).

Animation preview on images did not work as the web_editor stopped
every potential animation when an image entered edition. As the
behavior does not seem useful as there is no infinite animation which
is possible with standard odoo (and even if it was the case, it would
not be too strange that the animation continues), the feature is
removed with this commit.

Since commit 8ac1c19fac7615fecd51e670f798d13158a4e53c the odoo brand primary color
changed, which also changed the color of tips. The problem
was that they lose a lot of contrast in the appswitcher.

[IMP] account: It is better to order also by 'id', esp. when 'sequence' could match among multiple records.

In saas-12 and up, upstream_dependencies returns:

- when called from old API : a list of ir.module.module ids
- when called from new API : a recordset of ir.module.module

From 9.0 to saas-11, when called from new API it would also returns a
list of ids which can bring needless inconsistencies.

With this commit when called from new API a recordset is returned.

opw-690015

Neither the super-user nor the sudo() mode should need
to use read_group() on any of the private user fields.
So we can simplify the code and remove this special case.

The same is not true for read(), though.