Installation for Message Board Freeware




Important note for windows servers users:

You need to open
configur.pl, edit.pl, message.pl, setup.pl, and view.pl, then modify $fullpath to your full system path. In addition, make sure you are using "/" instead of "\" in your system path.

Please visit our FAQ section if you want more information about the system path.





For legal and copyright information, please refer to the header notice inside each script.
1) If the path to perl on your server is different from
#!/usr/local/bin/perl
then you will need to change it at the first line in configur.pl, edit.pl, message.pl, setup.pl, and view.pl.



2) Files can be uploaded with your FTP client in two different modes. You will need to use both to complete this installation. First, create two directories. One inside your cgi-bin (name it whatever you like, but for the sake of our example we'll use /cgi-bin/mb), and one outside your cgi-bin (again, name it whatever you wish, we'll use /mb). Change the permissions for /mb (the one outside the cgi-bin) to 755. Once you have done that, create a directory called board1 under /mb(the one outside the cgi-bin). Chmod this directory to 755. This is the directory step 5 mentions later on in this documentation. (You will need to chmod /board1 to 777, if you get permission denied errors when you try to post a message. However, try 755 first)

Upload the following files into /cgi-bin/mb in ASCII mode:

(everything except cookies.js and the icon_images directory)
/data
/data/board1.bd
/data/board1.txt
/misc
cgi_logo_smaller.gif
Common.pm
configur.pl
enotify.pl
errorlog.txt
footer.txt
header.txt
mcfg.pl
message.pl
mgcfg.pl
readme.html
setup.pl
smtp_mail.lib
superuser.db
vcfg.pl
vfooter.txt
vheader.txt
view.pl

Upload cookie.js into /mb also in ASCII mode.

Upload the icon_images directory into /mb in BINARY mode.

Note, that it is VERY important to make sure you upload each file in the correct mode.




Please visit our FAQ section if you want to know how to upload a file in ASCII mode.



3) Chmod all files and directories, besides cookie.js and images files, to permission "755."

This includes:
/mb
/mb/board1
/cgi-bin/mb/data
/cgi-bin/mb/data/board1.bd
/cgi-bin/mb/data/board1.txt
/cgi-bin/mb/misc
cgi_logo_smaller.gif
configur.pl
edit.pl
enotify.pl
errorlog.txt
footer.txt
header.txt
mcfg.pl
message.pl
mgcfg.pl
readme.html
setup.pl
smtp_mail.lib
superuser.db
vcfg.pl
vfooter.txt
vheader.txt
view.pl


*However, if you get a permission denied message when you save the configurations or passwords, you will need to chmod mcfg.pl, mgcfg.pl, vcfg.pl, superuser.db, header.txt, footer.txt, enotify.pl,errorlog.txt, and sub directories (data and misc, including their contents) to permission "777."

Please visit our FAQ section if you want to know how to chmod a file.



4) Execute setup.pl with your browser (point the browser to http://www.your_site.com/cgi-bin/messageboard/setup.pl)



5) Set the superuser admin name and password, then reload the browser to configure.
Setup.pl will detect most paths for you. The paths it fails to detect you will have to enter into setup.pl manually. Look for [please specify my path] to know which paths were detected and which weren't.

Be sure that when you get to the bottom of the configuration page that you do not neglect to specify both the Full System path to the message directory, and the WWW path (URL) to the messages directory. Note that these two paths different, although they point to the same place. The full system path is likely to be something like, "/web/home/httpd/cgi-bin/mb/borad1" or "e:/inetpub/wwwroot/mb/board1", whereas the WWW path is something like "http://www.yourname.com/mb/board1". Usually, you can obtain the system path from your server admin. If you can telnet to your server, type in "pwd" after you have logged in. The PWD command will return your current system path. Otherwise, you can always obtain the path from your server admin.



6) The board should now be ready to run! Simply point your users to view.pl. If you are not able to access view.pl due to configuration errors. You can always use configur.pl to fix the errors.



Note: in the freeware version, your superuser login is your reserved admin name the login you use to delete and edit posts.




Troubleshooting

Problem 1: My image files are showing up as broken links although I am sure the urls are correct.

Solution: There are four things to check.
1. The images should not be uploaded into the cgi-bin.
2. If your icon directory is called "icons", try to rename it to something else. Some servers don't allow directories to be called icons.
3. The images should be uploaded in binary mode.
4. Posted messages won't be effected even if you have fixed the problem after.


Problem 2: I get a permission denied message when I try to post a message.

Solution: You need to chmod the messages directory to 777.



Problem 3: I get a directory or file not found message when I try to post a message.

Solution: You need to make sure the system path to the messages directory ([html documents root]/mb/board1 is correct and the directory is created.



Problem 4: I get a permission denied message when I try to view messages.

Solution: The messages should be created outside the cgi-bin.



Problem 5: I get a 500 error message only when I try to post a respond message.

Solution: Your mail program path is incorrect or you need to at -t at the end of the path.



Problem 6: I get a 500 error message when I try to view a message only on some browsers.

Solution: You need to make sure the path to cookie.js is correct in configur.pl and cookie.js should not be inside the cgi-bin.



Problem 7: My replies don't show up unless I press the refresh button on my browser.

Solution: The page is cached by the browser. Try to create the messages with .shtml extensions. Otherwise, try to insert a nocache meta tag in header.txt. A sample meta tag would be <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">.


Problem 8: I am still trying to set the board and I get a 500 error message whenever I run a script.

Solution: It is usually a problem of the perl path. You need to make sure the perl path you are using is the path to the latest version of perl on your server. Also, make sure the scripts are uploaded in ASCII mode.




©1999-2001 CGI-Factory.com of SiliconSoup.com LLC