In ff56304f a solution was tried to have message posted from
backend livechat linkified for visitor in frontend. This was
forward-ported when it should not have been and introduced issues
including:

- `href="{link}"` would become `href="<a href="{link}">{link}</a>"`

- if html entities such as the ones for U+00A0, and entities <, >,
  ', " or ` were next to the link, the entity would be linkified
  too (up to the ;)

This happen because utils.linkify function is to be used with text
content and not html which was the case in this instance.

opw-693457
opw-702410

This reverts commit 1c60a631.

The fix was done to conciliate 83956d4c and ff56304f but ff56304f was
forward-ported erroneously and introduced other issues.

opw-702410

This should only be accessible in debug mode, since it is already
possible to run the schedulers (with a simialr effect) manually.

When the user clicks on "Run Reordering Rules", it might create
procurements. However, the cron "Run mrp scheduler" will also create
procurements and might already be running in the background. Therefore,
we need to make sure that both actions don't run concurrently.

Note that the same check is done for the wizard "Run Schedulers".

opw-695607

The field resource_type in mrp.workcenter tree view must be invisible because
this field was not available in the form view before f9f4bba2

Adding resource_type in the form view had no business case.

opw:698183

Attachment should be visible in website chatter.
Due to a bad copy/paste, the attachments are hidden
when website_mail_channel is installed.

When the policy of the sale order is set to
`Deliver all products at once`,
the commitment date should be the maximum of the order lines lead time
rather than the minimum, as you will deliver all lines at the same time

It looks like the former behavior is applied since Odoo 7.0
d8d0b884

It should therefore actually be applied in 7.0/8.0/9.0,
but we consider the risk too high for databases
that are used to the former behavior, and expect the old behavior.

We therefore apply this revision only in 10.0, to minimize the risks.

opw-702271

- In a livechat window, type a URL, then end by a space. For example,
  type "https://odoo.com " (whithout quotes)
- Press enter

It is converted into "https://odoo.com ".

opw-702410

The depends for an issue inactivity_days expects a set create_date but
this may not be the case (when creating the record for example with the
field create_date in the form view).

opw-702532

Create a canned response containing the character "<". It is
automatically converted into "&lt;".

The substitution field is systematically escaped, for security reason.
This causes the substitution observed. However, the canned responses are
only used in text-only messages. The escaping is therefore not
necessary, since the HTML is not interpreted.

opw-693970

Simplifies the left margin calculation logic with a pre-defined width.
In practice, more use cases should be taken into account, and that could
just make the logic overkill.

opw-697626

In graph view, the y-axis always uses the standard float precision with
2 digits. This might not be enough if the precision was defined
differently for a given float type.

opw-697625

Done at #13888

Signed at #13976

Signed at #14010

Closes #14251

1;2802;0c
now() was bad as it excluded the orders of the latest session
midnight is not good either because
- midnight server != midnight user (timezone)
- some restaurant, bars start in the evening and finish after midgnight

With this default, with 4 sessions:
- POS A, start 2016-12-21 08:05:36
- POS B, start 2016-12-21 08:08:11
- POS A, start 2016-12-22 08:17:51
- POS B, start 2016-12-21 08:19:23

The default start date will be 2016-12-22 08:17:51 to include all orders of
both sessions.

When there are too many labels to display on the x-axis, they overlap
and it simply becomes unreadable. By slightly rotating them, this can be
avoided in most cases.

opw-697625
opw-697626

The dates were lost when in render_html as replaced by the one in the context
(None so fallback on today).

Avoid calling twice get_sale_details

Fixes #14789
Replaces and closes #14790

When MRP and Product Extended are installed:
- Define a manufactured product with valuation as 'Periodic (manual)'
- On the product form, click on "Compute from BOM"

Several issues:
- The field "Counter-Part Account" is mandatory
- Account moves are posted although the product valuation is 'Periodic
  (manual)'

The problem is that the wizard is originally used for products with
valuation 'Perpetual (automated)', where this behavior makes sense. In
this use case, however, it's an issue.

Making the field not mandatory is not possible without an upgrade of the
module, so this will have to be fixed in master branch. Regarding the
creation of account moves, however, this commit solves it.

opw-697867

This reverts commit 8416c2bc.

Temporary revert this commit, to have enterprise green again...
Need to replace 'full' args by key in context to don't break override
Need to rewrite account_bank_statement_import_csv from enterprise

Introduced at 11812b0b

Leftover references to cr, uid

The field resource_type must be displayed in mrp.workcenter form view

opw:698183

Before this commit, 'select all' into a list view, and use an action that assign
a user_id to all the records will send n² email, because the function send_mail
use active_domain instead of the current record.

Now, we keep mass_mail mode, but simulate the case where we have clicked on
each record one by one and not all the records matching the active_domain.
So we send only one email by record.

How to reproduce:
   create a action server "record.write(dict(user_id=env.user_id))"
   add this action in context menu
   select all records in a list and apply the action server

Before this commit, the parser (date, datetime, float, monetary, ...) was only
called on field from current model, and not on sub field.

Eg: product_id.price was not parsed as float, because product_id != float

This commit add an overiddable function to get all the parsers: get_parsers

This commit closes #14572

correct 3068afd8 .

_get_partner_pricelist could return both a recordset or an ID.
While the ORM handles both where the method is called, a migration script
relies on an ID being returned.
( migrations/sale_contract/9.saas~13.1.1/pre-models.py", line 24 )

This commit ensures an ID is being returned every time.

account 343112 should be 34312
account 343113 should be 34313

Closes #14557

When making an inventory adjustment in multi company,
the default location_id was all the time taken from
'stock.warehouse0' even if the user was not allowed to read
the warehouse. Inspired from _get_default_location in pos_config.py

opw:695616

Avoid traceback 'list indices must be integers, not str' when country_id not in sidebar.
env.browse(id).read(['name']) return a list, so country['name'] should be country[0]['name']

This reverts commit 8b64bf76.

This should have been fixed in 8.0, a moment of distraction made me
push it in 10.0.

This is not the branch you are looking for, carry on.

Courtesy of DynApps

A big section of code was wrongly indented (1 level too much).
The method was returning after 1 iteration of the loop.

Closes #14764

If only the code of a warehouse is changed, `name` is None.
Do not try to set None as the new pull name.

Fixes #14766

To have the same as the main method in stock