|Desktop Publishing theory Web Design & HTML tutorials|
Help & Contacts
a large page full of info - be patient while it loads
|also view Suggestions & Reported Problems list below|
These are not beginners scripts - Read the
supplied readme help pages - not perfect but contain plenty of info for a "free-to-use program. If you have next to no knowledge of servers, paths,
permissions checking, set-up variables importance, and logical responses to the MANY
error possibilities etc, then these scripts are not really suitable for you...
NOTE: These scripts are created as working programs for webmasters, and not the common "play with and learn" free scripts found on many sites. If you are affronted by any of this, then please use someone else's programs.
As perhaps most more complex programs and therefore extended program processes are generally obtained at cost (and therefore rarely experienced by many), the less experienced using dtp-aus.com free-to-use programs often find themselves confronted by "server specific" requirements not otherwise of any real concern when dealing with simpler programs.
dtp-aus.com programs are now downloaded 1600-2000 each week. The install success rate from downloads is very high (we do offer a low cost professional install service for those with no time, knowledge, or desire to install themselves - and the low cost for the time involved and pre/post checking we professionally perform should indicate such is offered only as a service).
MS FrontPage Extensions
PERLTEST.CGI perl CGI script is a simple script for testing your cgi-bin suitability for dtp-aus.com Perl 5 scripts. Just uncompress this .zip file on your local hard drive, check the call command to perl - first line, then FTP upload it (the script, not the .zip file) to your cgi-bin. Set the script permissions to chmod 755 and run the script from your browsers command line. It will send back a simple web page report on your perl version ( file is now supplied with all programs ). Preset the internal URL variable and you can check various Sendmail paths.
Thanks to those of you who do help by reporting back with installation info, and even with donation support - appreciating the many hours of work that go into creating free-to-use and registered scripts plus detailed "readme" support to help you create a better interactive site - All these scripts and copies of them always remain my property via Australian copyright laws, the Berne Convention, and other International treaties - including in USA!.Ron Woolley
|Reported or known problems, and Suggestions|
So like all well trained tradesmen and technicians DO NOT ASSUME ANYTHING that you did; we all make simple mistakes that can sometimes be difficult to trace with out experience and an open mind. ASCII / Binary uploading requirements and Directory/File permissions are the primary reasons for problems, followed by incorrect config paths/URLs - ie a "program" error notice indicating it cannot Read a file could be a wrong path OR wrong dir/file permissions.... and again, do not assume program faults when thousands over two years have had few problems.
This page is updated with any known major fixes or suggestions, and all programs are regularly updated /checked. We do not create and forget as is the case with many program suppliers, because as with the dtp-aus.com tutorials the aim is simple - to help other web masters with fairdinkum programs; and the time involved in doing that can never be fully compensated.
Lastly - RTBM!
As it should be, most programs have TWO passwords.
All Ron Woolley's admin supported programs have ALWAYS required double (two) passwords for access and editing. One created manually when preparing the config file set-up. The other created / encrypted when first viewing the admin pages. (if you do not appreciate why, find it bothersome to use two, and don't care that you may often allow other sites to discover your single passwords to various admin applications editing... we even discover same occassionally via our own version of LogCount / LogLook... then please do not complain!). 2001... Some public programmers? are only just recently offering same as if some newly discovered option advantage!!
The number of sites around as above is quite prolific (and often programmers of publicly available programs recommending bad installation suggestions allowing htmldocs dir installs).
CGI-BIN AND HTMLDOCS directories
...... your program paths, server paths, setup data, saved password lists, email address lists, etc could then ALL be left wide open to rogue indexing search robots and worse still - robot programs sent by mischief makers.
**The latter, if an "Access Forbidden" error is displayed, can be generated by a directory listing block YET NOT by what the server is told to restrict access to - two separate OS S/W issues.
IF your browser then attempts to show the contents of the file OR opens the "Save As" option window, without displaying an "Access Forbidden" error you are in big trouble. Contact the host technicians and request the cgi-bin be repaired (most likely all their hosted sites on the same server are likewise) OR run quickly to a decent host even if you have paid in advance!!!! The only fix for cgi and saved data in html docs directories is to move the install into a secure cgi-bin.
E-Lists v2.2 June 6th 2001
NEW Sendmail E-Mail Header Format
.CGI or .PL ?
But then there are a few servers that will run a ???.cgi program, but not accept data from a forms "POST" method resulting in very strange and uninformative results depending on program logic (possibly through cgiwrap not sending the environment array or similar).
The "@" character
As some of my programs take in auxillary files as "require" files (placed in complied memory with the program), the exclusion of the backslash before the "@" can create a server error because the compiler reads it as an out-of-context array definition.
An example of this would be the header and footer files one can edit for personalising the top and
bottom of the earlier versions of the VizBook book page - ie an e-mail address in the html code should look like you\@adomain.name. Only make this change if problems arrise and you have included the "@" character somewhere ....sometimes it is allowed because of the way the texts are used...
ie the program expects and checks for it.
VizBook v2.0a May 2000; received minor internal improvements a few days after posting.
Also UPGRADES NOTE: VizBook v2.0 will NOT allow editing of older version entries. THIS IS NOT A BUG but a result of necessary changes and addition of an ID file for this and future versions.
Also see "New Sendmail E-Mail Format" above.
Program called URLs - www.????? - not the @referer array below
If all IS DOUBLE CHECKED for permissions/paths/ASCII upload etc and confusion still reigns, make sure all config URLs contain the "www" prefix (it is believed to be a cgiwrap set-up thing!).
Under "Permissions", the readme.htm files mention the use of chmod 777 instead of 666 or 766 if paths, ascii format up loading and permissions have been individually checked.
Some servers do not allow reading and writing of directories/files using chmod 766 (r+w). For the support file subdirectories and text format files in them, chmod 777 can be tried as a last resort but also required on some servers.
May 2000: The FILES IN cgi sub dirs of all programs should first be attempted with chmod 666. This note will be addressed as program / readme pages are upgraded - eventually some files will be recommended for 664.
The following is no longer applicable to recent versions ( late 1998/early 1999 only ) but will remain for earlier version users! ...upgrade of all programs is strongly recommended.
LogCount v3.5e - SSI fix
LogCount v3.5 - @referers array
@refererers and "bad referrer" errors - "remote access denied"
This ALSO blocks access via a browsers command line AND a local pc copy of a page containing the links - even yours!
The number of persons having problems with this concept because other simple lacking programs installed do not cause the problem is amazing.
IF a program is set to use referrer checking and you disable it just because you find it bothersome not being able to use the browser command line during testing and after, then quite frankly you are an idiot! No need to try and teach a webmaster all the implications but you have been warned.
Even password access forms can be more easily cracked via remote automation if disabled!!!
NOTE: The security of the @referers array will stop you from calling a script from the command line. Use a webmasters secure page for administration links and calling programs and admin scripts - ie ONLY a link ON your site will be accepted... not even a page copy on your pc.
The @referers array in the "????.set" or "????.pl" config files (there are two types in upgrade transition), and the readme.htm direct you to change the default values to ones suitable for your domain name. THESE ARE NOT paths, but domain names and each is a reference that the scripts appends to http(s)://. This is a security feature. Some programmers even allow other characters before the "www" when code checking referrers. There are plenty of rogue PC programs that can get around referrer checking if checking is so written! Checking should be explicit - ie "https?://RefferArray_item'.
Many sites can be called via 'www.yourdomain.name' AND just 'yourdomain.name' (without the www), so this array checks to see that calls to the scripts are indeed made from pages loaded from your site, and not remote copies that can be used to spam forms and affiliate links or record incorrect counts.
Invalid entries to this array do not matter as long at least one of the two as above is correct (if pointing other domains to your site include them with and without the www too).
Referrers are notified to the server by the browser - if the viewed page is not direct from your site (a copy or browser command line direct cgi call) then the cgi program will rightly complain.
A few paranoid? servers have cgi scripts
set up under cgi wraps etc that report garbled and/or inconsistent
referrer paths. These are becoming rare. If all is double checked and the "bad referrer" error continues
to stop you using the scripts correctly through on-site pages, look for the following near the top of the scripts under
the copyright etc notices:
Try the scripts with a hash sign ( # )
placed at the beginning of these lines ie:
That will disable referrer checking; also helpful temporarily if inexperienced and testing the initial install - in other words reset it later.
DO NOT create your own CGI-BIN, or use another name just because it looks better or neater or even sounds better! - especially if you are not FULLY aware of the idiosyncrasies of your Server. If the site is supplied with a server setup cgi-bin then use it!!
DO NOT use a sub directory of the CGI-BIN, or any other directory, to place the actual scripts in unless you know that it will have full server protection and script compiling permissions (should be OK if server setup of cgi-bin is supplied with site).
DO NOT use a directory name starting with the underscore ( _ ) character if there are MS FrontPage extensions installed on the server (installed by the Host).
Note: You can use FrontPage to
create sites on your own computer, but do not publish them with FP if you
intend using perl cgi scripts on a Unix server. Use FTP ONLY for scripts / progarm files.
.ZIP Note: All zip files are created on a 'Wintel' machine. If uncompressed files are not correctly uploaded by FTP AFTER expanding locally on your PC, the hidden line endings in all files will not be converted to Unix, usually breaking a script with a 500 error. (our programs are developed in both a Windows IDE/server and Unix environment - but are not NT compatible!)
Note: dtp-aus.com programs are developed on Perl 5.004 as of June 2000 and before then just 5.003 for compatibility reasons re most servers. We would like to but do not use the latest Perl - most hosts understandably do not upgrade when ever a new version comes out.
If you obtained any of these scripts via sources other than directly from this site, you have
obtained and are using them illegally - too many problems are created by so called friends
of users (know-all idiots!), and second rate installers, and plagiarists... if you think that is "attitude" then you do not have to deal with such cretins.
If unsure of required chmod values and things do not work, change the DIR chmod to 777 (and 0777 where applicable) and try again. Some servers do not like programs creating directories - create by hand and run again to create the default files.
NOTE: We always use makedir.cgi because it does/can indicate certain requirements of a servers set-up - not just to easily create correct file names.
ennyForms name change from anyForm (March 12 '99).
Permissions / CHMOD - basics
Words and characters are:
Each represents a fixed number, and with chmod we need to know how to set each of the group of three values by totalling the read and/or write and/or execute numbers accordingly.
And there is also a group of three used for each method. They are for - the system, user group, and the world; world being any and every body (sometimes chmod values begin with a fourth number, 0, and if so should always remain as 0 - ie 0755).
So the following list should suffice for cross referencing when one method is stipulated by the author and yet only another is available in your FTP program etc:
Read = r
= a value of 4
Unix servers account for approximately 50% of ALL server configurations.
|top of page
All Scripts Outline
|Over 120 pages: All major topics divided into Classrooms|
|Free Backgrounds & Buttons!||DTP and HTML||"My First Page" HTML lessons|
|Tutorial Text Search||Perl CGI Scripts||Typography & Layout|
|4 pages of Links||Visitors Book||Perl Scripts Forum n/a|
|Free Links page||Feedback Form||Q/A contact Forum|
|pages Designed & Published - Ron F Woolley|
|©1997 '98. Last Revised: Friday, 31 October 2003 22:04|