zackmathis
Forum Replies Created
-
Thanks! That fixed it. It looks like the old form had a lowercase “yes” throughout while the new one needed an uppercase “Yes” to work properly. I ended up exporting the old form, find/replacing yes->Yes, and uploading a new form.
Would it be possible in the future to allow code imports at the form level and/or edit the form in the text view that the export generates? I realize typos, etc. could quickly break forms and that an editing interface limited to clicks helps reduce that type of error, but for situations like this and not having to go through the process of rebuilding forms and relinking/transferring data to new Google Sheets (or other integrations), some users may find it useful.
I appreciate the help, Patrick and Predrag!
Hi Predrag. This link should work:
https://drive.google.com/file/d/1QQrj5t33a4WFhpWeAdV1nlRn-qvxYXNs/view?usp=sharingHi Dimitris,
Here is one of the forms that is having this issue:
https://drive.google.com/file/d/187bw1P-TuLWKz8WwD8lygRLW-A4_fa7_/view?usp=sharingThat looks great! Thanks, Nastia!
Upon further consideration, the text wrapping in email isn’t that big of a deal. With our other form plugin (FormCraft), the messages come through formatted to match the width of the <div> style of the current form.