ID: 11493
Updated by: sniper
Old-Status: Open
Status: Bogus
Bug Type: Scripting Engine problem
Operating system: 
PHP Version: 4.0.5
Assigned To: 

Let's bogus this..I wonder what was wrong too.
Maybe some old stuff? Like old php.ini? Anyway, great that it works now!


Previous Comments:

[2001-06-18 14:20:55] [EMAIL PROTECTED]
After a lot of frustration, I decided to wipe the slate clean and start over.  I 
backed up all my files and re-installed Apache 1.3.19 and PHP 4.0.5 from the bottom 
up.  And believe it or not, it works fine now.  I'm not sure why or what was causing 
this problem before, but I am no longer suffering from it.  Thanks for the attention 
you gave me, Sniper.



[2001-06-18 09:15:15] [EMAIL PROTECTED]
This is the contents of my auto_prepend_file, but this isn't giving me the issues:

    if( !isset($username) ){
        print "<html>n";
        print "<head>n";
        print "  <title>Login</title>n";
        print "</head>n";
        print "<body>n";
        print "<p align="center">n";
        print "  <font size="+4" color="red">Please Login</font>n";
        print "</p>n";
        print "<center>n";
        print "<form action=/cgi-bin/ method=POST><br>n";
        print "  Please enter your Username: <input type="text" name="usrname"><br>n";
        print "  Please enter your Password: <input type="password" 
        print "  <input type="Submit" value="Login"><br>n";
        print "</form>n";
        print "</center>n";
        print "</body>n";
        print "</html>n";

If there is no cookie set, it will show the login form and stop the browser from 
showing any more of the content of the rest of the page.  If there is a cookie set, 
then don't show the login form and show the user the actual page they wanted to see.

As for a script to reproduce this problem on your end, I'm not sure that's entirely 
possible.  From the discussions I've had with numerous people regarding this issue, 
the three systems that these people have seen this problem on are Solaris 7 and 8, and 
Sparc, all using the GCC compiler.  I myself am using Solaris 7 with the GCC compiler. 
 Now, I don't believe I can possibly give you a script to reproduce this.  Simply 
because this is an issue with the php.ini file and the PHP interpreter, rather than a 
page I might have made in PHP to do a specific task/function.  All I can offer as a 
suggestion is the following:

On a Solaris 7 machine with the GCC compiler, create a file for use as your 
auto_prepend_file(set in php.ini), then in a subdirectory of what you set as the 
prefix of your web server, in my case '/usr/local/apache/htdocs/' and then put a file 
in a subdirectory of that and try to view it through your browser.  There's no real 
script that I can write to show you this.


[2001-06-16 11:08:28] [EMAIL PROTECTED]
Please include a short example script that can be used
to reproduce this. What is in the file that is auto_prepend_file ?? 


[2001-06-15 13:40:32] [EMAIL PROTECTED]
I'm sorry, but I unfortunately don't know what you mean by that?  Do you want my 
php.ini file?  I'd try and let you see the page I'm attempting to do this on, but it's 
located on one of the server's in my company's intranet section.  I'll explain what 
I'm doing for now, and maybe that will help.

I edit my php.ini file in /usr/local/lib and change the include_path variable, then 
save those changes.  Then I stop my webserver and restart it 
(/usr/local/apache/bin/apachectl stop/start).  The changes in the error msg are 
reflected immediately at this point when I try to view the webpage.  And again, this 
works fine if I try to view a webpage located in the htdocs directory, but any file 
located in a subdirectory of htdocs produces this error.


[2001-06-15 11:43:20] [EMAIL PROTECTED]
I just tried this, and it works for me just fine.
You don't need every single directory in include_path..
That was bullshit. I should have tested it immediately.

Can you add short script into this report that reproduces this?


The remainder of the comments for this report are too long.  To view the rest of the 
comments, please view the bug report online.

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to