Make the database manager use `config['load_language']` instead of
`config['lang']`, just like the CLI option `--load-language`. If no language
is given, install `en_US` by default.
These two rules were used to restrict livechat users
to the read access to their own messages,
and allow livechat managers to see all messages.
Since 9.0, livechat messages are no longer
`im.chat.message` records (8.0),
they are now `mail.message` records, and this model
already implements its own security rules.
See `check_access_rule` of `mail.message` to know
more about the access rules of this model.
Therefore, these security rules are no longer necessary in 9.0.
Besides, it had as side-effect to restrict the access of
livechat managers for `mail.message` records.
For instance,
livechat users were no longer able to create customers.
opw-651958
When reversing entries in Journal Entry, each entry(account.move.line)
must be copied with its own 'tax_line_id'. In this way, the action window
"act_account_tax_tax" can find all the entries linked to a specific tax
(active_id) to compute the Tax Report.
opw:652598
In IE11, when adding a range to a selection that can fail if this range
is not displayed (display non on itself or an ancestor) or is not already
inserted in the dom.
e.g: IE fails in the following situation: http://jsfiddle.net/7cmf2tt9/7/
The feature causing this situation is minimal : it only set the cursor
at the end of a FieldTextHtmlSimple widget (the default widget for
fields.Html). This commit thus only ignore that error.
note: this is not an issue on IE Edge.
closes#9216
opw-652347
The method evict_record calls _update_cache with an empty dictionary,
which will not replace any cached value. Therefore, the cache is never
cleaned.
opw-652393
The mention mechanism of the chat composer first proposes partners that are
registered to the current channel or followers of the current document, then
users, and finally partners.
Also reduces the mention detection delay to 200ms.
Difficulty for the user to understand how to change the images.
Some options summernote being in the bar and the other in the snippets editor.
Need to merge this options.
[FIX] auto subscription
- removed auto subscription of managers for leave / allocation requests as this
can be managed through subscripion to the department
- updated some subtype labels
- removed auto subscription of leave / allocation creator as the employee is already
automatically subscribed; managers creating leave and allocation in batch should
not automatically follow the created records except through the department
subscription
[FIX] notification email batch
- add a context key to use the email queue for notifications linked
to allocations created in batch
- also fixed a missing context in a browse
The currency of the delivery method should match the currency of the
company. Indeed, the price specified in the corresponding product is in
the currrency of the company and does not depend on the pricelist.
opw-652716
- remove / udpate some paddings. Indeed some part of the notification emails
are badly aligned.
- postprocess the notification email to remove the content coming from odoo.
This ensure that action buttons present in some emails are not forwarded to
other people, notably customers. This is done by adding a div holding the
whole notification emails, with a summary = o_mail_notification. A summary
is used instead of a class or id because some html clients (like gmail)
strip classes, ids, ... summary seems to be kept in several clients.
The fields "payment_acquirer_id" and "payment_tx_id" were not set in the quotation
when selecting a payment method in the online quote.
Inspired from function payment_transaction in addons/website_sale/controllers/main.py
opw:652733
v13 of the POSBox image is vastly different from all the previous
versions. On top of that it contains a lot of new features. Because of
this a lot of the POSBox documentation had to be rewritten. While doing
that, we also decided to move the documentation to
odoo.com/documentation/user instead of keeping it here.
If the main object is not set, the default object used is 'ir.ui.view'.
One of the consequence is that website SEO metadata will be stored on
'ir.ui.view' instead of the correct model, in this case 'blog.blog'.
This will cause the SEO metadata to be the same for all the blogs.
opw-651898
Raphael Collet