Pricing/Ordering

EventHandler

Registered Members

Demos
- Events

- Admin Screens
- Visitor Created Test Events

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

Documentation
-Index
-
Install
-Feature List
-Requirements
-License Agreement

Support/Info/Help
-Forums
-Install Request Form
-Mailing List
-Contact Us

Download
-
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

-RatingsHandler
-AccountHandler
-Announcer
-Smartlist Manager
-Downloader


 

 

Upgrading Instructions
Professional Version v3.7

Important Upgrade Notes
  1. This upgrade is designed for users of version 3.4 and above. This is due to the fact that many significant changes have been made in versions 3.4-3.6.
     
  2. If you are using v3.3 and below, you can perform this upgrade. However you want to make sure that you check all of your Script Settings, your User Settings for all user (if using users), as well as your Event Settings for all events.
     
    Many settings have been added that you will need to define as we as many settings have changed that will require you to re-set them.
General Notes
  1. We always recommend you backup your current version.
     
  2. The file WWCcontests.pl no longer exists. If you are still using links that point to WWCcontests.pl, you need to change them to the new EventHandler.pl file.
      
  3. When upgrading, you should never replace the setup.pl 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.
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).

CGI
    |----- admin-event.pl
    |----- admin-member.pl
    |----- admin-script.pl
    |----- diagnose.pl
    |----- EventHandler.pl
    |----- readme.txt
    |----- SSI.pl
    |----- subs1.pl
    |----- subs2.pl
    |----- subs3.pl
    |----- subs4.pl
    |----- translator.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
                |----- hint.gif
                |----- Orangedot.gif
                |----- Purpledot.gif
                |----- Reddot.gif
                |----- Whitedot.gif
                |----- Yellowdot.gif

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:

#!/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-member.pl
admin-script.pl
diagnose.pl
EventHandler.pl
SSI.pl
subs2.pl
subs3.pl
subs4.pl
translator.pl

The line will look like this:

#!/usr/local/bin/perl

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.

Example:

admin-event.cgi
admin-member.cgi
admin-script.cgi
date.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-member.cgi
admin-script.cgi
diagnose.cgi
EventHandler.cgi
SSI.pl
subs2.cgi
subs3.cgi
subs4.cgi
translator.cgi

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.
     
    Example: http://www.domain.com/cgi-bin/EventHandler
      
  3. Upload all the newest versions of the files.  You will want to overwrite the following old files with the new ones.:
     
    admin-event.pl
    admin-member.pl
    admin-script.pl

    diagnose.pl
    EventHandler.pl
    SSI.pl
    subs1.pl
    subs2.pl
    subs3.pl
    subs4.pl
    translator.pl
      
  4. Upload the newest version of the following file to the plugins directory:
     
    AH.member.pl
    UBB.member.pl
       
  5. Upload the newest version of the following files to the translate directory:
     
    English.pl
    master.pl
     
    When uploading the .pl files, be sure to use ASCII mode transfer.
Edit your index.htm file
  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/EventHandler/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.
Upload NONCGI Files
Upload the files index.htm and admin.htm.

Note: The links.htm and the welcome.htm files are no longer needed and can be deleted.


We have included the images  directory with the update since some images have changed and some of the older images are no longer needed.

You can delete all of the images you have from older versions and upload the new images.
All you will need in the images directory are the image files included in this update.

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:

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

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, follow the steps below to set permissions.

1. Set CHMOD 755 on ALL .pl files (.cgi if you changed them)

2. Set permission on files below as directed (directories in bold):

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

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

Re-set the Script Settings

Point your browser to the NONCGI directory such as:

http://www.domain.com/EventHandler/

This should call the new index.htm file.

At this point use the link 'click here to login' to get to the login screen.

By default now, you are taken to the User Login.

You will want to use the 'Script Admin Login' link towards the bottom to get into the Script Administration now and in the future.

Once logged in to the Script Administration, you will need to check all of your Script Settings.

By default all events will be disabled. You will need to enable them again once you re-set all of your Script Settings.

Translate

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.

Create and Setup New User

If you are upgrading from a previous version in which you were already using user ID's, skip this step.

If you are upgrading from a previous version where you were not using ID's, you must create a new ID at this point.  Version 3.6 and all versions following will require the use of ID's.

To do this, while logged into the Script Administration Section, go to User Tasks under the Script Administration navigation menu and follow the steps to create a new user ID.

If you had existing events, you can now import the events into the data directory for the new user.  To do this, go to Import Events under the Script Administration navigation and follow the instructions for importing the events.

Note: The Import Events option will only exist in the navigation menu if there are events to import. If the application cannot find any existing events to import, the Import Events option will disappear.

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

To do this, you need to click on the link provided at the top where it says:

Click here to return to the login screen

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 will need to re-set the Event Settings for all of your Events. Once this is done, you are ready to go.

Note: Now that you are using users, the URL to call specific events will change. You must now add &id=xxx (where xxx is the user id) to the URL.


For example:

If your old link was something like:

EventHandler?filename=file&action=entryform

it must now be changed to:

EventHandler?filename=file&action=entryform&id=xxx

The &id=xxx tells EventHandler that you are now calling that event under the user xxx.

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