Welp...People like myself have Links structured in a different way than the default directory configurations. I use the full absolute path to require the links.cfg file based on the different location of that file.
OTHER LINK users have done the same thing and one of the problems they confront when switching to a new domain or server is that they forget to change the absolute paths to required files in their script.
Also, in some web servers, like IIS, you have to use the full absolute path, including the drive where the file is located, when requiring files.
Example:
In IIS, you cannot use the following required file codes:
Code:
require "../data/links.cfg";
You have to use the following:
Code:
require "C:/InetPub/wwwroot/account/cgi-bin/links/data/links.cfg";
Quote:
Why would that need to be checked on, unless someone were to set Links up with a non-standard structure?
I was just providing another piece of useful information in case this person or any other person in the future has problems executing their admin.cgi file on another server.
Sorry to be helpful.
Regards,
------------------
Eliot Lee Anthro TECH,L.L.C
www.anthrotech.com ----------------------