michelegiorgi / formality Goto Github PK

Hello @michelegiorgi ,

I am a Senior WordPress developer at rtCamp. I saw the codebase and I saw you have limited the code which has no way to extend the plugin and add new fields via 3rd party plugin.

I love to contribute open source plugins. Therefore would you mind if I tweak the codebase and make it easy to extendable via 3rd party plugins?

Please advise me on this proposal. I would love to contribute.

Thanks!

Great plugin!
Please add Recaptcha support.
Enhancement request.

First, awesome plugin! Thanks much for creating this and releasing it freely :)

Bug: If the final page is short, it makes the buttons jump around. This results in that the user has to click the send button twice, which feels weird.

Impact: I am worried some people may not realize this and not actually submit the form.

Workaround: I can workaround this by putting some content in there to make the last page longer, so the content doesn't jump when the right box shrinks down.

Example:

(First part of the video shows the buttons jumping, the second part at 0:07 shows the double-submit)

(Tested in Chrome)

If no limit is set for max text size, it will render the text as NaN. This is slightly confusing to non-technical users. It might be better to not render the wordcount at all in such cases, as it would not be relevant.

I have translated Formality into Norwegian Bokmål, but there is one string in the error valitation form that isn't translateable: "This value is required", when a user tries to progress without filling a required field.

Could that string be made translateable?

Willing to lend a hand with documentation.

thanks @michelegiorgi this plugin realy awesome.
its work perfectly on my website.

it would be great if you add date and time block for next version.

Thq

Hello!

I ran into problems with email notifications while developing on Local by Flywheel.

After investigation it occurred that the reason was in email_content() function, in the line where you're getting the template:

$response = wp_remote_get(plugin_dir_url(__DIR__) . "public/templates/notification.html");

Http request failed because of cURL error 60: SSL certificate problem: self signed certificate

As there are many scenarios where wp_remote_get() might fail, wouldn't it be reasonable just to fopen() the template file from the filesystem?
Why to get it remotely from plugin's own files?

Also it would be nice to have the template replaceable or filterable.

Thanks for your work.

Yes I do!

Thank you for the plugin! And you've made it OPEN too!
Everybody please donate, donate, donate! You deserve it.

And that site. Oh man talk about new age technology for a free, open-source plugin!

I would definitely like for this to support ACF fields in future!

On multipage forms, the more expected paradigm (as an ex-google forms user) is that the formerly-editable fields will be hidden instead of the last page only set to read only.

A nice option for multipage users would be hiding the final form page on success and instead only displaying the success message.

Hello Everyone,

I hope this message finds you well. While I'm not a programmer myself, I am an avid user of Formality and have been truly impressed by the dedication and hard work of the project team. Recently, I encountered a need for a form that allows users to collect payments seamlessly during form submission.

I am not sure about the feasibility of this, but I'd like to share a simple idea. Given that Formality is an open-source project with a global user base, having a single payment option might not be optimal for the entire community. Therefore, I propose integrating the WooCommerce checkout page with Formality.

Since many payment gateways already offer WooCommerce plugins, we could leverage this existing infrastructure. The concept is to use the WooCommerce checkout page in conjunction with Formality. This way, Formality can determine the price based on the form's logic, and users can utilize the familiar WooCommerce checkout process to complete transactions.

I'd love to hear your thoughts on this idea. Please feel free to comment below or give it a like if you find the proposal interesting.

I think a conversational login and conversational navigation by means of a redirect would be two really cool features. Also can't wait for the answer with the video. You should look at the forminator API. I think it would be the most useful to you.

Ciao @michelegiorgi
thanks a lot for this great new forms plugin. Great solution and looks really awesome.
Just a short notice: I went through your demo forms on your website and the browser crashed constantly when testing. (iOS 13.3)

On iPad I had problems when filling out a form because when I enter an input field and the iOS keyboard gets visible, the input field jumps below the visible area.

However I am looking forwared to test formality a bit more. :)

Saluti,

Philipp

Integration with Gutenberg is very nice and conditional fields!

The accessibility issues make it unusable.

• When pressing enter on empty input field it jumps to next input instead of showing a list of errors on top of the form
• On input error, focus should jump to list of errors above the form
• Also screen readers are unable to read the errors because of focus change to next input
• Error not being read to screen readers(errors not associated with input)
• The aria-invalid="true" or the HTML invalid attribute should be set on each invalid form control. This attribute causes screen readers to identify the control as being "invalid" .

Here's a example of a accessible form:

https://wet-boew.github.io/v4.0-ci/demos/formvalid/formvalid-en.html

A common question on forms is the 'legal agreement' type question. In these, it is quite common to have a field agreeing to some legal agreement linked elsewhere in order to submit the form.

Unfortunately the 'message' field does not allow HTML

Workaround 1: You can enter a link in Label, however, it is not visibly a link (underlined).

Workaround 2: Put a text block immediately before or after the question with the URL. Somewhat less ideal since this forces a new paragraph, but it does render the link with underline.

There doesn't seem to be an obvious way to display a field based on the input of a conditional logic field.

for instance if you have a multiple choice field:
"What are you interested in?" with options "a" and "b".

and then want to display a field "where" only if the user has selected "a", there doesn't seem to be an obvious way to do this.

Simply entering "a" into the conditional logic box results in the field still being hidden.

After migrating a site to a new server, the export is not working anymore.

The reason is simple:

• Problem Formality is writing the full server path into a file: /wp-content/uploads/formality/storage/.htaccess
• -> this path often changes, when moving to a new server or provider

Better:

Redirect to some REST-resource with only the filename. Avoid using the full server path.