If a transaction has the same source section and destination section, there was a risk of showing the wrong side of the transaction. Test that both section and nodes are the same instead. There is still a risk, of showing something wrong if source and destination are also same, but such transaction would be non sense anyway.

A previous operation might have poluted the request

If a sub field has a tales expression for it's value, need to use it firstly.

The idea to clean input after submit:
in pt form view editable gadget, after submit, it will check if there has a field which
should regenerate, if yes, it will ask it's parent gadget to provide new erp5 site info,
then use it to regenerate sub field

Fix bug:
when a field's enable value is defined by TALES, it'll not be in group list

sometime web_section's type is string

Also commit the datetime field used by proxy field with the timezone
properties defined in its sub-form so that proxy field work when
using these new parameters

Integrate replicateStorage optimization

[erp5_web_renderjs_ui] allow button menus (multiple forms or buttons) in header besides single buttons