Also, add an XXX about manage_test annoying behaviour.

Avoids the double-nonsense of looking the document up by path inside callee (!)
using the catalog (!!).
Also, follow naming conventions: variables containing documents should end
in _value, not in _object.

Vincent Pelletier:
- commit message
- remove unrelated change
- squash similar similar-intent commits even though they apply to
  different BTs

These methods must not be called synchronously:
- they can break catalog by not being careful enough about other
  reindexations which may happen in parallel. See the serialization_tag
  mechanism for more.
- indexation gets executed in the security context of the user causing the
  call, which may lead to an indexation result different from what happens
  when indexation happens with an all-accesses user.
These lines of code (some even commented-out) give a bad example. Replace
them with safe equivalents.

…r in (multi)relation field

/reviewed-on nexedi/erp5!556

Such tables are not visible in the ZMI (which is arguably a bug on its
own, although the ZMI is deprecated), but even accessing the setting
tab is broken as it runs these methods.
This change at least allows accessing stuff to start fixing.

The order in which messages are returned by getMessageList is undefined,
and manageInvoke refuses to execute messages which are blocked by their
dependencies. Notify depends on Alarm_runUpgrader, so it must be explicitly
ran second.
Also, avoid listing activities twice.

Here, we expect exactly two activities, one of each type, and just do not
rely on these being listed in any order (...in theory, as this is actually
assumed by the next iteration on getMessageList, but this is a separate
issues).

and fix pdf worker path

Create 2 new bt5:
erp5_minipaint for image editor gadget
erp5_jquery_sheet_js_editor for web table editor

OfficeJS bt5: erp5_officejs, erp5_officejs_jquery_app, erp5_officejs_ooffice, erp5_officejs_ui_test

The current and most-updated WebIllustration_view form is in erp5_dms, alongside the Web Illustration portal type declaration

Same reason as in 2115abc3.

Editor Fields were used to inject HTML, but the fields were
not pointing to Editor Field directly. They were pointing to
Base_viewWebFieldLibrary/my_text_content which is designed to
use a real editor (Gadget Field now) instead of inject HTML.

Some fields were changed to point to Editor Field in order to
inject HTML.

Base_viewTestPageFieldLibrary/my_embedded_text_content is also
changed to use a simple text area, like it should be originaly
designed for.

-  hal_json works minimally (but still) with Selections
-  ERP5 Report gets rendered
-  display Title of Forms

security calculation checks the validation state of the Assignment, but it should also check if it is expired or not started yet.

This merge request applies fix, extending tests to re-produce and test the situation.
Also, a cleanup in erp5_core: extension.erp5.StandardSecurity.

/reviewed-on nexedi/erp5!548

This is equivalent to work done for Leave Request, at:
185285c4
(merge_request 493)

Follow a simple / non-simple approach, like for Task and its lines.

In default case, user would need only one Presence Request Period, which can be edited directly on PresenceRequest_view. So, in this case, hide the Listbox containing the Presence Request Periods and have default_presence_request_period being created / edited on background, which will acquire quantity, resource, start_date and stop_date from what is set at the view of the Parent.
In case one or more Presence Request Period are added manually, user would get listbox with sub-objects, and editing should be done directly on them, i.e. fields like my_default_presence_request_period_start_date will be disabled fromPresenceRequest_view.

Additionally, now Presence Request has its own:
start_date: equal to the minimum start_date of all Presence Request Periods
stop_date: equal to the maximum stop_date of all Presence Request Periods

These values are set by interaction on Presence Request Period, triggered on setStartDate, _setStopDate. This helps so that presence_request_module listbox can have sortable dates.

Commit contains also test

/reviewed-on nexedi/erp5!541

/reviewed-on nexedi/erp5!551

It is defined in Portal Type and projects do use versions of it.
Add it as empty in generic implementation, since otherwise the portal type
is unusable (cannot create new documents)

preferences icon (main menu) : f1de (sliders)
sort asc (icon in listbox header) : f160 (sort-amount-asc)
sort desc (icon in listbox header) : f161 (sort-amount-desc)
configure icon (new "configure" listbox button) : f0ad (wrench)
hide (hide button in listbox) : f2a8 (low-vision)
worklist (main menu) : fOae (tasks)
link (relation string field) : f090 (sign-in)

/reviewed-on nexedi/erp5!550