Registered Members

- Events

- Admin Screens
- Visitor Created Test Events

Click here to test the admin screens and create test events.

-Feature List
-License Agreement

-Install Request Form
-Mailing List
-Contact Us

Free Version

Mailing List
-Click here
to stay updated. 

Rate this script at The CGI Resource Index:

Thank you for support and interest in our products!

Don't forget to take a look at our other scripts

-Smartlist Manager



Upgrading Instructions
Professional Version v3.5
For users of v3.4 only.

Note: Due to many significant changes, this upgrade will only work if you are currently running version 3.4. If you are running a version previous to version 3.4, you must perform an upgrade to version 3.4 first. Once your upgrade to version 3.4 has been completed, you can then upgrade to version 3.5.

  1. We always recommend you backup your current version. .
  2. The file no longer exists. If you are still using links that point to, you need to change them to the new file.
  3. When upgrading, you should never replace the file or the files in your 'data' directory.
  4. When upgrading, you should never replace any of your existing template files. Only upload new template files if you do not already have them. If you replace any of your modified template files, you will have to modify them again.

If you are using ID's, you should notify your users that you are going to upgrade.

By default, all events will disabled for all users.

The users will not be able to login into the Event Admin screens until you have finished the upgrade and reset the main Script Variables.

After you have complete the steps below, your users will be able to login.  However their events will be disabled until they reset their user variables and the variables for each event.

Unzip Files

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).

    |----- readme.txt
    |----- translate
    |----- plugins

    |----- admin.htm
    |----- links.htm
    |----- welcome.htm

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

Set Perl Location in PL Files (UNIX Only)

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:


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:

The line will look like this:


If need to run CGI extensions

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.



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:


To edit them, open each file 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.

Update cgi-bin files
  1. Login to your ftp server. This can be done using any FTP client such as CuteFTP.
  2. Change to the directory where your cgi scripts are installed.

  3. Upload all the newest versions of the files.  You will want to overwrite the following old files with the new ones.:
  4. Upload the new file to the directory above.

  5. Upload the newest version of the following file to the plugins directory:

  6. Upload the newest version of the following files to the translate directory:

    When uploading the .pl files, be sure to use ASCII mode transfer.
Edit your links.htm file
  1.  Open the file links.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:

    <BASE HREF="" target="main">

    Edit this line so that it points the location where your cgi script files exist.

    You will only edit the part that is in red above. Do not edit


    <BASE HREF="" target="main">
    <BASE HREF="" target="main">

Make sure you have the trailing / (slash) at the end.

The links.htm file has additional information in it for you to read.

Create non cgi-bin Directories and Upload NONCGI Files
  1. Upload the new files for admin.htm, links.htm, and welcome.htm.
Set Permissions for NT servers

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:

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.

Set Permissions for UNIX servers

For unix servers, please refer to the chart below for the permissions on the files.

cgi-bin/EventHandler - 777
    |----- - 755
    |----- - 755
    |----- - 755
    |----- - 666
    |----- - 755
    |----- - 755
    |----- readme.txt - 666
    |----- - 666
    |----- - 755
    |----- - 666
    |----- - 755
    |----- - 755
    |----- - 755
    |----- - 755
    |----- data - 777
    |----- translate- 777
                |----- - 666
                |----- - 666
    |----- plugins - 755
                |----- - 666

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

Only the files listed above require special permissions. All other files can use the default permissions.

Set The Main Script Variables

Go to your admin screen in your browser.

Click on the left hand side link labeled Script Variables. At this point you should check all of your Script Variables and re-submit them. Pay attention to any new settings and set them accordingly.


If you are translating into a language other than English, at this point you'll need to log into the Translator and translate any new lines as well as check all your existing translations.

Notify Users

If you have users, you should notify them that the upgrade has been complete.

They will need to submit their User Variables to update them to the new version format.

Once they have submitted their User Variables, they will then need to submit the Event Variables for each event to ensure they are operating.

You should also enform your users to check all of their settings to ensure they are correct.  They should also pay attention to any new settings that might need to be defined. 

That's all.

Your upgrade should be complete.

If you are having problems, please check out our support forums. The answer to your question may already be there. If not, just leave your question and we will answer it as soon as possible.




Featured Site

Used By

and many more




Copyright © 1994-2001 UbiDog Productions. All Rights Reserved.
Formerly known as Wolfcountry Web Creations