Stouk BKM Lite

For Windows IIS or Apache

- Unzip the file;

- Create subfolder under the cgi-bin folder of your Web Server named “bkm”

- Copy all files including subfolders to new location;

- Allow read/write access for Internet Guest user the following folders: “db”,”log”,”cache”,”stat”,”uenv”,”temp”,”debug”,”tts”;

- Make sure that Perl is associated with “.cgi” extension and that Web Server allows execute under the “/cgi-bin/bkm” ;

- Call the script from Internet Browser by specifying http://ServerAddress/cgi-bin/bkm/index.cgi;

Please skip the LINUX portion and continue reading important information below.

For Linux

- Unzip the file;

- Create subfolder under the cgi-bin folder of your Web Server named “bkm”;

- Copy all files including subfolders to new location;

- Allow read/write access for Internet Guest user the following folders: “db”,”log”,”cache”,”stat”,”uenv”,”temp”,”debug”,”tts”;

- Remember, some Linux Web Server configurations do not allow images to be served from within the cgi-bin folder. In this case: Copy the following folders “images”, “editor” with all the content to the directory on the same level as “cgi-bin“, you will have to pay attention to configuration screen of the script and make sure that appropriate paths are properly specified when initially executing the script;

- Some Web Servers only allow executing scripts if the permission on the folder, holding the script is 755 and the permission on the index.cgi is also 755

- Please do not e-mail me with ERROR 500 on your server I can only give you some reasons why this error might occur:

1) If the path to your Perl interpreter is not properly specified in the “index.cgi” (please check this too);

2) The files were uploaded incorrectly (ASCII vs Binary);

3) Permissions are not correct on files (you can safely change permissions recursively to 777 on all files and folders below “cgi-bin/bkm/*.*” except index.cgi, there is nothing executed from there); Note that "/cgi-bin/bkm" folder itself should have 755 as well as the index.cgi file;

4) Some module required by the program is not installed (please pay attention to XML::Simple and Mail::Sender modules, because they are not part of standard Perl installation). Please check the paragraph on Modules below if you think installing Perl modules is a difficult task.

If it is Error 500 that you have, and you checked everything above, please address this to the Administrator of Linux box (your host provider). Usually they are helpful with installations.

IMPORTANT:

SAME STEPS for WINDOWS and LINUX Below:

If the configuration is correct then you should see the configuration page. You Have to Press UPDATE at least once, to save the configuration.

If you do not press UPDATE and quit the script delete everything under the “db” folder and do the above operation again. Deleting files under “db” folder will re-initialize the script.

Please make sure that all the paths are recognized or configured properly, save configuration by clicking UPDATE.

To call the application always use the following address:

http://YOURSERVERNAME/cgi-bin/index.cgi?c=bkm0showcats

Please note the option “?c=bkm0showcats” after index.cgi (all lowercase).

If no command option is defined ("c") login will fail, even if correct user/password was provided.

Default password for user "administrator" is "12345". Please change it after installation not to compromise security.

Any comments or suggestions on installation instructions are appriciated.

Modules:

XML::Simple is used to work with the configuration files and data files without database;

Mail::Sender is required to enable user registration.

Other modules like Digest::MD5, used by script usually installed with Perl 5.x on your web server by default.

Modules installation tips:

If you do not have administrative permissions on your web server (which is the case if it is hosted by host provider) and you need XML::Simple or Mail::Sender modules installed, simply copy the XML and Mail folders, containing the Simple.pm and Sender.pm files respectively to cgi-bin folder and/or to Web root of the server. Script should see the module files and use them.