-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Form Builder action 'save' doesn't seem to work or trigger onSave #1058
Comments
I have the same problem :S |
@harpsicord86 Hey Steve! If your goal is to show form render, here is an example how you can do it:
You should use your own external save button.
|
Hi @ahmedsu thanks for the tip! But all I've been trying to do is to capture saving the form at build if the user closes the web page down. I thought there was an elegant way of doing it but there ain't... I've used the getData() action to get the json of the form to save through ajax. Honestly, I thought save() would have called onSave() :-( |
@harpsicord86 You could use
|
Could you tell me how to trigger onSave? I am trying to mimic the save action button behaviour by calling
Is there any way to replicate it? |
onSave will now be called when save is called from the api. |
## [3.4.5](v3.4.4...v3.4.5) (2020-08-23) ### Bug Fixes * onSave not called when save called from the api ([d607b02](d607b02)), closes [#1058](#1058)
🎉 This issue has been resolved in version 3.4.5 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description:
Following the documentation at https://formbuilder.online/docs/formBuilder/actions/save/ this function does not seem to do anything. It also does not seem to trigger onSave when used. Could you provide some guidance on this please?
Environment Details:
Expected Behavior
Running formBuilder.actions.save() would trigger onSave in options.
Actual Behavior
Running formBuilder.actions.save() actually does nothing.
Steps to Reproduce
add onSave as part of options and add an alert or console.log to function. Run formBuilder.actions.save() after form builder is initialised
The text was updated successfully, but these errors were encountered: