The user can be present from diferent logins, password tool only works with ERP5LoginUserMager
  users.

Mixed commit:

  43b1ae1b
  2f05fe1b

Returning true allows to add movements to existing one, and this group shall
always separate them.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

Original commit from : Lukasz Nowak <luke@nexedi.com>
                       3e45ec35

From Lukasz Nowak:

1- Compensation is undesired. (51c8a250)

  Raise loudly with message.

2- Disallow any compensation. (3c74ed07)

3- Emit more informative log. (534b2e77)

Also minimise activity hurricane by calling expand directly.

Open Orders are searched using indexation timestamp, which allows to see them
in "windows", and does not repeat expand if not needed.

Generate activities and allow to pass the tag. Use search and activate
everywhere which will allow to walk through objects without killing the cluster
even in case of really big documents.

Avoid calling isDivergent which can take few minutes to finish.

causality_state comes from well designed causality workflow, which informs
enough about delivery state. Fetching causality_state property is extremely
fast.

Notes:

Do nothing on 'calculate' instead of disabling *_causality_interaction_workflow as
these interaction workflows do not generate activities directly, and do work
that can't be postponed.

By contrast, 'calculate' transition of delivery_causality_workflow is modified
so that no 'updateCausalityState' activity is created by default.

This commit also update list of method_id which should not call calculate_causality

Conflicts:
	bt5/erp5_crm/bt/revision

See nexedi/erp5@6c4f7600

Allows to keep UI tests working independently of the login process
implementation details.

This reverts commit e5c160bc.

in API script AccountingTransaction_createReversalTransaction

Opening an accounting period is refused if the start date of the period
is more than one day after the stop date of the previous period, but this
check did not take into account that "next day" might be more than 24
hours, like it's the case when daylight saving happen between these dates.
Instead we check that the difference is less than 1.9 days.

Reorganise tests to group accounting period related tests in a dedicated
test class and add missing tests for period validation checks.

Also fix a few race conditions with catalog indexing that are probably not
a problem in real life but were revealed by the test.

See SQLBase._getExecutableMessageSet for operation principle.
Removes the notion of order_validation_text: activity validation is no
longer evaluated per-activity , but per-dependency for multiple activities
at a time. In this context, order_validation_text does not make sense as
it flattens all dependency types for a given activity.
Rework activity-dependency-to-SQL methods: use a dict rather
dynamically-generated method names.
Based on initial work by Julien Muchembled.

Seen happen on SQLDict with 94 indexation activities being stuck assigned
to a processing node on which load failed because of an SQL deadlock.

The main reason for not using cache.addAll was to fill the cache as a low
priority task, not to generate too much traffic, the safari compatibility
was secondary. Now that safari seems to support cache.addAll, remove the
comment about safari.

Components also have some extra checks in checkConsistency, we should
include this in coding style test.

See merge request nexedi/erp5!1324

This simplify code and also bring the functionnality of c484f8aa
(erp5_xhtml_style Base_cancel and logged_in: do not allow redirection outside
ERP5 site., 2016-02-12) for the cases where authentication_policy is
installed.

This also fixes a problem with translations of "Your password will expire at
 {date}", which was using different messages for every possible date.

Tests needed to be updated because we now redirect with properly URL encoded
parameters.

See nexedi/erp5@ea219b74