It happens for some objects that we don't allow the user to see them, even though
we might allows them to get some informations. Typically an object that they
should not see in a module but that could be used for some purposes.

Signed-off-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>

Signed-off-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com>

remove portal_web_services from erp5_base
add required dependencies on bt5

Use the same detection scheme as Formulator.
Extends a bit further rampant code duplication.

It was broken since commit fda3f093
("Move some work out of Message.__init__").

This reverts commit 96bfc618.

Revert "Use default Person's site & group as set by respective Career settings (not any more Person's Assignments)."

This reverts commit 9e376960.
Afterall, it seems more logical to use assignments because security depends on
assignements, so a user with inconsistent careers definition could create a
document that he cannot view/modify

This reverts commit 09960648.

This patch was draft and it was pushed by mistake to master.

Items are used on tasks for generating reports

This is useful for some reporting

Like this :
- we see immediately what is selected
- no risk to remove by mistake something already selected
- much more convenient to change
The only tiny drawback is that the look might be a bit different when many values are selected.

Because we want to display "Detailed Aged Balance" and not "Detailed aged
Balance"

some script pass group_by=('function_uid',) instead of group_by_function=1, resulting behaviour in the end must be the same

other ZEO clients even if ZODB Components are not.

Steps to reproduce:

  1/ On zope1, view and edit a person to make sure class is fully loaded.
  2/ On zope2 add an interaction in person_interaction_workflow and add a script raising an exception.
  3/ Edit a person on zope2. The exception is raised, confirming that the interaction is called.

  When editing a person on zope1, the exception is not raised.

ZODB Components: Rename common view to ComponentMixin_view (naming conventions and clash with erp5_pdm).

Before, the field value cache was only invalidated on the node where a field
has been modified, so similarly to reset of ZODB Components, implement
synchronization on all nodes through ZODB Cache Cookie.