First Time Installation

Professional Version v4.0 Beta 1

1. You can print this out and refer to it as needed.
2. DO NOT attempt to upgrade a previous version.  The beta does not contain upgrade features yet.

Unzip the files to a location of your choice. 

After unzipping you should have two main folders called CGI and NONCGI. 

The directory and file structure for these should look like the charts:
(directories are in bold).

CGI
    |----- admin_event.pl
    |----- admin_script.pl
    |----- admin_user.pl
    |----- EventHandler.pl
    |----- subs_global.pl
    |----- vars_main.pl
    |----- data
               |----- delete_this_file.txt
    |----- modules
                |----- MIME
                         |----- Lite.pm
                |----- Net
                         |----- Cmd.pm
                         |----- Config.pm
                         |----- SMTP.pm
                |----- UBI
                         |----- CGI.pm
                         |----- File.pm
                         |----- Mail.pm
                         |----- Tables.pm
                         |----- Template.pm
                |----- subs_admin.pl
                |----- subs_banned_admin.pl
                |----- subs_demog_admin.pl
                |----- subs_email.pl
                |----- subs_entry_delete.pl
                |----- subs_entry_form.pl
                |----- subs_entry_submit.pl
                |----- subs_entry_view.pl
                |----- subs_event_admin.pl
                |----- subs_event_backup.pl
                |----- subs_event_clear.pl
                |----- subs_event_create.pl
                |----- subs_event_delete.pl
                |----- subs_event_global.pl
                |----- subs_event_post_check.pl
                |----- subs_event_settings.pl
                |----- subs_export.pl
                |----- subs_member_global.pl
                |----- subs_questions_admin.pl
                |----- subs_recommend.pl
                |----- subs_templates_admin.pl
                |----- subs_totals.pl
                |----- subs_user_global.pl
                |----- subs_user_settings.pl
                |----- subs_winners_admin.pl
                |----- subs_winners_global.pl
    |----- translate
                |----- English.pl
                |----- master.pl
    |----- plugins
                |----- AH_Member.pl
                |----- UBB_Member.pl

NONCGI
    |----- admin.htm
    |----- index.htm
    |----- images
    |           |----- blackdot.gif
    |           |----- bluedot.gif
    |           |----- browndot.gif
    |           |----- EventHandler.gif
    |           |----- greendot.gif
    |           |----- orangedot.gif
    |           |----- purpledot.gif
    |           |----- reddot.gif
    |           |----- whitedot.gif
    |           |----- yellowdot.gif
    |----- support
    |           |----- _default.js
    |           |----- directional_events.htm
    |           |----- email_variables.htm
    |           |----- multipage_events.htm
    |           |----- questions.htm
    |----- templates
    |           |----- cont_tpl.htm
    |           |----- poll_tpl.htm
    |           |----- quiz_tpl.htm
    |           |----- surv_tpl.htm
    |           |----- template.htm
    |----- users
               |----- delete_this_file.txt
 

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_event.pl
admin_script.pl
admin_user.pl
EventHandler.pl

The line will look like this:

#!/usr/local/bin/perl

If your server allows you to run Perl scripts with the pl extension or you have other Perl scripts on your server that use the extension pl, you can skip this step. Most server will allow pl extensions. 

If your server only allows CGI extensions to be ran, at this point you must rename all the pl files to cgi files.

Example:

admin_event.cgi
admin_script.cgi
admin_user.cgi
EventHandler.cgi

Once you have renamed each of these files, you must edit the following files and indicate in them that you are using the CGI extension:

admin_event.cgi
admin_script.cgi
admin_user.cgi
EventHandler.cgi

To edit them, open each files in a text editor. Find the line that says:

$cgiext = 'pl';

This line must be changed so that it reads:

$cgiext = 'cgi';

Once you have edited each file and saved them, you are ready to go using the CGI extension.

1. Login to your ftp server. This can be done using any FTP client such as CuteFTP.
    
2. Create a directory called EH40Beta on your server in which the script will run.  This most likely will be located as a subdirectory of your  cgi-bin directory.
   
   Example: http://www.domain.com/cgi-bin/EH40Beta
     
3. Using your ftp client, change to the directory which you created in step 2 above.
    
4. On your server, created a directory structure that mimics the structure of the CGI directory which you unzipped.  This means you will create the following subdirectories:
   
   data
   modules
   plugins
   translate
   
   These directories will be subdirectories under the directory that you created in step two. Examples:
   
   http://www.domain.com/cgi-bin/EH40Beta/data
   http://www.domain.com/cgi-bin/EH40Beta/modules
   http://www.domain.com/cgi-bin/EH40Beta/plugins
   http://www.domain.com/cgi-bin/EH40Beta/translate
    
5. Upload all files from the CGI directory to their respective directories on your server. Ignore the files under the NONCGI directory for now.
   
   When uploading the .pl files, you should be sure to use ASCII mode transfer.

