Thanks in advance. I have been very satisfied with other WebAssist extensions. I bought the WebAssist Form Builder after using Form2Mail from Hot Dreamweaver successfully for several years (our clients didn't like the way the emails looked). I was thinking it would be easy to use and intuitive, but I can't find the answers to some very basic things about the forms. 
Oh Doug, I feel your pain. I'm just a user like you, and I'm sure Jason or someone from WA will answer you and be as helpful as he has been to me. But I just had to tell you that I'm glad I'm not the only one who feels this way and maybe I can share some of what I've learned in the last couple of weeks.
Even uploading a form completely using presets, the form previews like it's supposed to look. But when I upload it in a php page, I get all of the prompts (like "Invalid format. Please enter a full email address") showing up.
You have to upload the SpryAssets folder. The form is using Spry so those must be uploaded as well if you haven't already uploaded them for some other pages.
I can't find a quick way to get rid of the "Contact Me" text at the top (I already have that as an H1 tag on the page, I don't need it over the top of the form too).
That field is one of the options in the Formbuilder. On the Form Details page when you Edit the form, what you want the Submit button to say is above where you edit the form fields and first Fieldset has the Header (e.g., Appointment Request, Contact Me) in the Label field. That slipped by me a few times too.
I get a field called "Additional Notes" with a bunch of the old "Lorem ipsum dolor sit amet" stuff.
When you create your form, there are two files you want to be aware of. The first is the template that's created for your form. They get named things like template_5.php which I find confusing if you're making a bunch of forms. So I rename mine after the name of the form. You can edit that form like any php page in DW, including removing the Additional notes or changing the font size. (I know you can change the font size in the form creator too, editing the CSS, but I find those choices to be unintuitive for me since they don't show me which they apply to. So it's easier for me to edit it here.).
Btw, another lesson learned. If you edit your form and then tell the builder to not create another template (because you already have this one you worked on) it strips out the mailing code in the waue_formname.php file required for the form to be sent. So I just have it build another template based on the on one I already have, then delete it and go into the waue_formname.php file and change it to point to the form template I've named after the form.
That brings me to the second file you need to know about - waue_formname.php. Thankfully this one is named after the form you created so it's easier to find. Go into code view and look for
$MailBody = $MailBody . (GetFromPage("templates/Repair_Request_template.php"));
only it will say "templates/template_10.php" or whatever, and then change it to the name of the template you want. This might seem like busy work, but otherwise I've found if I just keep using the ones formbuilder makes, I end up with all these templates that are not in use. Maybe I'm missing something here, and Jason can tell me where I'm going wrong. But if I don't tell it to make a template, this area of the code on the waue file is blank and my form doesn't get sent.
The last thing I'd share with you is that when you get your form in the mail you will find it has fields you don't probably want, like the button name, or hidden or other fields that are on the form but not needed in the email. While you are in your email template find the line that says
$removeIncludes[] = "Security";
and then copy and paste it changing out "Security" for whatever other fields show up on your form that you don't want.
When I edit a form, do I have to re-upload everything in the WebAssist folder?
Once you have your Spry assets and the webassit folder uploaded the first time, the only files I've found I need to re-upload are the file with the form, the template and the waue associated file.
As long as I'm sharing, another thing I've noticed is that while I'm first creating a form, when you go into Form function and click to send the contents by email, there are a few things that are helpful to be aware of. If you are sending to a recordset, and click on the lightening bolt, I have not found that to really work. I either get no mail or only the first one in the set. I have to click on the Edit button above the Send the form contents by email, then click on the To button (not the lightening bolt) and add it as a recordset loop. That makes sense when I see it, but it took me a bit to realize it and there's nothing to tell you that clicking on the To button gives different options.
Also, if you are sending an attachment from a file upload field, clicking Save Uploaded Files on the first screen is not enough. Ideally you could go into the Edit screen and click on the paper clip and then Add. Select Entered Value, then the what you need, but what you need (Upload Files) isn't there yet. So you'll have to save your form at this point, and then edit it using the Server behavior of Universal Email. (Don't make the mistake of thinking you can click on Submitted file on this screen, because that won't work. I'm not sure what that's there for, but this isn't it.)
So, after you save your file, when you go back into the sb Universal Email to add the file you want to attach, you click on the paper clip, then select Entered Value, use the lightening bolt to go to Upload Files (Upload) and then select the Server Directory. Copy the Code info then select Server File Name. Click OK and then put your cursor in front of the Server File Name code and paste the Server Directory code.
Now when you go to save all this, is when you'll need to remember that you have to just create another template, and then go back to the waue file and put in your template. Unless you don't mind having a bunch of unused incremental templates who's name tell you nothing about what file they are associated with.
I love the form builder tool, and now that I've learned some of the basics, it has saved me a lot of work. But I'm not a coder so some of this was not very intuitive to me. I'm glad I'm not the only one. :)
I hope this is helpful and I haven't given you any bad info. Jason is really helpful so I'm sure he'll "set me straight" if there's places I've led you astray. But this is what I've found and I hope it's helpful to you.
