cancel & cancel_action require now View permission

Breadcrumb page is removed and merge into the Tab page.

The document title is now usually an history navigation back link.

add test case in erp5_ui_test

/reviewed-on !90

/reviewed-on nexedi/erp5!94

Sanitizing client data would help to prevent such issue.

/reviewed-on nexedi/erp5!92

(400 or 502) + add test case in erp5_ui_test

… 30 minutes difference.

/reviewed-on !93

caching_instance_method not used

erp5_simulation_test: as `erp5_default_business_process` is required in some test cases
erp5_simplified_invoicing: as `Invoice Line` should be allowed by `Sale Invoice Transaction`
erp5_configurator_standard_accounting_template: as `default_invoice_rule` business process is needed

defined before using it as argument for isURLAncestorOf.

@vpelletier, this caused a bug, since empty came_from would crash isURLAncestorOf when urlparse is called for this url (https://lab.nexedi.com/nexedi/erp5/blob/master/product/ERP5Type/Core/Folder.py#L517). I think this is a way to solve, I do not know if isURLAncestorOf should be changed also to return something in such situation. 

/reviewed-on nexedi/erp5!89

This ERP5 service worker provides the same functionnality than appcache (nothing more).
No need to activate it while appcache is still the only techno supported by most browsers.

in this context, int index is priority

This caused reports to be skipped sometimes

getOwner returns a python document.

Only support Base_jumpToRelatedObject for now.

fix the keys adding 'portal_type_workflow_chain/'
in _importFile, preinstall and export."

This reverts commit 6f8221b6.

This commit cleaned inconsistent prefix manipulation in
PortalTypeWorkflowChainTemplateItem. It passes the test suite,
however it was found to produce incompatibility with previously installed
business templates. In 'Upgrade Business Templates from Repositories"
there was a diff of PortalTypeWorkflowChainTemplateItems like:
Portal Type Name -> New
portal_type_workflow_chain/Portal Type Name -> Removed
For some reason the upgrade process would remove the chain
without adding the new element.

We are working on a clean solution, but since this needs more testing
I revert this commit for now so that master version does not cause
problems to users.