- For Absolute Beginners
- Server Error
- Script Is Displayed, Not Executed
- Script Is Being Downloaded, Not Executed
- "Unable to open udirectory-configuration.txt" Error
- "Unable to open udirectory-categories.txt" Error
- General "Unable to open" Errors
- HTML Files Are Not Being Created
- "Goto Listings" Button Not Working
- New Listings Not Appearing On HTML Pages
1. For Absolute Beginners
If you've never installed or executed any Perl scripts on your server before, it is recommended that you first try installing our basic test script as described at our reference site:
http://www.uburst.com/uDirectory/testscript.html
This simple Perl script is the most basic of Perl scripts and should help you to understand how to install and execute scripts on your server. It also will verify that your web hosting account is configured properly to run Perl scripts and will make installing the uDirectory script that much easier.
2. Server Error
Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "Login" screen similar to when you go to the URL of the script on our site:
http://www.uburst.com/cgi-bin/udirectory/udirectory.pl
If when going to the URL of the script on your server you get a "Server Error" instead, then the problem is usually one of three things:
- The path to Perl is incorrect.
The Path to perl is specified as the very first line of the CGI scripts. Typical values are /usr/bin/perl, /usr/local/bin/perl/ and /bin/perl. If you do not know what the path to perl is on your server, then you can ask your web hosting provider. NOTE: When specifying this path to perl, you must include the "#!" in front of the path. Example: #!/usr/bin/perl
- The file was transferred in BINARY mode (as opposed to ASCII or TEXT mode).
When transferring the CGI script to your server, you must transfer it in ASCII or TEXT mode - as opposed to BINARY mode. Your FTP program should give you an option to do this - so be sure to transfer the CGI script in ASCII or TEXT mode.
- The script does not have execute permissions.
Once the CGI script is transferred to your CGI directory on your server, you must change the permissions to READ and EXECUTE (chmod 755). If your server is a UNIX server, you should be able to change the file's permissions via your FTP program. If your server is an NT server, then you may have to get your web hosting provider to make the file executable.
3. Script Is Displayed, Not Executed
Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "Login" screen similar to when you go to the URL of the script on our site:
http://www.uburst.com/cgi-bin/udirectory/udirectory.pl
If when going to the URL of the script on your server, the script is displayed instead of being executed, then the problem is usually one of three things:
- The CGI script does not have the correct file extension for your server.
That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary.
- The directory that you put the script is not configured to execute CGI
scripts.
That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.
- The permissions on the script itself are not correct.
That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.
4. Script Is Being Downloaded, Not Executed
Upon installing the script on your server, the first thing you should do is use your browser to test the script going to the URL of the script on your server. Upon doing so, you should get the "Login" screen similar to when you go to the URL of the script on our site:
http://www.uburst.com/cgi-bin/udirectory/udirectory.pl
If when going to the URL of the script on your server, the script tries to be downloaded instead of being executed, then the problem is usually one of three things:
- The CGI script does not have the correct file extension for your server.
That is, some servers are configured to only execute scripts that end in .pl and others are configured to only execute scripts that end in .cgi. Check with your web hosting server and rename the file if necessary.
- The directory that you put the script is not configured to execute CGI
scripts.
That is, usually your web hosting service will have to make a special directory for you to put your cgi scripts in such as cgi-bin or cgi-local. Again you can check with your web hosting provider.
- The permissions on the script itself are not correct.
That is, you must make sure the script has read and execute permissions. This can be done with your FTP program on UNIX machines (chmod 755). People using NT servers, may have to get their web hosting service to change the permissions to executable for them.
5. "Unable to open udirectory-configuration.txt" Error
Deluxe Edition Only - The first time you configure your listings via the "Configure Listings" button and press "Submit", uDirectory will create a configuration filed called "udirectory-configuration.txt" in your listings directory. If instead of creating this file, you get an "Unable to open udirectory-configuration.txt" Error, then the problem is usually one of two things:
- The path to your listings directory is incorrect.
That is, the directory path that you configured in question #4 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your listings directory instead of just a relative directory path. An example full path might be something like:
$html_directory = "/www/youraccount/listings/";
...on UNIX servers, or perhaps something like this:
$html_directory = "C:/users/youraccount/listings/";
....on NT servers.
Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.
- Your listings directory does not have read/write/execute permissions.
Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your listings directory has READ/WRITE permissions.
6. "Unable to open udirectory-categories.txt" Error
The first time you create a category with uDirectory, uDirectory will create a category index file called "udirectory-categories.txt" in your listings directory. If instead of creating this file, you get an "Unable to open udirectory-categories.txt" Error, then the problem is usually one of two things:
- The path to your listings directory is incorrect.
That is, the directory path that you configured in question #4 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your listings directory instead of just a relative directory path. An example full path might be something like:
$html_directory = "/www/youraccount/listings/";
...on UNIX servers, or perhaps something like this:
$html_directory = "C:/users/youraccount/listings/";
....on NT servers.
Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.
- Your listings directory does not have read/write/execute permissions.
Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your listings directory has READ/WRITE permissions.
7. General "Unable to open" Errors
"Unable to open " Errors, are usually caused by one of two things:
- The path to your listings directory is incorrect.
That is, the directory path that you configured in question #4 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your listings directory instead of just a relative directory path. An example full path might be something like:
$html_directory = "/www/youraccount/listings/";
...on UNIX servers, or perhaps something like this:
$html_directory = "C:/users/youraccount/listings/";
....on NT servers.
Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.
- Your listings directory does not have read/write/execute permissions.
Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your listings directory has READ/WRITE permissions.
8. HTML Files Are Not Being Created
If upon creating a category and/or adding listings to the category you find that the HTML files are not being created in your listings directory, then the problem is usually one of the following:
- The path to your listings directory is incorrect.
That is, the directory path that you configured in question #4 of the script setup is not correct. Double-check the value of this setting or if possible, try using the Full Directory Path to your listings directory instead of just a relative directory path. An example full path might be something like:
$html_directory = "/www/youraccount/listings/";
...on UNIX servers, or perhaps something like this:
$html_directory = "C:/users/youraccount/listings/";
....on NT servers.
Note that this is a directory path...not a URL. So it won't start with "http". If you don't know the full path to your cgi-bin directory, then ask your web hosting provider.
- Your listings directory does not have read/write/execute permissions.
Try giving the directory full READ/WRITE permissions. On UNIX servers, this can be done via a chmod 777. On NT servers, you may have to contact your web hosting provider to make sure your listings directory has READ/WRITE permissions.
- SPECIAL NOTE FOR DELUXE EDITION USERS ON NT SERVERS - Take a look in your listings directory and see if .tmp files are being created. That is, does your listings directory contain only .txt files and .tmp file - but no .html files? If so, then this is a good indication that your script does not have permission to rename files in your listings directory (The script will try to rename those .tmp files to .html files)... even though the directory does have READ/WRITE permissions. To correct this, check the actual "permissions" setting and open up the permissions such that the script does have permission to rename the files in the listings directory.
9. "Goto Listings" Button Not Working
If upon creating some categories and adding some listings to your categories, you get a "File Not Found" error when you press the "Goto Listings" button, the problem is usually caused by having the wrong directory URL specified in question 3 of the script setup. This setting should be the full URL of your listings directory.
10. New Listings Not Appearing On HTML Pages
If after adding a new listing with uDirectoryTM, you don't see the listing when you view your listing pages, the problem may be that your browser is just displaying an older version of the pages saved in cache. Try pressing "RELOAD" on your browser in order to make your browser reload the latest pages.
----------
