Follow the specification of shacache and shadir: PUT is used in shadir,
POST is used in shacache in order to create new content. erp5_web can be used
without any modification to serve fully restfull POST interface.

Create special action for Web Site which reacts on POST type of request and
support it by low level functionality. This action is available in web view
only and affects only Web Sites configured for shacache.

Other changes:

 * do not check uploaded content, just return calculated sha
 * break compatibility during upload (better now then later)
 * avoid hiding errors during publishing content by hiding exceptions in
   WebSite_publishDocumentByActivity
 * do randomisation in tests and make them live test safe
 * connect to running web server in tests in order to use all stacks during
   uploading and downloading content
 * cleanup erp5_web_shacache and erp5_web_shadir business templates and remove
   not needed scripts
 * during testing treat running site as blackbox and do not try to be too smart

events (i.e. Mail Message) in CRM event_module.
Typo & XXX: comment added.

Messages) are to be stored inside CRM event_module.

Use absolute path, and display useful log when sql dump is not found

Recovery | Update

by human interaction.

Each workflow should use the respective Zuite.

Check the lock files, and launch the xvfb with some available display.

Use ERP5TypeFunctionalTestCase and runUnitTest instead of runFunctionalTest

O directly use the browser for manual runs.

The Configurator is usually used to bootstrap some instance, so have
previous business templates may cause some inconsistent.

Reorganize to execute tutorial tests for each configuration.

This make code of bt5 a bit smaller

Phantomjs still draft.

Make code more generic and several clean ups and API definititions.

Several changes which only improve code readability only.

It's job of form validation to handle this case appropriately.

modify Person object it can still unblock it if it has access to system
events).

Unknown ids must not prevent to create a document, so let ERP5 compute new ids.

Create (and open Assingmnet) before validating Person object.