NOF Form Handler Component

[riojarobin]

Quick question - is there any way to configure this component to submit forms to multiple email addresses?

[gotFusion]

You can try separating multiple addresses with a ;

email-address1 ; email-address2 ; email-address3 ; etc

[riojarobin]

You can try separating multiple addresses with a ;

email-address1 ; email-address2 ; email-address3 ; etc

Thanks, I have already, without success, tried this. I have a copy of Coffeecup FormBuilder somewhere; I think I'll teach myself how to use this and then integrate into NOF12 -or would you advise against this?

Regards,

Robin

[Trimdoner]

Thanks, I have already, without success, tried this. I have a copy of Coffeecup FormBuilder somewhere; I think I'll teach myself how to use this and then integrate into NOF12 -or would you advise against this?

The CoffeeCup form is very easy to integrate into a NOF page, but beware unless you have the very latest version the forms produced are Flash, so don't show up on iPads, iPhones etc.

Ken

[franko]

Not Coffee Cup but pretty much all my forms are 3rd party and are encoded on my server. Ctrl-T is your best NoF friend.

[gotFusion]

If you are still having problems or fighting with forms take a look at my tutorial for using online forms processing by 123 contact forms with Fusion.

http://www.gotfusion.com/tutorials/tut.cfm?itemID=4075

[Joe Rotello]

On 9/20/2012 8:33 AM, Trimdoner wrote:
> riojarobin wrote:
>> Thanks, I have already, without success, tried this. I have a copy of
>> Coffeecup FormBuilder somewhere; I think I'll teach myself how to use
>> this and then integrate into NOF12 -or would you advise against this?
> The CoffeeCup form is very easy to integrate into a NOF page, but
> beware unless you have the very latest version the forms produced are
> Flash, so don't show up on iPads, iPhones etc.
>
> Ken
> http://trimdon.com
>
CoffeeCup's new WebForm Builder 2.1 replaces the older CoffeeCup
Flash/PHP based form builder. It's now based on HTML5 + PHP generation.
It handles a wide range of needs, MySQL database is optional, sends
submitted forms to server-based file or to your Email, operates and
communicates to your web-site visitor transparently, etc.

In our 14+ projects usage, the 2.1 version integrates superbly into NOF
pages, using Ctrl-t placement of the generated form code as NOF HTML text.

http://www.coffeecup.com/web-form-builder/

Hope this info is of help.

[cougarfood]

Have you tried a bigger hammer? I do enjoy brute force at times (I saw a bumper-sticker once: "Sticks 'n stones may break my bones, but whips and chains intrigue me". I pray it's always my hands on that hardware).

Have you maipulated PHP? Have you looked at the FormsHandler Properties pages within the Scripts of your local publish directory? Stuff can be broken with ease, but it can also be manipulated correctly, then published independently. If you break it, simply re-publish that page and rip-into it again. NOF will always build it aneeuuuw, correctly.

Remember that this data will change after each NOF Form change, so it's best to make your changes, then save the file redundantly so's you don't have to re-manipulate that Handler Component after each change to the NOF form. This works well if you don't change the actual Form Fields.

Else, if you did modify the forms' fields, copy the correctly manipulated lines o'text from the Handler Component you had saved, then paste them into the newly (NOF) created component via a text editor. Then publish that single component to the server.

Again, your manipulated/text-edited NOF Formhandler component must be re-published after each form manipulation and subsequent NOF publication 'cause that component is created new after each Form change and publication.

[Joe Rotello]

On 9/24/2012 3:19 PM, cougarfood wrote:
> Have you tried a bigger hammer? I do enjoy brute force at times (I saw
> a bumper-sticker once: "Sticks 'n stones may break my bones, but whips
> and chains intrigue me". I pray it's -always --_my_- hands on that
> hardware).
>
> Have you maipulated PHP? Have you looked at the FormsHandler
> Properties pages within the Scripts of your local publish directory?
> Stuff can be broken with ease, but it can also be manipulated correctly,
> then published independently.
>
> Remember that this data will change after each NOF Form change, so it's
> best to make your changes, then save the file redundantly so's you don't
> have to re-manipulate that Handler Component after each change to the
> NOF form. This works well if you don't change the actual Form Fields.
>
> Else, if you did modify the forms' fields, copy the correctly
> manipulated lines o'text from the Handler Component you had saved, then
> paste them into the newly (NOF) created component via a text editor.
> Then publish that single component to the server.
>
> Again, your manipulated/text-edited NOF Formhandler component must be
> re-published after each form manipulation and subsequent NOF publication
> 'cause that component is created new after each Form change and
> publication.
>
>
I understand where you are coming from. Really, I do.

NOF 12 is NOT to be discarded, not by any means, yet at the same time
those that do not have the time, or perhaps not the staff, to "mess
with" NOD CSS and PHP codes that it generates CAN benefit by taking a
serious look at external third-part tools such as CoffeeCup's WebForm
Builder 2.1

WebForm Builder 2.1 is not quite the "bigger hammer" that I too at first
thought it was. It's pretty elegant in structure and not wasting your
time to get an important job accomplished.

Joe