This plugin provides similar functionality that we have in ERP5 form to warn
user when he's about to leave the page without saving.

Allows getting current selection's MD5 even outside ListBox's renderer.

try 2: Now without NameError

This reverts commit 4d5df6e7.
Revert done due to ERP5-MASTER : 3506 Tests, 174 Errors, 18 Failures

Allows getting current selection's MD5 even outside ListBox's renderer.

Only set response headers when published alone.
Also, do not set Content-Length, as Zope can set it by itself.

add test to check if using the tag include_img on template, the image is added on the document, content.xml and manifest.xml

Add condition to not replace the manifest it already exists. It was added to fix the issue when a dynamic image is added on style.xml. The manifest is replaced and turns the document invalid

The grouping date is a property representing the date when this grouping is
effective.
In erp5_accounting, when setting a grouping reference, the grouping date will
be set to the latest date of grouped line. When running reports with
"omit_grouping_reference", lines that are grouped after the end date of the
report will still be displayed.

SQLCatalog structure changed, and can be updated with:
alter table catalog add column grouping_date datetime after grouping_reference;

You might also want to set a grouping date on movements with a grouping
reference in the migration.

The editable field has to be registered in listbox editable fields to be used
as an url column.

Coordinate base class already inherit from Base, so no need for class
inheriting from Coordinate to inherit from Base again. Also, no need to reapeat
the property sheets that are already defined on Coordinate.

This use to work because categories are metanode and metanode were organisations

Prior to this change, such accessors were only generated if
'acquisition_base_category' was set on the accessor, but such accessor also
makes sense without acquisition_base_category.

Most coordinates from organisation were configured to acquire properties on the
region categories. This was not a problem, because prior to
36420d5c ("Fix class hierarchy for nodes"),
Categories were Organisations because they are MetaNode.

MetaNodes have always been Organisations, but this does not make sense at all.
This change reveal some hidden bugs with code that was working accidentally
because all meta nodes, such as categories use to be organisations and have all
the accessors from organisations

Although this also fixes "too many files" error, the way to upgrade some kinds
of objects should be reviewed in order to avoid such export/import.