Form content not being received

There should be no limit to the amount of fields. However my UI is somewhat experimental in that it 100% JavaScript
I have noticed that larger forms causes the interface to have delayed responses. But I am working on this to sorted I’ll the field bindings.

With the content issue, are you using field tags %field% in the email body?

The saved form does not correspond to what I am seeing on the page:
https://df7.84e.myftpupload.com/checklist-forms/pet-behavior-screen/
For item 24, the label is hidden but the field name (comments24) shows up as the default text in the textarea box. The saved form has “Enter comments” as the default text. I also have two additional items, 25 and 26, in the saved form which do not show up on the page.

On the content issue, I am not using the auto responder. I am referring to the posted form content that is sent to the mailer recipients. The recipients get the e-mail, but there is no posted form data.

could we have a chat on skype? david-cramer
or email [email protected]

Hello David Cramer,

Almost the same case. Are those received mails not contain the form data? Because I am getting blank mails, even though there were data put in the field. Moreover, I am getting the CSV file when we checkmark Attach a CSV version of the submission.

It would be great if we also get the form data in the mails.

Thanks for your effort man.

I’ll take a look and reply with solutions shortly.

Problem was the emailer message was not filled in. hence no email body.

I’m adding in an auto summary if the mailer is empty and including a tag {summary} to indicate an auto build of the form submission.

As with the limit of fields, my builder is config heavy: it has many options and config inputs. PHP has a default input limit of 1000 so a large form can go over this limit. see max_input_vars

To solve this, you can increase the setting in php.ini file.
This however is not ideal as not everyone can modify it and personally it there for a reason so I don’t think it should be touched.

So what I have done is have it build the form config object into a JSON string and submitting it as a single field. Problem solved. However, there is now a potential problem of max_post_size, but that is by default 2MB which is unlikely to be a problem.

The update will come later today or tomorrow. still sorting a few issues on it.

hmm.. I could understand a bit of it.

Did you mean that if we place {summary} in the body of the mailer, the filled-in content will be fetched properly?

Excellent. Kalyan, what David is saying is that if you leave the e-mail body in the mailer blank, all of the form data will be sent with the e-mail. Or you could write a custom message and include {summary}, and the form data will be sent.

David, I would suggest you return the field name and the field value.

I will wait and test the field limit issue when an update is published.

Thanks for your willingness to enhance your plugin.

The {summary} tag works great. A big help for returning data from long forms. The issue with the number of fields has also been resolved.

Thanks!