Re: [SM-USERS] Hairr pulling not helping to configure SM on NT

[p d. t. <pdo...@an...>]

1) Please try not to top-post, thanks.
2) Reply to the list, not me personally.  Others may want to see how 
this thread gets resolved - share your free help with the rest of the 
'net.  :)

> Thank you for the response. I really may be stupid, sometimes my wife thinks
> so anyway, but I think the current path definition IS the default as
> installed. It is:
> 
> /* Path for SquirrelMail required files. */
> define('SM_PATH','SMail/');

What file did you find this in?  This is NOT standard.  Someone else 
changed this, not us.  Depending on what file this is, it should be:

define('SM_PATH','../');

or

define('SM_PATH','../../');


  - paul

> Now, I may have missed something or done something dumb and that is not
> supposed to be the default. I'd love to find out I screwed up something so
> easy to correct. Based on the information I have provided, should this be
> the proper path? If not, what SHOULD it be??
> 
> Thanks - M
> 
> -----Original Message-----
> From: p dont think [mailto:pdo...@an...]
> Sent: Wednesday, September 15, 2004 6:27 PM
> To: ARC Support
> Cc: squ...@li...
> Subject: Re: [SM-USERS] Hairr pulling not helping to configure SM on NT
> 
> 
> 
> 
> ARC Support wrote:
> 
> 
>>I have been trying to get SM 1.4.3a running on NT4 SP6 with Apache 2.0.50,
>>php 5.0.1 & Mercury 4.0.1a. I've followed every hint I've been able to
> 
> glean
> 
>>from various info sites and there just isn't any doccumentation covering
> 
> the
> 
>>new releases of SM, Apache, php and Mercury. What I run into when calling
>>index.php from my smail directory (which resides in c:/
>>Apache/Apache2/htdocs) is:
>>
>>Warning: main(SMail/functions/strings.php) [function.main]: failed to open
>>stream: No such file or directory in
>>C:\Apache\Apache2\htdocs\SMail\src\login.php on line 19
>>
>>Fatal error: main() [function.require]: Failed opening required
>>'SMail/functions/strings.php' (include_path='.;C:\php5\pear') in
>>C:\Apache\Apache2\htdocs\SMail\src\login.php on line 19
>>
>>If I use absolute paths instead of the SM_PATH constant I get further.
>>Although I haven't gone all the way and put absolute paths throughout
> 
> every
> 
>>document, it seems it might work if I would. But, that isn't the goal, the
>>goal is to use the path constant ( define('SM_PATH','SMail/'); ) for ease
> 
> of
> 
>>configuration, and, as I understand it, absolute paths slow the process
> 
> way
> 
>>down.
> 
> 
> Why did you edit SM_PATH definition?  Nowhere in the docs does it say to
> do that.  The page request was made to a file in the
> c:/Apache/Apache2/htdocs/SMail/src directory, and because you fiddled
> with the SM_PATH definition, it now tries to find the included file in
> the nonexistent directory c:/Apache/Apache2/htdocs/SMail/SMail
> 
> 
>>Now, line 19 of the login.php calls:
>>require_once(SM_PATH . 'functions/strings.php');.
>>Using the absolute path it finds the file and the error message moves on
> 
> to
> 
>>the next line, and so-on. When I put in an absolute path, I can keep
> 
> moving
> 
>>ahead.
>>
>>I've tried using an absolute path for the constant, I.E.:
>>define('SM_PATH','c:/Apache/Apache2/htdocs/SMail/'); and I get access
>>violations. I have tried to make the smail directory shared with full
> 
> rights
> 
>>for everyone (I know, security risk) to no avail. At least with the
> 
> constant
> 
>>set to 'SM_PATH','SMail/' I get the above error msg (I have all reporting
>>turned on, another security issue)
> 
> 
> Change it back to what it was and start from there.  All configuration
> should be done in conf.pl or config.php if you are confident you know
> what you're doing.
> 
> Good luck,
> 
>   Paul