[FIX] Fix website theme slowness
[IMP] base: no default domain for partner's title

The title field should not have a domain by default.
When a new record is created or the 'is company' field is changed, the onchange_type is triggered to restrict the domain accordingly to is_company field.
When an existing record is modified, there will have no domain on title field. It's not ideal but at least companies will be able to change the title without the need to modify twice the field is_company.
Fixes #1713
[FIX] --dev mode crashes on read_template ormcache invalidation
[FIX] export: in saas-3, req becomes request.

Error during forward port b9275da8a52255d0fc3f914de9d406612e7dde50
[FIX] web: CharDomain form widget: fixed change selection
button not correctly displayed depending on the effective_readonly
parameter. It is now correctly computed.

Also added a link to see records when in view mode, instead of not
being able to see the selection if not in edit mode.
[MERGE] Forward-port saas-3 up to 9b55532
[MERGE] Forward-port saas-4 up to 9a84d55
[MERGE] Forward-port saas-5 up to acbdac4
[FIX] google_{account|calendar}: fix synchro

- no more tracebacks when trying to sync more than once with Google Calendar
- no more context hacks, explicit return of `ask_time`.

(Closes #1588)
[FIX] base : context evaluation with active_id server side. It now keeps the active_id in case of a refresh.
[FIX] Fixed the issue of calendar view reload events inconsistency, when the slow create popup creates event through any form button which is kind of object, action or workflow at that time events are reloaded but still button action is not called like workflow is not triggered and hence state of the event is still not changed and due to domain newly created event is filtered, note that events are refetched when create_completed is triggered and create_completed is triggered right after creation of record, but there are case where some form button changes state of the record and it requires to refetched for example we have scenario in mrp order planning where Confirm Production creates event but before workflow is triggered and state of the event is changed, events are reloaded and newly created event will not returned because of domain.
[FIX] test_new_api: missing parent menu
[FIX] account: reconcile: no useless revalidation

Avoid revalidating the complete account moves
that contain the lines being reconciled.
The reconciliation does not change the validity
of those moves anyway.
This represents a very important speed up of
reconciliation when moves with several hundred
lines are involved.
[FIX] stock: inventory lines with no production lot: compare with correct stock level

Inventory lines without production lot number should
be compared with the stock level of products without
a production lot. Otherwise the final result of a
validated inventory is wrong as soon as there are
lines with and without production lot for the same
product.

Adds corresponding regression test.

Fixes https://bugs.launchpad.net/openobject-addons/+bug/1008099
Manual rebase of #1658, courtesy of Numerigraphe
[I18N] Update 8.0 translation with latest source code
[IMP] bundles: display warning for forbidden local @imports
[FIX] web: do not focus if the focus_field is not a field

Sometimes, focus_field could be a button, and in such cases, we should not focus on it

opw-612045
[FIX] models: onchange on new records do not nullify fields from _inherits records
[FIX] point_of_sale: field date of report.pos.order should be a datetime

The date_order field of the pos.order is a datetime, not a date
As, in report.pos.order, the date field is related to date_order of the pos.order

We usually do not commit fixes altering the model fields structure in 7.0, but this one is retro-compatible, as the database structure won't change
[FIX] models: stored func fields computation on one2many write

On one2many fields writing in an existing record (not when creating new record), the computed stored fields of the one2many were not re-computed correctly
Computed stored fields were marked as modified only if no_store_function was not set to True in the context. no_store_function is set when writing one2many records on an existing record.
Now, these computed stored fields are marked as to be recomputed, but are recomputed later, at the end of the existing record write