Do it only after other direct methods fail,
to avoid ignoring a closer environement coming
from a calling frame.

+ Sign CLA

Closes #5148

Closes #5175

This reverts rev. 9f9e7ef0

As explained in 9f9e7ef0,
if a field "lang" is present in the view, clicking in any action item
in the more menu leaded for the action title to be translated
in the lang value of the form, such as in the partner form.

9f9e7ef0 fixed the issue,
but has as side-effect to not update correctly the active* keys.
So, if "active_id" was used in the context of the action button,
and the active_id was set in the dataset context, for example
because you come from another form, trough another action button
(For instance, Customers > Opportunities > Logged Calls),
the active_id was not updated with the current id of the record.

opw-620293
opw-617321
fixes #3462

Closes #5127

If the list view is grouped (with a groubpy filter),
the default order must always be the order of the groupby

[FIX] Simplify destination package and don't write package info on quant when moving entire packages Closes #5125

Most pop servers don't perform deletions until QUIT. If for some reason
the process is killed while fetching a large quantity of messages, the
quit method isn't invoked, while the commit method has been. We may thus
end up with duplicated messages the next time we try to fetch. It therefore
helps to fetch the messages in small subsets and call the quit method between
those subsets.

In 7.0, prevent changes in activities of validated sheets was done thanks to the constraint
_check_sheet_state.
In 7.0, python constraints were checked at each write operations
whatever if the fields on which the constraint is were altered or not

This is no longer the case in Odoo 8.0: The constraint is checked
only if the fields on which the constraint is are altered.

As this specific constraint must be applied anytime, whatever the altered fields,
we now do this constraint check in the "write" method.
Besides, it was already the case for the unlink method.

opw-627415

has_group is cached and do not fetch all the users with a slow `group.users`

Once a timesheet confirmed, the activity hours should not be modified,
for any reasons.

The constraint _check_sheet_state prevents to modify activities
for confirmed timesheets, but does not prevent the addition
of new activities within the current, but confirmed, timesheet.

opw-627415
fixes #5128

Improvements were requested in Issue 626112 like splitting columns, and the second table was broken so I also fixed it

This reverts commit 8cd2cc89.

It turned out that forcing recomputing fields as user admin breaks some
existing behavior.  Instead, we make the recomputation as user admin explicit
by adding compute_sudo=True in the field's definition.

Closes #5157

As in python id is a builtin function name.

Closes: #5027

Try a "git blame" or "git shortlog -nse"

Still around 10 commit remaining to be indentified.

Closes #5138

Closes #5136

when creating Cost of Goods Sold Journal Entry

[FIX] calendar: allow to force the sending of email in function _send_mail_to_attendees (even if email are himself) and use it for reminder.

Since rev. 1ce0b70a, ir.ui.menu
was readable for employees and portal users only

Since rev. 74aa7406, the navigation menus
were displayed for employees and portal users only.

Therefore, when sharing a record with the share feature, nothing was
displayed when following the link.

This rev. introduces a new group "Shared group", implied for all shared groups
created through the share feature.
Read access to menus is given to this group
The possibility to display the webclient navigation menus as well.

When sharing a record to a share user (for instance, the quotation),
the action in the url was set to "action_id=" instead of "action=",
therefore, the link sent just leaded to nowhere.

mail.message and mail.notification are transversal: they should not received directly the access rights