First Time Installation
Professional Version v3.2

1. You can print this out an refer to it as needed.

Unzip the files using any zip program such as Winzip. Make sure that you maintain the directory structure when unzipping the files.

For a complete list of the files which should exist after you unzip the file, click here.

If using NT, you can ignore this step.  If PERL is setup properly on your server, the .pl files should already be associated with the PERL installed on the server. 

For UNIX servers. You may need to set the location of your Perl in the scripts. The default location set for Perl in the script is:

#!/usr/local/bin/perl

If this path is correct for your server, you can skip to the next section.

The Perl location is the first line of the following files:

admin.pl
admin-main.pl
diagnose.pl
EventHandler.pl
subs2.pl
subs3.pl
subs4.pl
translator.pl
WWCcontests.pl

The line will look like this:

#!/usr/local/bin/perl

This applies for NT based servers only. 

At the top of each .pl file you will see require statements that look like:

require "setup.pl";
require "subs1.pl";
require "cgi-lib.pl";
require "date.pl";

Some NT servers will require that you put the full absolute (real)   path to these files.

If you are unsure whether your server requires the full path, you can do one of two things:

1. Contact your server administrator and they should be able to tell you. (preferred method)
   OR
2. Test the script once you are done with all the other install steps.   If you get blank screens or a message that states "Documents contains no data", you should then try the full path on the require statements.

If your server requires the full path, you should change each of these to look something like:

require "d:/www/www.domain.com/cgi-bin/WWCcontests/setup.pl";
require "d:/www/www.domain.com/cgi-bin/WWCcontests/subs1.pl";
require "d:/www/www.domain.com/cgi-bin/WWCcontests/cgi-lib.pl";
require "d:/www/www.domain.com/cgi-bin/WWCcontests/date.pl";

The path you would use would be dependent on where you put the contest files.

The files which might need editing include:

admin.pl
admin-main.pl
diagnose.pl
EventHandler.pl
subs2.pl
subs3.pl
subs4.pl
translator.pl
WWCcontests.pl

This step is not a must at this moment. It can be done at any point down the line.

The template file is used to make your script look as though it is part of your site.

The following are template files along with descriptions for each:
template.htm - Your main template file.
contest_tpl.htm - Default template file to be used for contests.
poll_tpl.htm - Default template file to be used for polls.
survey_tpl.htm - Default template file to be used for surveys.

For full details on templates, please click here.

1. Create a directory such as EventHandler on your server in which the script will run.  This most likely will be located in the cgi-bin directory.
   Example: http://www.domain.com/cgi-bin/EventHandler
    
2. On your server, created a directory structure that mimics the structure in the zip file.  This means you will create the following subdirectories:
   
     data
     uploads
     temp
   
   These directories will be subdirectories under the main directory that you created in step one. Examples:
   
     http://www.domain.com/cgi-bin/EventHandler/data
     http://www.domain.com/cgi-bin/EventHandler/uploads
     http://www.domain.com/cgi-bin/EventHandler/temp
   
3. Upload all files to their respective directories on your server with exception of the files in the images directory.
   
   This can be done using any FTP client such as CuteFTP.
   
   When uploading the .pl files, you should be sure to use ASCII mode transfer.
   
   If you are importing the files on an NT server using FrontPage, you more than likely don't have to worry about the ASCII transfer mode. However if you do encounter problems running the scripts, you should try uploading the files in ASCII mode with an FTP program.
      
4. Create a directory such as images in an area where image files can be read. Some servers cannot read image files from within the cgi-bin directory. If you place this directory under the cgi-bin directory, and the images don't show up, try moving it to a location outside of the cgi-bin directory.
   Example: http://www.domain.com/EventHandler/images/
    
5. Upload all the files from image directory in the zip file to the new image directory which you created in step above.

Once you have uploaded all the files, you will need to set the permission on files and directories. Please refer to the chart below for this:

All directories should have the following permissions:

• 777 for UNIX
• Change (RWXD) (RWXD) for the IUSR_XXX account on NT.

Note: If you are on an NT server you may need to ask your system administrator to set the permissions for you. If you have to, just ask them to set the permissions on your main 'EventHandler' directory as well as all files and subdirectories under it to 'Change (RWXD) (RWXD)' for the 'IUSR_XXX' account.

 For full details on each of the files, you can click here.  

Run the Script Administration (admin-main.pl) to set all of your main script variables.

By default, you will leave the username and password blank when you first login.

Once you login into the Script Administration, you should make sure you define your admin username and admin password.

If you are planning on allowing multiple users, you need to check the appropriate box in the Script Administration. This option is labeled 'Use ID's (Multiple Users).

If you decide to use ID's, you will need to create at least one ID to get started. This can be done through the Script Administration in the section called 'Create New User'

We recommend using ID's right from the start even if you are the only one planning to use the script.
If you don't, and later you want to switch over to using ID's, there a few special steps you need to take. It's easier just to start with ID's. 

At this point you are ready to start creating your events by logging into the Event Administrator (admin.pl).

If you are using ID's (recommend), when logging in, you will use the username and password which you created for the new user.

If you are not using ID's, you will use the admin username and admin password that you set in the Script Administration.