The problem was that mentions weren't correctly erased with DELETE key (in some
conditions), or when replacing mention text. When this happened, the mention
didn't appear in the message, but the message was even tough sent to the erased
mentioned people.

With this rev., we don't try to detect erasing on the fly anymore, but we
rather validate mentions before sending the message with the content of the
input.

opw 669362

In the report model `im_livechat.report.channel`,
The `session_name` field no longer exists. It has been
replaced by `technical_name` instead, labelled
`code`.

opw-669443

When a shipping/invoice contact is created, the picture with the truck/dollar must
be used. Inspired from 66d4de7a

When a product template has several variants, the fields volume, weight and
standard price don't have be displayed in the prodcut template form view.

opw:669240

Missing from previous commit 50382418

A SO line with an ordered qty less or equal to the sum of all the quantity
linked to its procurement must be ignored. In this way, when a SO line has
an Ordered Qty equal to 0 in a SO, all the other lines can be processed like
in 8.0

opw:669200

`write` expects a `dict` for the `values` argument,
`part[record.id]` is a list of commands to add new
followers.

See the returned variable `specific` of the method
`_add_follower_command` in `mail_followers.py`.

Surrounding `part[record.id]` with a `dict` with
`message_follower_ids` has probably been
forgotten by oversight.

`gen` and `part[record.id]` have actualy the same
syntax, and the `write` done with these variables
should therefore be called the same way.

opw-669376

When the user can't read the model res.partner, former code tried to determine
whether or not the user was follower of the document. This was wrong for three
reasons.

First, it performed an RPC to get the partner_id of the current user, but this
info is already stored in the session so the RPC was useless.
Second, the partner_id isn't helpful to know if the user is a follower because
everything we have is the follower_ids, which aren't ids of the res_partner
model, but ids of the mail_follower model (compare apples and oranges...).
Third, we anyway didn't use that information at all as the button indicating
whether or not the user is a follower wasn't displayed.

This rev. simply removes that useless RPC and only displays the count of
followers as previously.

The email link in the opportunities help message
was built as:
`<a href="mailto:info">odoo.com</a>`
instead of:
`<a href="mailto:info@odoo.com">info@odoo.com</a>`

opw-669361

This reverts commit 33755f18.

note: revert for now since some scenarios were not taken into account,
detached event could have been moved to another day.

In 22051dcc, the sidebar contacts of the calendar were ordered, this does
it in another way to solve several issues when selecting filters.

When editing a recurring event clicking `Update only this instance`
allow us to detach this event from the recurring sequence, but without
clicking it there are instances where the event will still be detached
maybe unexpectedly.

Clicking on it will create an event which shadow the recurring one that
being done thanks to:

- recurring_id: the id of the recurring event creating this event
- recurring_id_date: start of the virtual event this new event shadows

Before this commit: when the start or end date of an recurring event is
changed, all modification are not applied on the recurring events but
only the current virtual event occurrence is detached and modified.

After this commit:

- when the end date of a recurring event is modified, it is modified for
  all the instance (not detached) of the recurring event,

- when the start date of a recurring event is modified, it is modified
  all the instance (not detached) of the reccuring event and if:

  * one occurrence of the recurring event is still on a (not-moved)
    detached event of this recurrence, this virtual event will be
    shadowed.

  * a detached event has now no occurrence of the recurring event on its
    day, it will still be left untouched but will now not shadow an
    event anymore.

eg.

we start with recurring event A on 4, 5, 6 => we see [4: A, 5: A, 6: A]

-> detach event on 5 calling it B => we see [4: A, 5: B, 6: C]
-> change start of recurrence to 5 => we see [5:B, 6:A, 7: A]
-> change start of recurrence to 7 => we see [5:B, 7:A, 8: A, 9:A]
-> delete detached event B on 5 => we see [7:A, 8: A, 9:A]
-> change start of recurrence to 3 => we see [3:A, 4: A]

closes #10873
fixes #10278
opw-665700

- swap reply-to and mark-as-unread buttons in threads
- remove blockquote from stripped html in channel previews
- readd padding to no-content message in threads, also to no match found
  message
- add 1 to chat window z-index to prevent control panel buttons to show
  through it

Force the values of `res_id` and `res_model` when creating assets
attachments. This avoid getting wrong default values from the context.

When using the mail composer with a automatically created report (like
when sending a quotation by email), if the report asset must be saved,
the context used is the one from the mail composer, which contains a
`default_res_id` entry.

