Skip to content
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

Remove advanced form functionality #42

Open
kaittodesk opened this issue Apr 11, 2020 · 3 comments
Open

Remove advanced form functionality #42

kaittodesk opened this issue Apr 11, 2020 · 3 comments
Labels
question Further information is requested

Comments

@kaittodesk
Copy link
Member

Plugin's advanced form functionality is very limited:

  • no way to build multiple forms, i.e. one HTML applies to all forms;
  • enabling advanced forms overrides simple forms;

I propose we remove advanced form functionality from the plugin and direct users towards our Contact Form 7 plugin - https://github.com/sendsmaily/smaily-cf7-plugin/. This may require a major release.

@kaittodesk kaittodesk added the question Further information is requested label Apr 14, 2020
@kaittodesk
Copy link
Member Author

As an alternative we could also suggest using HTML widgets. This way user does not have to install another extension.

@ghost
Copy link

ghost commented Jan 15, 2021

We could add a settings page to create and manage new forms. Form could be specified from a <select> field in widget options, with the default value being basic form.
This would allow all users to keep already saved forms and would grant experienced users more flexibility.

@kaittodesk
Copy link
Member Author

This is what I am actually trying to avoid, because it would make the upgrade path of the plugin more difficult.

We are planning on having form builder built into Smaily, and all of the custom form functionality would be provided by that feature, i.e. user would be able to select a form built in Smaily to show on their website. If we'd add form management functionality to the plugin (even if it is as basic as storing HTML in the database), then we would need to have a plan in place for what to do with the forms managed by the plugin when form builder is generally available, and can be integrated with the plugin. At the moment I cannot see a good way to get rid of the plugin managed forms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant