lst_price was exported as found in tag
<attribute name="name">lst_price</attribute>
so lst_price was exported

Remove from pot to avoid confusion

The fact that it uses the correct template id now, fixes #6860

The read_group calculates the sum for every group for the non-stored fields  as it is not possible
anymore to add it in the xml, fixes #6638

The read_group simply searches for all products in the group and sums the totals of the fields for these
products.

Due to commit 1576bc98,
when name_search() is called on analytic accounts with
multiple path components (e.g. A/B/C), the intermediary
searches are done without the extra domain criterions,
because they should only apply to the leaf.

However because the limit was applied for each step
of the multi-path search, it was quite likely that
no valid results were found in the final filtering,
returning no result at all.

In fact the intermediary steps should not apply the
limit at all, because the leaves we're looking for
may actually be located under parents that are not
found when the limit is applied on each step.

This commits removes the limit (hopefully without
too much of an extra penalty for large databases)

It also introduces a better fallback in case the
multi-path search did not produce any result,
for example if the name of the lead really contains
a '/', and it was not meant to be a path separator.

contains acquirer definition to support Atos Wordline online payments
Courtesy of Eezee-It

Closes #6684

The next action date (date_action) should be red if in the past, not if the
deadline date is in the past.
Introduced at 9f68a37a
Courtesy of @sve-odoo 

When clicking on the BOM state button from product.product, and clicking
on create afterward, it must open mrp.bom view with the product and product variant
already set(as with product.template).

opw:645045

If the price in a price list line is based on "Supplier Prices on the product form",
the model "product.supplierinfo" and "pricelist.partnerinfo" must be readable by the
public user.

opw:645709

The method "_create_account_move_line" must take into account the rounding
method when computing the taxes for each line.

closes #7683
opw:645516

The new-api record prefetching algorithm attempts
to load data for all known records from the requested
model (i.e. all IDs present in the environment cache),
regardless of how indirectly/remotely they were
referenced. An indirect parent record may therefore
be prefetched along with its directly browsed children,
possibly crossing company boundaries involuntarily.

This patch implements a fallback mechanism when
the prefetching failed due to what looks like an
ACL restriction.

The implementation of `_read_from_database` handle
ACL directly and set an `AccessError` as cache value
for restricted records.

If a model (like `mail.message`) overwrites `read` to
implements its own ACL checks and raises an `AccessError`
before calling `super()` (which will then call
`_read_from_database`), the cache will be not fill,
leading to an unexpected exception.

If this commit messae looks familiar to you, that's
simply because this is the new-api counterpart of
b7865502

Display claim_count and claim_count_out only to salesman and contact creation
group members as it requires these access rights to be computed.
Fixes #2458, Closes #7734

this is needed when selling products with a disabled uom

Don't use select element when printing a non-filled survey, and small
appearances improvements.

opw-645011

The state of a crm claim has been removed in f14eddbb.

Thus, it is not possible to know the closure date and this commit hides
the field in the view.

opw-645826

The value associated to the the "Closed" is done and not close.

opw-645808

A jquery selector $('td[id^=]') may have been valid once uppon a time,
but it cause error on current jquery versions.

Also in some case when we want to add a field on a view, there may be
a mess to detect the parent.

opw-645557

Unlink typical domain evaluation (ir.rule, filters,...), the evaluated domain
for automated actions did not included time in the context so it was not
possible to make time based conditions in domain.

This should be used with care as filters 'Based on Timed Condition' are still
possible and will probably be enough (and safer) in most cases.

The field "state" in "sale.report" model must consider the state used
by "sale.order.line" to be consistent with the view created in this model.

The function _sale_count in 'product.product' model must return
the number of product included in a "confirmed" or "done" sale order line.

opw:644200

If the variants are displayed by list of attributes, the image of a
product displayed would be updated to the image of the first variant.

But this was not done when using the customizing option "List View of
Variants".

opw-645729

The field used for the report was different than the field used on the
model the report is based uppon.

As analyzed by jle.

opw-645582

The current xpath was the one for saas-6 or future 9.0 but didn't work
in version 8.

closes #7715
opw-645555

note: this commit should not be forward ported after 8.0

closes #7715
opw-645555

Accessing the phonecall and the lead do not require the same permissions so
should not be computed in the same method.
The effect of the multi was already lost as the phonecall_count was already
computed in another loop.
Add the phonecall_count button in a second view to make the computation only if
the user has the requried access rights.

Fixes #2458

related to opw-645011

Modify all references of google_attendee['email']

When the max seats available is set to 0, there should not be a limit to
the seats available.

Previously this was not taken into account in the frontend event ticket
sale, so an event would appear to be sold out.

fixes #6999
opw-645542

You may get a google_attendee without email from Google, cf #3853

The content of website.layout_footer_copyright is modified in several modules
but the terms were missing in .pot file.

The method add_payment expects to recieve the id of a journal, not a browse
record. Introduced at 4b548d98
Courtesy of bluesoft83

The onchange on partner field must not fill the company name if
the partner is not a company or not in a company. If the partner
is not a company, the contact name field must be filled with the
partner name.

opw:644878

Delete the code introduced by 656f8241
Group by didn't work in calendar tree view, group of records showed (0)
as number of related records for each group.

closes #7602
opw:644735

add new team member Jean-Paul
fix email adres Maarten

Keep the existing information in the context for the price_get call instead of
creating a new one.
Closes #7646

When calculating the cost, quantity did not take the product efficiency into
account when calculating the cost. The quantities on the MO order were correct,
but not the cost that needs to be increased to compensent efficiency.

Closes #5927
Closes #7648

When doing a copy of a google drive spreadsheet (in google_drive.py's
copy_doc method, using the following google API call
https://developers.google.com/drive/v2/reference/files/copy).  Google
server return an error if we used the old spreadsheet KeyId.

The new FileId is available in the AlternateLink and this commit updates
it.

closes #7660
opw-644889