On export in WFB you get the following code:



Can this code be shortened to just be this:


Will the form still work correctly?

Next up on my list...
Is there a way to put the form into a page in SCCP without it being in an iframe tag and have it show up on the page?

I use it like this all the time.

Thanks, I thought it would be ok.
By chance do you know just what purpose the contact_us.php files has? It is generated by WFB, but if just using the shortened iframe code and directly referencing the contact_us.html skips it, what is it for?

I'm not an expert on anything that has to do with PHP, but I would say don't delete that one. The HTML file contains the "html" of the form, but the functioning of the form is on in the HTML, it's in the PHP and .js files so I'm sure that the PHP file has some of that functionality in it for your form to work.

Your correct Jo the myformname.php needs to stay. It's actually the backbone of the form processing. If you look at the top of your myformname.html you will see the form action="myformname.php".

I see it there. Was not looking for it before. So then directly referencing the html like this as Eric posted:
Is not a problem with the functionality of the form.

Then any ideas as to the whole script/noscript tags in the original code output by WFB (first code block in the first post in this thread).

Just trying to get my head wrapped around how SCCP and WFB work together. I'm currently neck deep in the CSS for one of the WFB themes to massage it into shape for the new look of my SCCP site when I put the update online.

I have hand coded lots of forms this way to use them on a site that I add custom JQuery/mysql dropdowns to and some other custom scripts. The original script tags trip up my custom scripts so I drop them.