Professional Version v3.3
These instructions are for the update files only.
For instructions on installing the full version, click
- This upgrade will work for users of WWC
Contests Pro and EventHandler Pro versions 2.7 and above. Users of versions
prior to 2.7 should perform a new install since their data is not compatible
with this version.
- The file 'WWCcontest.pl' will still
exist but only for compatibility. It is nothing more than an exact copy of
the 'EventHandler.pl' file. This allows sites to maintain any links
to the file 'WWCcontests.pl' without any interruption of operation. The 'WWCcontests.pl'
file will be called initially, but it will eventually redirect over to the 'EventHandler.pl'
file. You do not have to change your links which are pointed to 'WWCcontests.pl'.
We do recommend that you change them over time due to the fact that
the file 'WWCcontests.pl' will eventually be removed from the distribution
in future versions.
- The 'WWCcontests' directory is now
referred to as the 'EventHandler' directory. You do not have to
rename the directory but we recommend that you do rename it some time in the
- The directory 'contests' has been
changed to 'data'. The upgrade will not automatically change this for
you. You must rename it yourself. You can continue to use the directory 'contests'
but we recommend renaming it to 'data' since we will refer to the
data directory in the documentation. If you rename it, don't forget to make
sure you change the path for the 'data' directory in the Script Variables
. The upgrade has been designed to recognize the directory change
and should automatically correct any template paths that are pointed to use
the 'contests' directory. However, after the upgrade, it is recommend that
you check all your paths.
- The Contest Administration (admin.pl)
is now called User Administration.
- All contests, surveys, and polls are now
referred to as events.
- When upgrading, you should never replace
the setup.pl file or the files in your 'data' (contests) directory.
- cookie-lib.pl, cgi-lib.pl and
version.pl are no needed.
- Some new files may have been added depending
on the version you are upgrading from.
- The modules CGI.pm is required for a
few of the new features such as uploading. If this module is not installed
on your server, you will not be able to use these features.
CGI.pm has been a standard part of the Perl 5 distribution since 5.004
release of Perl. You must be running Perl version 5.003, patchlevel 7 or
higher in order to use CGI.pm.
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
The users will not even be able to login into the
Event Admin screens until you have finished the upgrade and reset the main
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.
Unzip the files to a location of your
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).
| |----- bg.gif
| |----- bg2.gif
| |----- Blackdot.gif
| |----- Bluedot.gif
| |----- Browndot.gif
| |----- EventHandler.gif
| |----- Greendot.gif
| |----- hint.gif
| |----- link.gif
| |----- Orangedot.gif
| |----- Purpledot.gif
| |----- Reddot.gif
| |----- reset.gif
| |----- submit.gif
| |----- Whitedot.gif
| |----- Yellowdot.gif
| |----- cont_tpl.htm
| |----- poll_tpl.htm
| |----- surv_tpl.htm
| |----- template.htm
For full details on each of the files and directories, you can click
|Set Perl Location in PL Files
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
If your server only allows CGI extensions
to be ran, at this point you must rename all the pl files to 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
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.
Login to your ftp server.
This can be done using any FTP client such as CuteFTP.
Change to the directory where your cgi scripts are installed.
Upload all the newest version of the files. You will want to
overwrite the following old files with the new ones.:
When uploading the .pl files, be sure to use ASCII mode transfer.
Never overwrite the setup.pl file. We don't include the setup.pl
to prevent this from happening.
If you had a temp directory, it is no longer used. You can
The uploads directory is no longer used also. If you
do not have any uploaded files in this directory, you can delete
it. If files exist in this directory, do not delete it.
These files will be moved as the users login to their accounts.
You can periodically check this directory. Once it is empty, you
can delete it.
If you have an images directory located here, these files have
been moved to a non-cgi directory. You can delete the images
directory here and all image files. If you have any custom images
located in this directory, you don't want to delete them. You will need
to move them to the new images directory that you will be created in
Upload the newest version of the following files to the translate
When uploading the .pl files, be sure to use ASCII mode transfer.
If you have the cookie-lib.pl,
cgi-lib.pl or version.pl files, they
are no needed. You can delete them.
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.
- In this file you will find a line that looks like the following:
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
Make sure you have the trailing / (slash) at
The links.htm file has additional information
in it for you to read.
non cgi-bin Directories and Upload NONCGI Files
Create a directory called EventHandler under the root directory
(main directory for your website) for your website.
Using your ftp client, change to the directory that you created above
in step 2.
Create a directory
structure that mimics the structure of the NONCGI directory. This
means you will create the following directories.
These directories will be subdirectories under the directory that
you created in step two. Examples:
Upload all the image files to the images
- If you are using version 3.1 or above, you should move your master
template files to the templates directory. These are the template
files which normally existed under the main cgi-bin/EventHandler
directory such as:
Once moved, they will exist at:
Do not overwrite any of your existing
templates files with the ones in the zip file.
- If you are using version 3.0 or below,
upload any new template files to your templates directory. If you
have a master template file (template.htm) in the cgi-bin/EventHandler
directory, you should move it into this directory.
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
When setting change permissions, you will want
have NT propagate (apply) those permission to all subdirectories and files under
each directory also.
You may need to ask your system administrator
to set the permissions for you.
for UNIX servers
For unix servers, please refer to the chart below
for the permissions on the files.
|----- admin-main.pl - 755
|----- admin.pl - 755
|----- date.pl - 666
|----- diagnose.pl - 755
|----- EventHandler.pl - 755
|----- readme.txt - 666
|----- setup.pl - 666
|----- subs1.pl - 666
|----- subs2.pl - 755
|----- subs3.pl - 755
|----- subs4.pl - 755
|----- translator.pl - 755
|----- WWCcontests.pl - 755
|----- translate- 777
|----- English.pl - 666
|----- master.pl - 666
|----- templates - 777
|----- cont_tpl.htm - 666
|----- poll_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.
Some UNIX servers will not allow 777
permissions to be set on the cgi EventHandler directory. If you follow the instructions completely
and you continue to get a server error while attempting to run the
scripts, set the permissions to 755 or 775 on the '/cgi-bin/EventHandler'
|Open your NEW
administration page in your browser
Point your browser to admin.htm
file which you uploaded. Most likely this is:
where domain is your domain.
You will no longer call the admin-main.pl
or the admin.pl files directly.
You can if you want but it is recommended that you use the new admin.htm
Main Script Variables
Click on the left hand side link labeled Script
Variables. This is under the Script Admin section.
Once you are in the Script Variables screen, you want to go through
of the fields and set each and every variable.
Since you may have moved your image files along with your master
template files, you need to change the paths to them accordingly.
Once you have set all the fields properly, click on the button
labeled Modify Main Variables.
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.
You can now notify the users that the upgrade has been complete.
You should notify them where the new admin screen is located. This
was the URL mentioned above:
Inform the users that all of their events have been disabled and that
they need to login to the User Settings screen. Once they are in
this screen, they will be presented with instructions on steps they
should take. Inform them to pay close attention to the instruction so
they don't run into any difficulties.
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