RSD Element: Form Container - Post ID...
Mark Madura
Registered User
60 posts
Is there any documentation on how the Form Container is used? As I mentioned in a separate thread, I'm in the process of converting our demo form which is currently a custom PHP form. Should I be using Web Form Builder to create a 'new' form?
Scott Swedorski
VP of Software Development
0 posts
Those are just elements that allow you to visually build a form. It adds no backend functionality to actually make the form work. That would still be something you would have to code in PHP. If you want to build a form, Web Form Builder would be what you want to use.
Learn the essentials with these quick tips for Responsive Site Designer, Responsive Email Designer, Foundation Framer, and the new Bootstrap Builder. You'll be making awesome, code-free responsive websites and newsletters like a boss.
Elisabeth Weir
Registered User
12 posts
Is there a tutorial or anything on how to put the WFB into the form container? I've looked all over and can't find out how to do it....
Bob Visser
COO
827 posts
You can find an overview here: http://www.coffeecup.com/help/articles/ … -designer/
The future of web layout has arrived and it's called CSS Grid. CoffeeCup helps you to get ready with a free guide, the Grid Builder app plus cool demos & themes.
Brian Durfee
Senior Advisor
1,096 posts
Elisabeth Weir wrote:
Is there a tutorial or anything on how to put the WFB into the form container? I've looked all over and can't find out how to do it....
Is there a tutorial or anything on how to put the WFB into the form container? I've looked all over and can't find out how to do it....
The tutorial will show you how to do it. One other tidbit is that the WFB form does not go in a form container. Here's the difference.
As Scott said, the form container is to visually build your form, but you have to provide your own form processor.
With WFB, it generates the form AND the processor so everything is self-contained. The code that WFB gives you when you export goes into an HTML Element.
ASK ME ANYTHING
I provide personalized help for Coffeecup Users including personal or group training for Site Designer, Web Form Builder and more via Zoom.
Email me at support@uscni.org or call 865-687-7698.
Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
I provide personalized help for Coffeecup Users including personal or group training for Site Designer, Web Form Builder and more via Zoom.
Email me at support@uscni.org or call 865-687-7698.
Did you know that Web Form Builder can be used for both simple and complicated forms and that it's not limited to the default fonts and buttons? Take a look at a form we developed for WindowTinting.com.
https://forms.windowtinting.com/forms/w … ppingcart/
Elisabeth Weir
Registered User
12 posts
Bob Visser wrote:
You can find an overview here: http://www.coffeecup.com/help/articles/ … -designer/
You can find an overview here: http://www.coffeecup.com/help/articles/ … -designer/
Hey Bob -- the link you posted just links right back here. Which is cool the first go-round, for that authentic Through The Looking Glass experience ... but does not actually address the issue long-term...
Brian Durfee wrote:
The tutorial will show you how to do it. One other tidbit is that the WFB form does not go in a form container. Here's the difference.
As Scott said, the form container is to visually build your form, but you have to provide your own form processor.
With WFB, it generates the form AND the processor so everything is self-contained. The code that WFB gives you when you export goes into an HTML Element.
The tutorial will show you how to do it. One other tidbit is that the WFB form does not go in a form container. Here's the difference.
As Scott said, the form container is to visually build your form, but you have to provide your own form processor.
With WFB, it generates the form AND the processor so everything is self-contained. The code that WFB gives you when you export goes into an HTML Element.
OK, I just got confused by the name. I somehow thought a "Form Container" was a, well, container for a form made in WFB! I understand now! Thank you both for taking the time to reply!
For any future person who comes along with the same question:
The interaction elements are for the more skillful web developers. If you have created a custom form, then use the form container, input, and button submit elements. Use them as a placeholder for your custom fields in the design. You will need to export the page source to complete the configuration for these elements. Using Web Form Builder? Then instead use the HTML element to paste the fully completed and functional form.
From : http://www.coffeecup.com/help/articles/ … -elements/
Bob Visser
COO
827 posts
Elisabeth Weir wrote:
Hey Bob -- the link you posted just links right back here.
Hey Bob -- the link you posted just links right back here.
Haha, wow, was a long night! (Working on something cool though
).Anyway, I updated the link, sorry for that
The future of web layout has arrived and it's called CSS Grid. CoffeeCup helps you to get ready with a free guide, the Grid Builder app plus cool demos & themes.
Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.
