website_form_editor does not depend on project but apparently just
assumes it's been installed and the form construction tour uses it to
change the "action" selection to issues then (back to?) sending an
email.
This ends up triggering two additional "change" events on the email
option, which adds a new email_to field every time, blocks the
submission of the form (since they're all required and only one is
filled) and breaks the tour.
On "toggle_email_to", only add an email_to field if it's not already
present.
website_form_editor does not depend on project but apparently just
assumes it's been installed and the form construction tour uses it to
change the "action" selection to issues then (back to?) sending an
email.
This ends up triggering two additional "change" events on the email
option, which adds a new email_to field every time, blocks the
submission of the form (since they're all required and only one is
filled) and breaks the tour.
On "toggle_email_to", only add an email_to field if it's not already
present.
The new RPC API calls the '/web/dataset/search_read' route for a
search_read instead of '/web/dataset/call_kw/model/method'. The
first one returns an object with keys count and records, whereas
the other one only returns the records.
When converting the code in website_form_editor to this new API,
one forgot to update the handling of the RPC result.
The website_form_editor code was adapted to the new rpc methods, but
this concerns class that do not have the rpc method. We use the
callback argument to specify a given ajax method
Use performModelRPC instead of Model object or use ajax if performModelRPC
is not available
nb: EventDispatcherMixin include now the custom_events managment instead
of widget[REMOVE] web.dataModel
Automatically whitelist fields added to a website_form through the form
editor.
Ideally fields *removed* from a form should be removed from the
whitelist, but since we don't/can't keep track of the website's form,
there's no way to know if a field is needed by multiple forms and thus
no way to remove them.
Plus that would require way more source-tracking than just whitelisting
all the form's fields, I don't know if snippet widgets can track the
removal of elements from a page (easily anyway).
- Prevent user from removing the Submit button
- Renamed Success Page into Thank You Page in the modal
- Destroy the snippet if user closes the very first configuration modal
- Replaced display_name field by subject in tour because the former was readonly
- Changed "Editor" to "Builder" in module name
- Removed field domain, need to fix it later
- Removed lingering console.log
- Require recipient e-mail
- Added missing Date field
Contains the new ajax post function introduced by e8d58dd
in the community version of web that comes from mdo's
original code and that I was not able to get rid of.
Christophe Simonis