[FIX] account:  the 'Customer taxes' field on the product is readonly when my product doesn't have any variant
[FIX] website.snippet: display snippet editor button inline insead of 2 lines for the small boxes
Merge pull request #1337 from odoo-dev/saas-5-fix-product-taxes-view-chm

[FIX] account:  the 'Customer taxes' field on the product is readonly when my product doesn't have any variant
Merge pull request #1338 from odoo-dev/8.0-fix-website-snippet-button-css-chm

[FIX] website.snippet: display snippet editor button inline insead of 2 lines for the small boxes
[FIX] website_sale: fix error in tracking_last_order which was using the field is_delivery from module delivery
[FIX] ir_attachment: _filestore cache ignore uid

replace ormcache_context by ormcache: use the context in the cache key is useless
set skiparg=3 (default skiparg=2) so the uid is not used in the cache key: the filestore path is the same for all database users
[FIX] web: avoid trying to access to deleted record message when change password

The onchange call can be made with empty ids list (which would fail). opw 610810
[FIX] web: wrong tooltip display for long menus

Due to the switch to Bootstrap 3.2 in this version, tooltip auto placement works erroneously (see https://github.com/twbs/bootstrap/issues/13897).
This is a workaround, waiting for a fix in Bootstrap assets.

(Closes #1341)
[FIX] models: check harder that default value is not NULL before setting it

When computing defaults we may end up with
a falsy value that is not None (e.g. '' or False)
That value will be cast to None when being
saved in the database, depending on the column type
(e.g. saving False on a many2one actually stores NULL).

Improve the test to consider the value being written
*after* that conversion, to *really* avoid nonsensical
and expensive queries such as:

    UPDATE table set col = NULL WHERE col IS NULL;
[REF] Odooification
pull from odoo/8.0
[IMP] ir.logging: add index on dbname/type, important with high number of log lines
[FIX] website: more robust inherit between footer_custom and footer_default
[REVERT] 8b41906: disabled all on_change on new record form

This reverts commit 8b41906bf8a22e3f00d3ea334f89b7f1aec27442.
[FIX] models: display_name and name_get mismatch

- display_name uses name_get and not the other way around:
name_get should not call _compute_display_name, _compute_display_name should call name_get.
The previous behaviour was not backward-compatible with the old api.
All the models redefining name_get would have 2 different behaviors between name_get and display_name.

- Do not set an inverse function to display_name:
In most cases, writing on display_name writes on _rec_name (if any, not mandatory).
If the display_name computation is redefined, we need to redefine as well the inverse method to avoid unexpected behaviour
This required to also modify tests in base_import as readonly fields are avoided.

- Remove search method on display_name:
For the same reason as for the first point, it could be good that searching on display_name use name_search (and not the other way around).
However doing this would be very inefficiant (need to do the search, without limit, extract the ids of the name_get result just to generate
a subdomain ('id', 'in', [...]). As in most cases it would anyway mean to search on the _rec_name it's better to directly do so.

- Changing label to avoid mismatch:
In view displaying the list of fields or when a match is made on the label of a field (e.g. when importing csv file,
matching is made on both label and technical name), the fact that display_name field has '
Calling it 'Display Name' will avoid most errors.

- remove display_name definition from website_forum_doc,ir_model:
These fields are doing the same thing as the display_name of the new api, we can remove them.
We need to keep the one for res.partner as it's a stored field.
[IMP] account.invoice: add extra @id on `smart button` to make inheritance easier
[FIX] res.users: safer read() when computing default company value

The goal is to avoid any kind of prefetching
of other fields when copmuting the default
company, as this will sometimes happen in the
middle of a database update, when the default
company is used for setting the default value
of new columns. In that case the db schema
may not fully match the in-memory model, leading
to an SQL error.
[FIX] stock: backport of rev 0a6d63b
Forward port of branch saas-5 up to eda2f06
[FIX] {base_action_rule,calendar,hr,mail,project_issue}: decorate the method `message_post` to specify signature