The product_id field is not required on a mrp.bom (while product_tmpl_id is). When searching for BOMs linked to a product.product, we should display the one specific to this product and the ones linked to the template (but not linked to another variant).

scheduler_cron_id was not initialised so the scheduler always crashed (with just info message)

Closes #1536

Fixes an error introduced in f6fb2b69

If any missing or partially incorrect values cause
an exception other than a psycopg2 error, we should
still catch it, rollback that record and report
the error, rather than letting bubble and fail
without any feedback to the user.

Fixes #1485

[FIX] account: res.partner: limit access to "total_invoiced" field to group "group_account_invoice". Use SUPERUSER_ID to access data

[FIX] calendar: onchange_dates: protect against void dates (for example when creating a meeting through the form view)

When we compute the discount of a product to display (result of product_id_change), we compare prices in the currency of the product while we expect prices in the currency of the pricelist. opw 606188

When a record is created, the magic fields (id, create_date,...) are first removed from the vals as the user should not set a value for these.
However if a value for this is given in default value (e.g. defined in an ir.value), the creation would crash (sql error : column specified more than once) as the magic column would be added again.

In some rare cases database records have negative IDs,
so the slug URL could look like /foo--20. This could
be mistaken for a slug ending with a `-` and a positive ID.
The latter is not supposed to happned as final hyphens
are stripped by slugify, but has been used in the past
and may be used in old links.

Same behavior than in saas-5

It was not possible to subscribe again to a mailing list once unsubscribed

These parameters are (or should be) irrelevant for
a search_count(), and they could actually break the
result or make it significantly slower (e.g applying
`order` on large tables).
This fixes a performance regression introduced by
0f43032b.

We could also raise an error offset/limit are
passed in combination with count, but that seems
unnecessary.

Also switched to "SELECT count(1)" for the count
query, as it is simpler and just as fast.
We'd get the same perf with * or any constant value,
as in "SELECT count('me in')", but let's keep it
simple ;-)

Will fix problem where opened dropdown list were hidden behind the modal footer

[FIX] mass_mailing: allow to add a user/email to a specific mailing list and not always the last as previously.

Otherwise all templates are displayed and this will lead to some issues.

Also added a description on event.registration, because currently its
displayed name is Email Thread.

There is no reason to propagate the context in those buttons.

Besides, it leads to issues concerning the email template, rendering the wrong res_id because the active_id was wrongly propagated

Same as for rev 4bad513d, the references were not correctly parsed, added missing regex

and without spaces for vat

tooltip stuck visible should be removed on click + remove tooltip container except for modal in order to prevent them for staying visible in some rare occasion

Sometimes, when you send an email in the chatter, a pop-up is displayed to fill the partner details
This case happens when the email address you send the email is not associated to an existing partner
In such cases, in lead, we use the company name and contact name to fill the partner name