As this means sorting had no effect, drop sorting on versions: versions
are arbitrary strings which can have any evolution scheme, so do not try
to guess what is more recent than something else.

Also, make effective date visible and editable on relevant document views
lacking it.
Add a test.

Specifically, system must not compare version to decide which is older, and
does not. So remove noise from test, and reword docstring.

The duplicated getBrain/getObject code in Shared.DC.ZRDB.DA only exists with
some versions of Zope or Products.ZSQLMethods

reload(), which should be called only for filesystem tests, was called for
ZODB Components. So on the first execution, sys.modules was updated with a new
instance of the module whereas the module in erp5.component.test stayed the
same. On the second execution, reload() failed it checks whether
sys.modules[MODULE] == erp5.component.test.MODULE.

fixup! SelectionTool: Changing storage or memcached settings were not taken into effect until restart.

fixup! SelectionTool: Changing storage or memcached settings were not taken into effect until restart.

fixup! SelectionTool: Changing storage or memcached settings were not taken into effect until restart.

* date attribute is converted to timezone only when attribute is accessed (and not in __init__ anymore). Some code that needs performance may be able to use date_utc attribute wich is the date as UTC
* debit, credit, debit_price and credit_price uses "is_cancellation" column instead of getObject().isCancellationAmount()

* Ctrl+S to save
* Ctrl+space to autocomplete
* unsaved changes warnings

Using https://github.com/ajaxorg/ace-builds/commit/45d3068aa7190f08396bcfe134e505fe144c1ccb

erp5_mysql_innodb_catalog: add related keys child_aggregate_relative_url and parent_journal_relative_url

This allows to use the same script for various columns. It is
particularly convenient for listbox used in reports with a list of
columns that could vary depending on data.

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