url
- corresponding test added

- improve OfficeJS applications by reducing the quantity of code to be written and reuse the ERP5 configuration (portal_type, actions, forms, etc.) instead to generate the app

  The API changed on the slap, this commit follow up the changes.

Which is useful when debugging tests

Some files in the Skin Folder was not deleted by mistake

/reviewed-on nexedi/erp5!914

'only_visible' in essence checks 'Add portal content',
But here we care for View permission really, since user can have worklist in a document
even if he/she does not have the rights to add content to the module.

otherwise naturalWidth/naturalHeight may be 0

Domains are not meant to display too many documents at the same level.

Domains are not meant to display too many documents at the same level.

Domains are not meant to display too many documents at the same level.

/reviewed-on nexedi/erp5!830

Avoids accumulating useless connections when a single test file contains
multiple files.

Sorting on all documents is a performance killer.

In case no query parameter is available, do not trigger any allDocs
calculation and do not display the listbox, as results would be
meaningless.

For instance, typing a backslash in a relation field does not crash the ui anymore.

/bug #20180123-D78557
https://nexedijs.erp5.net/#/bug_module/20180123-D78557

This property is only conditionally set, which causes distracting error
when something goes wrong. If we really want to check that the expected
code path was followed there has to be a better check and a more debugging-
friendly error than an AttributeError.

While such activity parameter combination does not make sense, it is
technically possible to spawn activities with a group_id set but without a
grouping_method_id.
The consequence is zombie activities: they never fail, do not prevent other
activities from being executed, but and are permanently run on the node
which reserved more than one because:
- all but one activity is in MESSAGE_NOT_EXECUTED state, forcing an abort
- finalizeMessageExecution does not understand that MESSAGE_NOT_EXECUTED
  activities may not have failed, and itself fail while trying to detect
  the failure type (ConflictError vs. others), failing to free & postpone
  the activity, in turn failing to bring it to eventually permanent failure
  state.
Make those conditions consistent, and use tuple-unpacking to detect any
future inconsistency much earlier, simplifying debugging.