My ISP also runs PHP as a CGI process, I set the following variables in the
index.php3 file as follows:

define ("APPLICATION_ROOT","/home/mydomain");
define ("EXTERNAL_PATH", "./");

The application_root directory is my 'home' directory on the server. Into
this directory are created the MODULES directory and the HTDOCS or WWW (your
'web root' directory)

External Path is the path from the web root to your index.php3 script. Since
my index.php3 script currently resides in my 'web root' directory, there is
no need to add any path info.


Hope this helps
mike

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Stanton Max Finley
Sent: Sunday, June 25, 2000 5:40 PM
To: FreeTrade
Subject: [FreeTrade] EXTERNAL_PATH: /cgi-bin/


My lame host has implemented PHP in my cgi-bin so, for example, when I go to
login I get the old "file not found" page because of course freetrade is
looking in the cgi-bin for the login page.  The URL I get when I go to log
in is http://www.mystyc.westhost.com/cgi-bin/index.php3?SCREEN=login Of
course my stuff in not in cgi-bin. It is in the APPLICATION_ROOT:
/www/mystyc/freetrade/ where it's supposed to be.

Now what?  Can I change EXTERNAL_PATH: to put me in the correct directory
when I try to log in?  The notes mention that this can be hardcoded.  How is
this to be done?  Or is there another work-around?

Here's what I get when I go to index.php3 in htdocs:

SERVER_NAME: www.mystyc.westhost.com
SCRIPT_NAME: index.php3
APPLICATION_ROOT: /www/mystyc/freetrade/
EXTERNAL_PATH: /cgi-bin/

Best regards,
THE newbie



------------------------------------------------------------
To subscribe:    [EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Site:            http://www.working-dogs.com/freetrade/
Problems?:       [EMAIL PROTECTED]





------------------------------------------------------------
To subscribe:    [EMAIL PROTECTED]
To unsubscribe:  [EMAIL PROTECTED]
Site:            http://www.working-dogs.com/freetrade/
Problems?:       [EMAIL PROTECTED]

Reply via email to