Whenever used via activity nodes, it is not possible to discover IP of the server via portal absolute url.

See merge request !1478

   Only Person could include getFirstName and getLastName, so implement a fail-safe in case Login is inside a Computer or any other document.


(cherry picked from commit f7694fbc)

OSOE website is not necessarily part of standard configurator so only adjust if it is indeed installed.

See merge request !1476

(cherry picked from commit 1ad44735)

Suite

Module erp5.component.document.erp5_version.ERP5ProjectUnitTestDistributor, line 326, in getTestSuiteSortKey
  wanted_test_core_quantity = PRIORITY_MAPPING[test_suite.getIntIndex()][1]
AttributeError: getIntIndex

Avoids the infamous 1024 file descriptor limit. No functional change
expected, as it seems unlikely this bug ever triggered on waitress-managed
file descriptors.

When using report sections with title, this is supposed to create outline
in PDF, but this seem to became broken somewhere in the last 10 years.

This repair by using text:h instead of text:p and by setting
text:outline-level

To activate it, we have a preference to allow users display or not ERP5 tools

This report proably needs to be updated more, but at least use proper
getAggregatedAmountList so it no longer crash

It was not enabled in ERP5JS had minor issues

See merge request !1473

match date field id in listbox's column

When jumping from a product to multiple transformations, there was no status
message and also ignore_hide_rows was not passed, which made this jump non
functional when the corresponding preference was enabled.

Same as 896e5cc8 (Allow to jump from Product to its related Transformation
using it as Material as well., 2011-12-13), but for Component.

`object_report` and `object_exchange` action categories are only enabled
in erp5_xhtml_style. Use the `jio` equivalent categories so that the
generated report is also enabled in ERP5JS.

OfficeJS use another mechanism for actions registration, so duplicate
actions defined on the portal type is not necessarly a problem, as long as
all actions are not registered in the same app.

See merge request nexedi/erp5!1469

For some reports displaying transformations result to end users, it's much
better to have amount ordered in the same order as the model lines.

AmountGeneratorMixin was already sorting the lines, but the order was lost
during aggregation, because we used a dict, which on python2 does not
retain order. Switch to using an OrderedDict to keep the order.

This makes RSS reader somehow usable for support request RSS.

One important think to keep in mind is that because of a bug in how URL characters are (not) escaped in the dialog to edit character is that editing the feed URL should be edited from knowledge pad module, and not directly from front page. Also this should be edited by clicking Edit button, not by pressing enter.

See merge request nexedi/erp5!1467

See merge request nexedi/erp5!1470

See merge request nexedi/erp5!1455

To "mark as read" and open preview, the front page gadget uses the "md5" key,
which is calculated from "link", but we can have multiple entries for the same
links, like it's the case for officejs_support_request app.

Instead, use guid or id if available, this is what RSS/atom use for this purpose.

See merge request nexedi/erp5!1465

so user can login

Instead of expecting exactly actions with "preview" or "view" name, take any
action which name contains "preview" (or title is "Preview") or name is "view".

This makes it easier to include support request applications in different
applications, where the default actions might have a different name. This also
fixes the preview link for File portal type, because there was no "preview" or
"view" actions for File.

We received a few support requests from users who are able to change their
password but not to log in afterwards. These users probably copy and pasted
their user name with an extra leading or trailing space. In the reset
password dialog, these spaces are stripped, because Formulator by default
strips the input (unless "whitespace preserve" is on, but we usually don't
set it except in text areas).

Historically we have been completely avoiding the extra spaces and made the
login/user_id case sensitive, because login and user id were the same thing
and there have been issues when looking up user id in mariadb because of
mariadb collations, so we took the easy way of saying "logins are case
sensitives and spaces also mater", but with separate login / user id,
this can be revisited, because the login is only used to check the password
and find an user ID.

Stripping spaces from logins is a common thing these days (google, twitter,
facebook strip logins) which simplifies user experience and reduces support.

The risk of conflicts seems very low, if users are created with ERP5 Forms
Formulator already had stripped the login anyway. After this change in case
of two user names ('alice' and ' alice ') conflict, none of them would be
able to login.
We keep compatibility with users with trailing spaces, so if there is only
a user named ' alice ', without other users that would conflict (for
example 'alice' or ' alice'), this user remain able to login anyway. This
last part is probably not so important in reality, it is for compatibility
with testPasswordTool.TestPasswordTool.test_login_with_trailing_space

* Fixes https://erp5js.nexedi.net/#/bug_module/20160609-11B02E6 and https://erp5js.nexedi.net/#/bug_module/20210517-F12266
* Support ERP5JS
* Improve test coverage
* Small CSS changes
* Fix bug editing business process when erp5_graph_editor was installed 

See merge request nexedi/erp5!1461

Until now, portal_sessions was only reliably usable when using a family with only one zope node, because the session data was using RAM cache.
When used by authenticated users it was more or less usable, because of haproxy
sticky cookie that we set for authenticated users, but for non authenticated users
this was basically unusable.
This was especially a problem for CaptchaField, for which users are generally not
authenticated.

This changes portal_sessions to use a distributed cache, which brings several
differences:
 - sessions are now shared between all zopes of a cluster.
 - storing ERP5 temp documents is still possible, but modifying a temp document in
   session does not automatically save the changes in session, for next session read
   to be using the modified document it's required to save the document explicitly.
 - session respects transaction semantics, changes are only persisted in session when transaction commits successfully.
 - `portal_caches.clearAllCaches` API no longer clear all sessions.

See merge request !1451