When a product with costing method = standard price and inventory valuation = perpetual (automated),
the button "Set standard price" in General information in  "product.template" is shown if the
product template has only one variant. In the other case, the button is displayed in the variant
view form.

opw:668568

The customer address must be the shipping address defined on the SO.
The contact address can be removed from the report because the object
passed to the report is the stock.picking where the partner_id is the
one linked to the shipping contact.

opw:669015

opw-669266

The section_id field has been renamed to team_id in 9.0. Moreover,
the Sales Team group by is already present in the view from which
this one was inheriting, resulting in duplicated group by's.

Before the fix dda8e221, the duplicate
records were erased thanks to the index used in the dictionary(id of the partner).
After this fix, to avoid this this problem, the label of each record is used as
key in the dictionary.

Return 404 for seo when profile is private.

The value validation was de facto nullified by escaping invalid translations in
`XMLTranslator.process_text`.  Reimplement it by checking whether the
translated term can be translated back to its source term in the field value.
The sanitization of translated terms is now gone, as not all terms should be
sanitized (like attribute values).

Do not parse the translation of an attribute value.  The content of a
translatable node attribute (such as 'string') should not be tested for
XML/HTML validity: the value can contain special chars such as `&` in its
source and should not be escaped when evaluated.

This fixes escaped page title in the partner form
`Sales & Purchases` => `Ventes & Achats`

In Odoo 9.0, the field `company_id` has been moved
from the `res.currency` model to the `res.currency.rate`
model.

The different reports applying the currency rates on the amount
at date have not been updated according to this change. This
includes the sales, purchases and invoices analysis report.

Basically, before 9.0, there was one `res.currency`
per existing currency per company. A simple `JOIN`
on the `res_currency` table was therefore enough
to apply the currency rate.

From 9.0, the currency records are shared between
companies. It's the rates (`res.currency.rate`) that can be
set a on specific company. The simple `JOIN` on
`res_currency` is therefore no longer enough: the company condition
must be added. Only rates from the specific company
(e.g the company of the invoice) must be considered, or rates
without companies.

We take the opportunity to factor out the method, so, if a correction
must be done, it must be done in one place only.

opw-669129

A UserError must be sent if the delivery method set on the delivery order
has no redirect on courier provider's website.

opw:668960

Users are tempted to enable all features they
see under the former "Speed" section of the
website settings, even if they have no idea
what they do.
One of them was `CDN Base URL` and had a default
value that was wrong and very likely to break
your website if enabled by mistake.

This commit replaces the default value with
a placeholder that looks more like a `sample`
URL, and makes the fields required when the
CDN option is enabled.

It also moves the whole "Speed" options to
technical features / debug mode.

The checkbox `Assets management & Revenue recognition`
actually installs only the assets management. The revenue
recognition is not installed when checking this box.

Actually, the revenue recognition is not even
available within the community edition. This box
couldn't therefore possibly install this module.

opw-669093

On printing, the announcement bar URL was displayed
in the printing result.
e.g.
`https://services.openerp.com/openerp-enterprise/ab/register/...`
was displayed at the top of the print.

This is related to the revision 50a4ca31.

This is due to this simple typo, the according CSS rule was
never applied because of it.

This reverts commit 50a4ca31.
This causes retro-compatibility issues if you do not
update the `assets_backend` qweb views.

Closes #10853

Add a dummy 'match_rules()' function for backward-compatibility of commit
d8605b79, as 'match_rules()' was called from  server-side 'im_livechat.loader'
template.

The POSBox attempts to maintain whatever Wi-Fi connection it has as best
it can. When it loses it's current Wi-Fi connection it will attempt
to recreate it every 30 seconds. This works well, but a side-effect of
this is that it'll also print a 'Could not connect to LAN' ticket every
time it fails. If you where to leave the POSBox with Wi-Fi on for an
extended period of time you could return to a lot of 'Could not connect
to LAN' tickets.

This makes it so that the 'Could not connect to LAN' ticket only gets
printed once upon connection loss. Although it would be simpler to just
not print this ticket at all when losing connection, it is very useful
to know when the POSBox has lost connection. Otherwise when it loses
connection it would stop working and noone would know why.

This bar was never displayed as the remote css was always empty.

When using the enterprise web client, the printing stylesheet show the
target of links (<a> tags) between parentheses, including the one from
the annoucement bar that should be kept hidden.