-
Notifications
You must be signed in to change notification settings - Fork 908
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
adding more fields to a form #9
Comments
Hi @HGBeary, thanks for contacting us! |
Thanks for the quick reply! I've prepared a form for volunteer tutors to Henry G. Beary On Tue, Dec 1, 2015 at 2:25 AM, Nelson notifications@github.com wrote:
|
Ok. Understood. I will need to slightly modify the form handler to achieve this. |
Wow...thank you so much! Tomorrow would be perfect! Attached is a screen Henry G. Beary On Tue, Dec 1, 2015 at 8:35 AM, Nelson notifications@github.com wrote:
|
@HGBeary i've updated the form handler to be generic so that you can add any fields to the form and collect any data in the Google Spreadsheet.
|
Thanks for the updates! I've got a minor (I hope) issue: if I use I get the message page but the data does not get emailedor put into the spreadsheet. If I don't use the id=gform I get a page of data but I also get an email and the spreadsheet populates. What am I doing wrong?? Here's my test page without the id="gform": http://lvg-ct.org/Tutor-Form-monthly-report-Gmail.php Thanks again for Henry G. Beary On Thu, Dec 3, 2015 at 2:37 AM, Nelson notifications@github.com wrote:
|
The also, consider the addressing any markup validation issues: https://validator.w3.org/nu/?doc=http%3A%2F%2Flvg-ct.org%2FTutor-Form-monthly-report-Gmail.php to prevent issues. |
Thanks for the reminder to clean up my html! The attached screen capture Henry G. Beary On Thu, Dec 3, 2015 at 4:22 PM, Nelson notifications@github.com wrote:
|
It appears That Github does not allow images to be uploaded to issues as email attachments... Please manually upload it, or send us the link to the version of the page with the gform I'd. Thanks. |
When I run the page in the Chrome debugger I get the following error on Uncaught TypeError: cannot read property “style” of null Henry G. Beary On Fri, Dec 4, 2015 at 2:02 AM, Nelson notifications@github.com wrote:
|
Ah... that's because you have changed the DOM significantly. You are serving the page using a PHP-enabled server, this script was meant to be for static pages where no sever interaction was permitted... You can still take advantage of the script while serving the page from PHP, but you have much more power than our original constraint dictated. If you are going to serve the page from your Dreamhost server, and alter the page's DOM, it might be worth customising the |
How can you add a new field that has drop down options or allows users to select more than one option |
@nelsonic I've added a checkbox input to my form and the corresponding column to the spreadsheet - everything else is working fine, but no matter if I check the checkbox or not, I'm getting the same value reported to the spreadsheet. Do you know how to accomplish this for a simple True/False value? |
Does our OP have any more concerns on this issue? If not, please close! Hopefully you were able to get something working, but static pages are best. For other posts, please see #31 on the checkbox input (new features/bugs should be separate issues), and same for a drop-down multi-select. I can take a look at these when I have more time. |
The original issue has been resolved with the support for more form fields. Again, please post in other issues if particular fields are not working for you! |
@divyats6550 This issue is >3 yrs old and I do not believe has anything to do with captcha. We have had issues around captcha if you search closed GitHub issues. We implemented a Honeypot technique and recently made it the default experience for all forms as well (that utilize the JS that is). |
I would like some info to customize "html-form-send-email-via-google-script-without-server". I need to add additional text labels but it's, apparently, not as easy as it looks!
The text was updated successfully, but these errors were encountered: