Since the new translation process for views, their arch is translated upon
reading the views, before applying inheritance. Remove the useless translation
that was done after this process.
Enable the prefetching of several fields while evaluating an onchange. Special
care is taken to not prefetch computed fields or fields already in cache. The
latter is necessary to avoid "cleaning up" dirty fields by accident.
The translations inside the i18n/ folder are the translations published on
Transifex. It will contains the translatable "general" terms (menus, error
messages, actions...).
The account, taxes, journal names are made translatable thanks to the
l10n_multlang module but it should only be translated in the `spoken_languages`
values (nl_BE for l10n_be). These translations are present in i18n_extra folder
which is not published on Transifex.
Regenerate the translations correctly and populate the nl_BE.po file with
previous translations.
The hightlight element when a tip is clicked was placed over a white
rectangle. This induced a problem if the element was itself white.
Also the dimension of the helper were badly computed.
+ remove specific tip style in kanban view
Embedded the template core in a 'root widget tag' to make the selector 'this.$('.o_mail_chatter_compose_message_suggested_partners input:checked')' works.
When creating a document a message is posted (ex: 'document created') and the track field users are auto added as follower and notified with the last posted message (like the just create message). So the author was notify of the creation of its own document.
The problem did not appears using form view, beacause when the mail.message were reloaded, the thread was mark as read, so the partner (author/creator) was directly removed from the needaction_partner_ids field. The issue happen when loading the demo data, generating many needaction for the admin user (creator of most of the document).
This bugfix remove the current partner from the new follower to subscribe and to notify with the last posted message, as done when a message is posted (in _notify method of mail.message).
1) Check unit price before linking SO line
We need to make sure that the unit price on the SO line is the same than
the unit price that will be applied for the new analytic line.
It is the case for an expense product which is invoiced at cost price to
the customer, for example a flight ticket. The user should be able to
link 2 flight tickets with different prices on the same SO, which is not
possible before this fix.
2) Convert account move line amount into currency of SO if necessary
3) Partial revert of 2d5776d248
We want to decrease the invoiced quantity if the refund is generated
from the SO, but not if the refund is generated from the invoice
directly. Indeed, if we decrease the quantity from a refund generated
from the invoice, this will make the SO line invoiceable again, which is
something we don't want.
Fortunately for us, a refund generated from an invoice is not linked to
the SO (see method _refund_cleanup_lines in account_invoice.py), so no
extra code is needed.
4) Iterate only once in the SO lines in order to find out the
invoice_status of the SO
The test does not have hardcoded values referring to demo data anymore.
Moreover, in the test, we now use values which are different from the
demo data (621.54 instead of 700). Overall, this will make the test more
robust.
hr_expense: change car travel sale price
Car Travel Expense is used as a product invoiced at sale price.
Therefore, it is more useful to have a cost price and a sale price which
are different.
The whole idea of this commit is to avoid having the same values
everywhere.
With the new pricelist system, a price should be specified for any
supplier, otherwise the price chosen for a PO is zero.
Also add unit price for existing PO
add the stock_journal property in the yml test and make python test depends from AccountingTestCase to prevent errors when launching these test without a localisation. Also raise error in code if no stock_journal is found.
* When the autocomplete popup list appears, the focus should be on first element in list, in order to quick create a new record if no match
* Tour.js has been modified because jquery ui autocomplete needs a mouseenter event to be notified that this element will be set
Fabien Pinckaers