Reverts 037a7ed3
More details, see 574d45a6

This will be required to fix a possible race condition in causality_workflow

still keeping backward compatibility with older python_memcached.

This is required for ERP5Site_checkDataWithScript script (erp5_core BT).

Otherwise, we use superclass' __contains__ implementation, which uses
objectIds, which is inefficient in HBTreeFolder2 to lookup a single key.

This commit reverts fdf4fa44 that does not work in reality.

add work around for the performance regression introduced in Zope 2.12.23 in BTreeFolder2, for the case where we use BTreeFolder2 directly.

Partial commit of c29f5cda

Revert "Allow restricted python to use HBTreeFolder2 iterators."

This reverts commit 3da34864.

Partial commit of c29f5cda.

A ZopeLite patch was added to prevent loading of zcml files, which is wrong
for ERP5: CMF products were not properly initialized.

Code is also simpler now that we call OFS.Application.initialize(), which is
not significantly slower.

We keep patch not to register help though because this is quite expensive:
we should even consider always disable help because they seems to cause many
conflicts during Zope cluster startup.

A monkey-patch to unittest is updated for Python 2.7, so that tests aren't run
when they shouldn't (e.g. --save without --load).

Conflicts:
	product/ERP5OOo/tests/testOOoImport.py

 Create promise configuration on-the-fly with the configurations reusing
 existing API to get cloudooo, memcached and kumofs informations from
 environment.

 This approach allow us use erp5_promise alarms at any unit test to
 configure cloudooo, memcached and kumofs, instead implement ad-hoc
 configurations on tests afterSetup methods.

Since DeadlockDebugger is checking for product configuration,
it was no longer working in unit test

Provide migration ability from persistent Control Panel if present.
Drop destructive "backward-compatibility" code (delete object if old
version).
Fixes Zope 2.13 .

Fixes Zope 2.13 .

If we ever need it back, just move this Document class into a business template,
so that Products.ExtFile is not a hard dependency of ERP5.

since Zope 2.12.23, ObjectManager's get and __getitem__ returns only 'items' (no attributes / methods from the class or from acquisition).

ref. http://comments.gmane.org/gmane.comp.web.zope.cvs/22117

Now we can do like this.

updateCellList(portal,
               supply_line,
               'Internal Supply Cell',
               'SupplyLine_asCellRange',
               table,
               activate_kw=activate_kw)

Then reindex activites take into account the activate_kw.

that should be part of commit 9b5c74fb ('force' argument in
BusinessTemplate._install() should not mean clear catalog. we can and
should use 'update_catalog' argument instead to clear catalog).

we can and should use 'update_catalog' argument instead to clear catalog.

erp5_autocompletion_ui: Add JS ERP5Autocomplete() parameter to transform text before sending AJAX request.

For example, if one wants to uppercase/lowercase the value entered by
end-user.

erp5_autocompletion_ui: Autocompletion property value set to the field should be the one queried from the Catalog.

erp5_autocompletion_ui: Consider that description may not be needed, thus only one line, the label, is displayed.

Possible through defining a TypeBasedMethod (PORTAL_TYPE_getCompletionDict)
returning a dict serialized in JSON by the calling method, or otherwise
overriding fallback script (Base_getCompletionDict).

erp5_autocompletion_list: Move away generic JS code from RelationField as it should be reusable anywhere.

Limit the number of results to 15 instead of 20 as it seems to be enough (taken from an existing customer project).