These are completely useless and create conflicts with VCSs.

because ID should not contain whitespaces.
This reverts commit e6cd717e.

Publishing "activate" is generally harmless, but creates (with current
publisher code) two failing activities, causing unnecessary noise.

...when COLUMN is not a valid column (hence mutated to a STRING_PREFIX
token at lexer level).
Kudos to Tristan for triggering this bug.

insertbefore instead of insertBefore.

Finally removes the need to hardcode transition id when it's the same as
current transition (which should be the case in the overwhelming majority
of transitions).

No change yet, just to have verbatim code for easier comparison.

Otherwise fmt_data lookups becomes slower on each iteration.
Also, reword patch comments to be still descriptive when moved a bit
further from involved code.

On sites with more than one Zope, this code was causing the cookie to be
bumped each time a form is rendered, causing unneeded cache misses and
slight ZODB bloat (estimated around 100B per form view).

jquery.validate enables checkers which have the name of an
input field type, which just cannot work with password validator
as it has a mandatory parameter, and is not intended anyway.

Also, document include_context parameter.
Also, rename category_id into use_relative_url (the new parameter)
to make it clear more than single-level is supported.

Using the legacy API was broken and this is also to prepare
DocumentationHelper and ClassTool removal.

Some Constraint Property Sheets and Views in core bt5s were defining
properties whose Portal Types (and sometimes their Views as well) were
available in a non-core bt5s.

BusinessTemplate: Get rid of spurious warning when skipping update of Local Roles for non-ERP5 objects.

- Do not enable on all password fields
- Allow specifying strength metter for a given field
- Allow customising password validation rules by changing properties
(allows different rules in the same page)
- Login similarity check can be done by adding login as a sequence
or blacklisted word, as desired
- No hard rules of what a strong password is, instead use a reward
system for using varied characters & character classes, reduced
when password contains widely known sequences or too common
passwords.

erp5_autocompletion_ui: Add JS ERP5Autocomplete() parameter to transform text before sending AJAX request.

For example, if one wants to uppercase/lowercase the value entered by
end-user.

erp5_autocompletion_ui: Autocompletion property value set to the field should be the one queried from the Catalog.

erp5_autocompletion_ui: Consider that description may not be needed, thus only one line, the label, is displayed.

Possible through defining a TypeBasedMethod (PORTAL_TYPE_getCompletionDict)
returning a dict serialized in JSON by the calling method, or otherwise
overriding fallback script (Base_getCompletionDict).

erp5_autocompletion_list: Move away generic JS code from RelationField as it should be reusable anywhere.

Limit the number of results to 15 instead of 20 as it seems to be enough (taken from an existing customer project).