HAL JSON uses JSON, which uses UTF-8, but properties of ERP5 documents
does not enforce any specific encoding, so if we happen to have
documents with string properties that are not UTF-8 compatible, they
could not be queried with HAL JSON (json.dumps was raising UnicodeError)

This pre-process field default properties and document title to make
sure they can be serialized as json. This assumes that configuration
(form definition, actions, ...) will be valid UTF-8, but just does extra
effort to make sure "broken" data can be displayed without error.

/reviewed-on nexedi/erp5!928

ZODB Components: 'Migrate Components from Filesystem to ZODB' view: Fix ListBox to display selected ones first.

In this context, 'selected' means classes found by introspecting Portal Type
Class MRO. This was not sorted properly only for filesystem Products.

ZODB Components: Do not automatically validate when importing from FS as imports have to be adjusted manually.

Besides not being actually needed, checkPythonSourceCode() was called on all
temp_objects created for migrate_component_from_filesystem Business Template Action.

/reviewed-on nexedi/erp5!929

['Person: 372 doc/hour; SaleOrder: 132 doc/hour;']
Thus adjust accordingly. Do not mix http and https.

/reviewed-on !926

Editing instance parameters will automatically trigger instance update at node and there's no need to stop / start instance.

evaluated before timeout and thus causing unexpected AttributeErrors
later.

password pair generated (in some cases this might happen after frontend
generation leading to 403 HTTP error codes in bootstrap code.)

Cleanup conditional code.

code will fail with :
"local variable 'user' referenced before assignment".
As callee is handling the possibility of delayed frontend and / or
instance creation this is perfectly fine.

To allow viewing the wallpaper

User can send the error page to allow understanding the issue.

[erp5_hal_json_style/erp5_web_renderjs_ui] Render the form directly after a successfull call to Base_edit

This decreases the query number from 2 (POST to Base_edit -> redirect + GET to render the form) to 1 (POST to Base_edit -> render the form) and so improve the speed of ERP5JS.

To achieve this, apply so fixed in ERP5JS:
* rerender the panel/header after Base_edit (router is not called in such case, so, it must be manually called)
* fetch the page title from the form calculation (as the document context is not recalculated, only the form)
* force deleting the current field values, used by the relation field listbox search

This commit also force the full page refresh when diplaying a new document, in order to prevent keeping field values from the previous one (so bugs used to occur when using the previous/next document pagination).

Thanks to Tristan Cavelier for his work on this topic.

With a minor update of ghostscript, we again had weird changes:

AssertionError: 'ERP5 is a free software.\n\x0c' != 'ERP5 is a free software.\n\n \n\x0c'

URL convertion has to be done by javascript so that the code become useable for officejs.

This reverts commit 9f8dd82c.

This dialog is used by erp5_hal_json_style and select column should not be displayed there.

This feature of configuring openssl to disallow issuing more than one
certificate for the same common name as been disabled in SlapOS'
certificate_authority recipe, but instead of fixing this, we decided
to disable this test until the tool is completly rewritten using
caucase.

MySQLdb relies on garbage collection to close the connection. Relying
on such asynchronous event as the garbage collector is never a good idea,
and this can cause issues when the transaction associated with the
connection is started: because the connector is being replaced, it will
never be properly aborted. So do not take chances and do not leak open
connections: always close it.

So that it's more apparent that we are not leaking a potentially active
transaction on that connection.

The same error code can be used for different causes. Specifically, it can
be used for SQL-level syntax error (which this code intended to handle),
or it can be used for fulltext syntax error (which makes this code raise).
Also, drop forced-reconnection, because this means a still-established
connection make be kept around and completely detected from current
transaction, which may cause a database snapshot to be kept indefinitely
(actually, until mariadb's timeout), in turn causing performance issue
because of associated InnoDB snapshot.