This fixes an error message preventing a non-system-manager user to edit the
Point of sale settings.

This fixes an error message preventing a non-system-manager user to edit
settings.

Rescue sessions have been added with revision
bed40932

With this feature, this is possible to have multiple
pos sessions opened for a same user, if there are
rescue sessions.

`get_current_session` rely on the fact only one pos session
can be opened per user.

Rescue sessions are now excluded to get the current session, so:
 - at most one session can be found
 - rescue sessions cannot be resumed.

opw-652857

Forward port of 503820ac from 8.0

opw:652310

HTTP status lines are required to have both
a status code *and* a "reason phrase".

Some stricter HTTP clients / proxies choke
on status lines without "reason".

Technically, setting `response.status` is supposed
to set both at the same time, so we need to provide
both, or to set `status_code` only and let werkzeug
add the reason.  This patch does the latter.

Fixes #8924

The serialization gives different results for some elements.  For instance, an
empty element `i` must be serialized as `<i/>` in XML and `<i></i>` in HTML.
It must be done like that, otherwise the world (of web browsers) would break.

Add a test case for `html_translate`.

group_no_one is almost no longer accessible (way too technical to ask to modify
the url to end users) while this field is simply more advanced configuration
(functionnal and not technical).

Replace technical feature group by purchase manager.

The sidebar can be make visible by clicking on a button 'Channels' in
the control panel.

They need to have the message_type 'email' instead of 'notification', so
they can be starred in the interface.

... allowing multi-line edition, like in the chatter.

Shortcuts:
	- in the client action: ENTER sends, SHIFT+ENTER goes to newline
	- in the chatter: SHIFT+ENTER sends, ENTER goes to newline

Don't use autosize anymore to resize the textarea according to its content as
it didn't fit well within the flex layout of the client action ('height: auto'
didn't increase the height of the flex-item with 'flex-grow: 0'). We perform
the resizing ourselves instead.

including:
- reset scroll position to bottom when leaving channel
- allow clicking on the avatar image
- hide stars when message is of type notification
- sort channel names
- add # before channel names
- rename Whole company channel in general
- replace \n and \r in messages by <br/>
- lighten the hover color of sidebar items in the client action
- Display @ before mentions

Allow to inherit state modification access right

Closes #9145

Name should be Deferred Revenue Type if the type is sale

The currency rate used to compute the amount to show must be the currency rate
matching with the date of the payment.

opw:652478

When the http csrf is default enabled, callbacks raises a http error 400:
Invalid CSRF Token.

Fixes #9065
Closes #9073

cherry-pick of 8feabe46 and 2fa8b99e
needed for nightly build, sorry for the forward port

[FIX] stock_account: counterpart account for standard price adjustment is now expense instead of stock_input or stock_output.

[FIX] stock_account: do_change_standard_price() function (button to manually update the standard price of a product in average/standard price) fixed (was simply crashing).

When website_quote is installed, the Terms and Conditions of the quote
template should replace the Terms and Conditions of the company.
However, if the T&C of the quote are not filled, they will be kept
empty. This fix uses the T&C of the company as a backup.

This fix also set the TéC in the lang of the partner.

opw-652390

The amount to show in payments_widget must be the opposite of amount_currency like
in the else condition:
    amount_to_show = payment.company_id.currency_id.compute(-amount, self.currency_id)

opw:652478

Should go to master, not to 9.0

Commit 4f9c9adf adds the context to the RPC call of 'message_post', but the
context was only defined for messages sent, and not for internal notes logged.
This causes a crash when logging a note on a calendar event as its method
'message_post' makes the assumption that it always exists, and tries to access
one of its keys.

opw-652470
Closes #9164

Fixes/hides a deadlock when running test_sale_order with either a single
database or a db_filter making a single database visible: the test
causes a report to be printed, which invokes wkhtmltopdf, which tries to
fetch assets using the registry which is being loaded. The asset request
thus waits on a lock which is held by the test which waits on the asset,
deadlocking the whole thing.

Using HttpCase means we're using the test_cr or something and bypassing
the deadlock, instead the asset requests just 404 as they do when using
the nodb routing.

.. instead of at the start. The reason is: if any rollback have to occur
during the call to `save_attachments`, we want to avoid rollbacking an
unlink on the ir.attachment table (because we cannot rollback the
removal of a file in the filestore).

This issue is especially annoying when we generate a bundle whose
ir.attachment record has the same hash than the invalidated one (for
instance when one of the source files in the bundle has been touched
but not modified) and of of these rollback occurs: the bundle has been
deleted on the filestore and cannot be served.

The order of the stylesheet's declarations in the html matters. Make sure
that the first part of the css is declared first (*.0.css).

If the compilation of a stylesheet asset produces any error, don't save
it and instead output it debug-mode like.

Else, a css file with three rules produces two files when the max css
rules is set to three.

see rev 37959d45

This way it is overridable by unit tests.

It's not used