Fixes remaining occurences of 8.0 in the windows installer. Mainly, odoo is now
correctly installed in odoo.9.0-timestamp/ instead of odoo.8.0-timestamp/
The lost filter wasn't working:
- The domain syntax was not correct
- It tried to filter `active='f'` leads,
while, in the SQL view, they were already filtered out
with `active='t'`
We can safely remove the active=`t` from the SQL view, by default
`active='f'` records are filtered out except if explicitely set
otherwise.
opw-651746
Since invoice quantities are computed from the invoice lines linked to the so line via a many2many field, we need to overload the refund function that adds the fields on the invoice lines; explicitly copying the sale order lines references.
Some usability improvements. A field "Purchase Order" is added on the
invoice line, so it is much easier to make the link between the invoice
line and the PO.
On the other hand, the "Purchase Order" field which was used for
encoding help is kept empty since it is not meaningful.
If the default_sale_tax_id or default_purchase_tax_id is removed from
the settings, the ir.values must be updated accordingly (i.e. set to
False). Otherwise, the value will come back when the page is reloaded.
When using the tab key on non text node range, it could fail in some
given case.
Also when removing the last element of the table row, a correction was done in
d33086c03f but if there was no element before the table (eg. the editor
is empty) an error could occur.
Tests for null range were not done in #8845, so in given case (where the
focus is not in the editor) we could get an issue.
The code for remembering the selection when clicking the editor
was made useful in d33086c03f, but there was an edge case when
the editor itself was in a modal: then the selection would be lost.
This commit change the code as following:
1) restore the selected range if:
- the current selected range is not in the editable of the active editor
- there is a corresponding saved selected range or we are in an embeded
editor (and not in air mode as when editing the website)
2) save the selected range if:
- we don't restore the selection,
- the current selected range is in the active editor editable area
These menus were visible to all employees, but the reports use
hr.salary.rule.category that is only available to HR Officers/Managers.
As these reports are not meant to be available for employees anyway, we
hide them.
(this bug has been spotted by the nightly crawler that clicks on every
menu as demo user)
The variable `date` is compared to the field `name` in the selection
query. `name` is filled in with datetime data. In particular, in the
module currency_rate_live, datetime.now() is used in the name. It is
necessary to make an appropriate comparison to make sure we select the
updated rate right away.
This controller is mainly used by im_livechat which don't send html message. It is more secure to force it in plain text. If anonoymous user write html tags, it will be escaped and sanitize.
Posting message is done in 'html' since mention add html tag in body. Clickable url is done server to allow link in mail and chat message. Plaintext are transform into html, and html message are simply parsed to transform url into clickable link.
When adding a line to a confirmed sale order,
the procurements are automatically created, with
this product.
Therefore, the product of the line should no longer be changed,
as otherwise, the product on the procurement would no longer
be the same product than on the sale order line.
To be able to change the product of a line on a
confirmed sale order, you must therefore first
delete all procurements.
When using the editable list on the sale order form,
it was not possible to add a new line on a confirmed sale order,
while it should
(when `Allow to edit sales order` is chosen in the Sales settings).
The reason was that the fields `tax_id` and `product_id` were
set as readonly when the SO state was not draft.
When using the popup/dialog view, it worked by luck, because
the line `state`, which is a stored related field to the sale order state,
was not correctly computed, and was seen as `draft`, while it should
actually be `sale`, for a confirmed sale order.
We change the readonly condition of these fields,
which is now based on the fact wether or not
the line is already invoiced or not, which makes
more sense.
opw-651573
- Add recipients as followers, and automatically refresh the follower's list
(before this rev., one needed to reload the record to see the followes' list
updated)
- Don't display needactions on chatter's messages
- Simplify buttons of suggested partner's dialog, as it should only offer two
possibilities: Save or Cancel
- Replace unnecessary t-raw's by t-esc's
When looking for a so_line linked to the task, the sale_service module accidentaly removed the already referenced so_line.
The desired behaviour is:
1/ Check if task is linked to so_line, if yes reference it
2/ If not, then let the dict as it was before, do not put False if there already was a value (for example something that sale_timesheet might have found)
Aaron Bohy