leading to potential issues.

Now the behavior is back to its previous version, posting on the user creates a private
discussion. Fixed management of model variable in message_post to avoid posting messages
on the mail.thread model.

Classic inbox writes on partner, with hr it writes on the employee profile, like previously.

[FIX] website_forum: fixed (un)publish management on the profile. Partners are now also published by default. Better protection of displayed profile: only publis profiles with karma >= 1 are displayed on the forum, to avoid allowing external users to browse the user lists. Some cleaning / improvements in the bio edit form that was a bit buggy.

[FIX] survey: in prepare_result, result_summary variable could be returned without being initialized (error in question.type maybe, but anyway should be more secure)

[FIX] account: several fixes in bank statement reconciliation related to multi-currencies use cases where the statement is a foreign currency but receive a payment in the company currency

[FIX] bus, im_chat : disabled realtime status notification, replace it with rpc calls and set random retry delay on bus (longpolling)

Portal users are not allowed to read account.move.line model
Therefore, in the portal, if you let the payments in the invoice view, the portal user is warned that he is not allowed to see account.move.line

Fixes #2008

filtering displayed meetings according to the selected partner.

by the user. Otherwise it was resetting the search to all events.

- fixed call to a wrong method
- fixed button display, now based on the standard way of managing karma (popup when
not having the required karma)
- fixed button display karma computation
- some css tweaking for this button

For companies having a lot of invoice, not applying the year filter leads to a long reponse time

At the confirmation of a bank statement, the name may not be set (e.g. generated by point of sale). This field is not requred so make a fallack on the statement line (which is required).

A new ir.sequence is generated at pos.config creation for the orders. However it was not used as the type was not set. The fallback was done on the general sequence.
In addition to the sequences being shared, it was not possible to create a pos.order in multicompany (no sequence found for user company, name was null).
Same issue for the pos.order.line.
This patch generates correctly pos.order and pos.order.line sequences at pos.config creation.

Instead of using the pos.config sequence to generate session number (not what this field was intended to), use the existing sequence for pos.session.
Remove company_id value on default pos.session sequence to make sure it's shared between companies and correctly set the prefix.

If the pos.config is not properly configured for multicompany (e.g. using location belonging to another company), launching a session with this config may fail (access rights).
This prevents to configure an incorrect point of sale in the first place.

[FIX] website_forum: second part of the fix introduced at revision fd5516ad. Wrong commit was added to 8.0, missing code cleaning.

[FIX] website_forum: issue in biography (unnecessary tags added by editor) + menu control (Users / My Profile)

in the behavior of browse records due to the new API introduced a wrong
behavior, now fixed.

[FIX] point_of_sale: the order reference used the session sequence number wich was not unique accross sessions on different point_of_sales.

Now we are using the session id which is unique, but is less understandable

[IMP] Cleaning of reporting (group_by, filters), adding new favourites and default views, some renaming (py and xml files)

8.0 wmspartialview jco

[FIX] website_event: allow everybody to ready event.type. Else a user who is not public, not portal and not event user or event manager cannot read the event.