The Assigments are only relevant if the User is based on Person Document, on SlapOS, an user come from a Computer or a Software Instance Document. This change makes the document compatible with other kinds of Users, as Assigment is overkill for Non-Person cases, as the presence of ERP5 Login is enough to determinate the User existence. 

The other alternative would be re-factorize to not duplicate code, which seems not the intention of how this code was written. 

/cc @jerome, @kazuhiko 



/reviewed-on nexedi/erp5!458

Simpler, and reduces the exposure of exc_info (which can be tricky to use
in other contexts).

Unlike Medusa, WSGI does not do it.

Both the dummy method_id and the actually-used grouping_method_id.

Without this commit, it felt back to the timerserver egg.

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 !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 nexedi/erp5!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.