The workflow method transitions were configured to use a different
guard from the user action transitions.

"Manager bypass" was not set

The default character_set_system is utf8mb3 (>= MariaDB 10.6), utf8 (<= MariaDB 10.5).

See merge request nexedi/erp5!1977

- app does not manipulate data structure anymore (jio does)
- use union storage for multiple masters
- remote slapos masters fetch is done in replicateopml storage repair method
- sync repair method recreates the storage on new master urls, and updates the stored objects accordingly
- add erp5monitor layer in monitoring jio storage

- add notify parameters on controller
- fix form_view custom submit handling

erp5_core: reindex recursively only if indexable children type exists in Base_reindexObjectSecurity.

This is important especially for SyncML Subscription having tons of SyncML Signatures that is non-indexable.

Note: first I tried the change in the restricted python only like :

--- product/ERP5/bootstrap/erp5_core/SkinTemplateItem/portal_skins/erp5_core/Base_reindexObjectSecurity.py
+++ product/ERP5/bootstrap/erp5_core/SkinTemplateItem/portal_skins/erp5_core/Base_reindexObjectSecurity.py
@@ -4,7 +4,8 @@
 # with lots of content could mean hours of non-usable overloaded system.
 type_tool = context.getPortalObject().portal_types
 for portal_type_name in context.getTypeInfo().getTypeAllowedContentTypeList():
-  if getattr(type_tool, portal_type_name).getTypeAcquireLocalRole():
+  if getattr(type_tool, portal_type_name).getTypeAcquireLocalRole() and \
+      type_tool.getPortalTypeClass(portal_type_name).isIndexable():
     reindex = context.recursiveReindexObject
     break
 else:

but I got the following exception :

  File "Script (Python)", line 8, in Base_reindexObjectSecurity
    type_tool.getPortalTypeClass(portal_type_name).isIndexable():
  File "/(SR)/eggs/AccessControl-4.4-py2.7-linux-x86_64.egg/AccessControl/users.py", line 179, in allowed
    if self._check_context(object):
  File "/(SR)/parts/erp5/product/ERP5Type/patches/AccessControl_patch.py", line 44, in _check_context
    return aq_inContextOf(getattr(object, '__self__', object), context, 1)
TypeError: unbound method _aq_dynamic() must be called with Address instance as first argument (got str instance instead)

Plus, remove the duplicate of 'text-align'

This is follow up of commit 0000dee0 (erp5_core: update
mimetypes_registry with shared-mime-info_2.4-5 and media-types_10.1.0.,
2024-09-17), after this change, Products.MimetypesRegistry build regular
expressions with fnmatch.translate, which on python2 produces regular
expressions like:

     >>> fnmatch.translate('*.aaa')
     '.*\\.aaa\\Z(?ms)

such expressions cause a warning in python3:

    >>> re.compile('.*\\.aaa\\Z(?ms)')
    ...
    re.error: global flags not at the start of the expression at position 9

Running this on python3 would be incompatible with python2, because
`fnmatch.translate` on python3 generates regular expressions that are not
valid on python2.

To solve this mimetypes_registry.xml was edited by hand to move the
flags at the beginning, replacing for example '.*\\.aaa\\Z(?ms)' by
'(?ms).*\\.aaa\\Z'

The ssl/x509 were renamed after we decided to change the name of the
holding property sheet during the code review. The code was updated,
but not this form

  Otherwise it gets other unrelated objects from a full text search

This is tested in test_14_multiple_workflow_different_permission_roles

See merge request nexedi/erp5!1982

Otherwise
  https://example.com/foo
would match
  https://example.com/
but not the language-selector
  https://example.com/en/

and not as manager, as some scripts in the workflow have proxy roles, so
it would be nice to test them too.

The CA certificate can be stored on the connector (it is obtained from
the clammit instance).

To store properties related to x509 certificates, used for exemple in
TLS connections

When commiting from ERP5, they are always alphabetically ordered.
So commit the list of property sheets ordered alphabetically to ease to decrease
the number of diffs when commiting from ERP5.

   Fix inconsistency on guard and permissions

   Fixup the inconsistent restart/restart_action transition, that has
     Assignee/Assignor guard in am inconsistent matter.

   Allow assignor have the same permissions and guard than the assignee

   Fix up permissions on delivered state, where the Assignor had no
   permission to view/access accounting period (so deliver by assignor
   only was impossible).

See nexedi/erp5@bcd82831

See nexedi/erp5@bcd82831 (comment 216152)