Dreamweaver - Using Form Processor Pro

Author

Using Form Processor Pro

Jely_Bean

2004-05-18, 7:35 pm

Hi...

I don't really understand how form handlers work...so I bought this program
Form Processor Pro (email-form.com) -- said it was easy to install, etc. but I
am really having a hard time understanding how it works. I have set up a form,
and it can be looked at: www.sierrabrokers.com/marketanalysis.htm

I have set all the fields, and even have set up the validate form options... I
am using Dreamweaver 4.
This program uses two files, which is states to put into the CGI-Bin.
Directions are as follows:

Installation package consist of Form Processor Pro 4.0 executable files,
configuration files and demo forms with real working examples:

formprocessorpro.pl - executable PERL script that performs form processing;
formprocessorpro.php - executable PHP script that performs form processing;
formprocessorpro.cfg - basic configuration file for executables (see FPP
Description / Basic Configuration File)
?
Form Processor Pro 4.0 is developed to run on any Windows- and Unix-
compatible platforms (web-servers) and has standard requirements for PERL or
PHP scripts. This usually means that there are no special requirements for the
final server that may need additional installations.

Form Processor Pro 4.0 PERL executable needs PERL 5 or higher,
Form Processor Pro 4.0 PHP executable needs PHP 4.1.0 or higher to be
installed on the system.
Both PERL and PHP packages are commonly available at the hosting server.

NOTE: You should use either PERL or PHP Form Processor Pro 4.0 executable at
once; there is no need to use both of them. Two versions (PHP and Perl) were
developed to cover more types of servers where this script can be used.

Installation

Form Processor Pro 4.0 installation process can be divided into the following
steps:
Step 1. Unpack Form Processor Pro 4.0 installation package, using any
archive-extraction program (e.g., WinZIP).
Step 2. Upload Form Processor Pro 4.0 extracted files to the server, using any
FTP client (e.g., CuteFTP).
Form Processor Pro 4.0 PERL executable (formprocessorpro.pl) must be located
in the folder that has executable permission. Most often it is /cgi-bin/ folder.
Form Processor Pro 4.0 PHP executable (formprocessorpro.php) has no specific
location restriction.
Step 3. Set permissions, using Unix shell command or any FTP client (e.g.,
CuteFTP)
1) Executable (read/execute) permissions for Form Processor Pro 4.0 Perl
executable (if you don?t use PHP executable)
Unix shell command: chmod 755 formprocessorpro.pl
2) Write Enabled (read/write) for files and folders that need to be accessed
for writing. For example DB or log files, folder for user uploads - attachments
(see section Learning to Work with FPP)
Unix shell command: chmod 666 <filedir_name>,
Where <filedir_name> is file or folder in question
For Form Processor Pro 4.0 forms configuration please refer to section FPP
Configuration

________________

it has examples of forms...and simply states to change the preferences on the
form.php file, so I went into CGI and set the preferences and saved...but I
really have no idea what I am doing. DO I have to have a PHP program in order
to use this script? I figured once I uploaded it, that only the host would need
to have the program....Please someone, just help me figure this program out, or
if there is an easiar way to send this form to myself to test it...that would
be great.

I have tried everything!

curmungeon

2004-05-18, 7:36 pm

How about contacting the people you purchased it from?

"Jely_Bean" <webforumsuser@macromedia.com> wrote in message
news:c8bubm$h26$1@forums.macromedia.com...
> Hi...
>
> I don't really understand how form handlers work...so I bought this
program
> Form Processor Pro (email-form.com) -- said it was easy to install, etc.
but I
> am really having a hard time understanding how it works. I have set up a
form,
> and it can be looked at: www.sierrabrokers.com/marketanalysis.htm
>
> I have set all the fields, and even have set up the validate form
options... I
> am using Dreamweaver 4.
> This program uses two files, which is states to put into the CGI-Bin.
> Directions are as follows:
>
> Installation package consist of Form Processor Pro 4.0 executable files,
> configuration files and demo forms with real working examples:
>
> formprocessorpro.pl - executable PERL script that performs form
processing;
> formprocessorpro.php - executable PHP script that performs form
processing;
> formprocessorpro.cfg - basic configuration file for executables (see FPP
> Description / Basic Configuration File)
> ?
> Form Processor Pro 4.0 is developed to run on any Windows- and Unix-
> compatible platforms (web-servers) and has standard requirements for Perl
or
> PHP scripts. This usually means that there are no special requirements for
the
> final server that may need additional installations.
>
> Form Processor Pro 4.0 PERL executable needs PERL 5 or higher,
> Form Processor Pro 4.0 PHP executable needs PHP 4.1.0 or higher to be
> installed on the system.
> Both PERL and PHP packages are commonly available at the hosting server.
>
> NOTE: You should use either PERL or PHP Form Processor Pro 4.0 executable
at
> once; there is no need to use both of them. Two versions (PHP and Perl)
were
> developed to cover more types of servers where this script can be used.
>
> Installation
>
> Form Processor Pro 4.0 installation process can be divided into the
following
> steps:
> Step 1. Unpack Form Processor Pro 4.0 installation package, using any
> archive-extraction program (e.g., WinZIP).
> Step 2. Upload Form Processor Pro 4.0 extracted files to the server,
using any
> FTP client (e.g., CuteFTP).
> Form Processor Pro 4.0 PERL executable (formprocessorpro.pl) must be
located
> in the folder that has executable permission. Most often it is /cgi-bin/
folder.
> Form Processor Pro 4.0 PHP executable (formprocessorpro.php) has no
specific
> location restriction.
> Step 3. Set permissions, using Unix shell command or any FTP client
(e.g.,
> CuteFTP)
> 1) Executable (read/execute) permissions for Form Processor Pro 4.0 Perl
> executable (if you don?t use PHP executable)
> Unix shell command: chmod 755 formprocessorpro.pl
> 2) Write Enabled (read/write) for files and folders that need to be
accessed
> for writing. For example DB or log files, folder for user uploads -
attachments
> (see section Learning to Work with FPP)
> Unix shell command: chmod 666 <filedir_name>,
> Where <filedir_name> is file or folder in question
> For Form Processor Pro 4.0 forms configuration please refer to section
FPP
> Configuration
>
> ________________
>
> it has examples of forms...and simply states to change the preferences on
the
> form.php file, so I went into CGI and set the preferences and saved...but
I
> really have no idea what I am doing. DO I have to have a PHP program in
order
> to use this script? I figured once I uploaded it, that only the host would
need
> to have the program....Please someone, just help me figure this program
out, or
> if there is an easiar way to send this form to myself to test it...that
would
> be great.
>
> I have tried everything!
>

amberp

2006-11-30, 5:17 pm

quote:
Originally posted by curmungeon
How about contacting the people you purchased it from?

Because sometimes it's just faster to ask for help elsewhere and you actually get help, more often than not, than you get with the product/services actual "Support" team (If you really want to call some of them that).

For instance,

Another poor soul not given support

I see this so often and have gone through this same thing with so many companies.

Anyway, mods, I apologize for bumping a hundred year old thread, but I really needed to comment on that.

I'm going through my own issues with Form Processor Pro.
Easy to install, lol. Yeah, right...

I really had high hopes for this product because it's exactly what I needed. I liked the idea of an easy to use form processor or linux that could handle just about any form you threw at it.

Boy was I sadly mistaken :/

And the last thing I can really afford to do, is throw money into another "failed" piece of software, not to mention support for it.