1. Open the file index.htm in an editor of your choice. This is located in the NONCGI directory that was created when you unzipped the files.
    
2. In this file you will find a line that looks like the following:
   
   <a href="../cgi-bin/EH40Beta/admin_event.pl">Click here to login</a>
    
   Edit this link so that it points the admin_event.pl file.
   
   You will see help inside of the file to aid you in editing this file.

1. Login to your ftp server once again.  You may still be logged in from before.
    
2. Create a directory called EH40Beta under the root directory (main directory for your website) for your website.
   
   Example: http://www.domain.com/EH40Beta
    
3. Using your ftp client, change to the directory that you created above in step 2.
    
4. Create a directory structure that mimics the structure of the NONCGI directory. This means you will create the following directories.
   
   images
   support
   templates
   users
   
   These directories will be subdirectories under the directory that you created in step two. Examples:
   
   http://www.domain.com/EH40Beta/images
   http://www.domain.com/EH40Beta/support
   http://www.domain.com/EH40Beta/templates
   http://www.domain.com/EH40Beta/users
    
5. Upload all files from the NONCGI directory to their respective directories on your server.

If NT server, you will want to give the IUSR_XXX (Internet Guest Account) account CHANGE (RWXD) (RWXD) permissions for both main EventHandler directories. These are the directories you created such as:

http://www.domain.com/cgi-bin/EH40Beta/
http://www.domain.com/EH40Beta/

When setting change permissions, you will want have NT propagate (apply) those permission to all subdirectories and files under each directory also.

Note: You may need to ask your system administrator to set the permissions for you.

For unix servers, follow the steps below to set permissions.

1. Set CHMOD 755 on the following files (.cgi if you changed them)

         cgi-bin/EH40Beta
              |---- admin_event.pl
              |---- admin_script.pl
              |---- admin_user.pl
              |---- EventHandler.pl
 
2. Set permission on files below as directed (directories in bold):

cgi-bin/EH40Beta - 777 (see special note below)
    |-- vars_main.pl - 666
    |
    |----- data - 777
    |
    |----- translate- 777
    |            |-- English.pl - 666

EH40Beta
    |
    |----- templates - 777
    |           |-- cont_tpl.htm - 666
    |           |-- poll_tpl.htm - 666
    |           |-- quiz_tpl.htm - 666
    |           |-- surv_tpl.htm - 666
    |           |-- template.htm - 666
    |
    |----- users - 777

3. All files not mentioned above need no special permissions. Default permissions are fine.

1. This step is not a must at this moment. It can be done at any point down the line.
    
   The templates files are used to make your script look as though it is part of your site.
   
   For details on template files, click here.
    
   Note: When editing the template file, you must always include the $REPLACE variable.  This is to indicate where the script should insert the HTML which is generates.

Point your browser to the NONCGI directory that you created. Most likely this is:

http://www.domain.com/EH40Beta/

where domain is your domain.

This should call the index.htm file as present a welcome screen with a login link..

Click on the link 'click here to login'.

Click on the link that says [ Script Admin Login ] at the bottom.

You will be taken to the Script Login screen.

Leave the Admin ID and Admin Password blank and click on the Login button.

Once logged in, you will be at the Script Settings section.

Follow all the instructions and set your Script Settings as you need them.

It is important that you read through all the settings and set them accordingly since these are the settings that make your install of EventHandler run properly.

Click on Master Demographic Settings from the Script Admin Navigation menu.

Here you will define the master Demographic Fields that you will want to use for all users and events.

Make sure you read all the notes provides.

IGNORE THIS SECTION AS THE TRANSLATOR IS NOT COMPLETED

If you are translating into a language other than English, you'll need to translate the lines at this point.

To do that, got to Translator  under the Script Administration menu. Follow the instructions to create a translation.

Next step is to create a User ID.

To do this, while logged into the Script Administration Section, go to User Tasks under the Script Admin Navigation menu.

You will now be able to create a new user.

Once you have created the new user, you are ready to setup the User Settings.

To do this, you will use the link provide in order to login as that user.

This will return you to the User Login screen. Login using the new user you just created.

Once logged in, you will be at the User Settings Screen.  Read all the options and set them as you need them. These are your default settings for this user.

At this point you are ready to begin creating events and administering them.

To create am event, go to Create Event under the User Admin Navigation menu.

In this section you can create an event.  Just follow all the instructions to create an event.

Now, take some time to look around the admin screens. You will want to get familiar with them.

The admin screens have online help and docs to help you get around.

Make sure you read all instructions carefully.

At this point you are ready to begin using your EventHandler.

To call a list of your users, you will call EventHandler such as:

http://www.domain.com/cgi-bin/EH40Beta/EventHandler.cgi

If you want to call the events for a specific user, you will call EventHandler such as:

http://www.domain.com/cgi-bin/EH40Beta/EventHandler.cgi?Actn=Events_List&User_ID=xxx

where xxx is the user ID  for the user.