I ended up recompiling and re-installing PHP 4.3.4, and the problem went
away. Everything is functional once again.
Interesting note: The client browser was not getting cookies from the
server. However, one of the other virtual sites (not phplib) was
sending out cookies properly. I doubt anything in phpLIB was the cause,
rather it must have been something in PHP.
From: Nathaniel Price [mailto:nprice@...
Sent: Monday, January 12, 2004 4:05 PM
To: Corbin B. Siddall
Subject: Re: [Phplib-users] phpLIB 7.4 PRE2 just stopped processing
Ach! I must have missed the original email... My previous email assumed=20
that *nothing* was working and I see that that's not actually the case.=20
The steps I outlined in my email may still be useful, but I'm not sure=20
that would be the best way to approach the problem.
I would agree with Layne Weathers (who posted elsewhere in this thread),
that session problems seem to be the root of the problem. Since you are=20
using the MD5 challenge_crypt authentication, sessions have to be=20
working perfectly to allow anyone to login.
If you're using the PHP4-sessions (i.e. the actual session data is=20
handled by PHP4, and PHPlib just wraps itself around PHP4's session=20
handling with local4.inc and session4.inc), I'd check to make sure that=20
sessions are enabled and working properly in PHP4. Check the PHP=20
documentation on sessions for more info:
Also (this applies to both PHP3 and PHP4), check to make sure that=20
cookies are in fact being passed around as they should. You can check=20
this by enabling cookie notification on your browser, or by looking at=20
the HTTP headers that your browser sends to make sure it's sending the=20
cookie that PHPlib sets. If you use fallback_mode, make sure your=20
scripts add the session id to any links/urls with $sess->purl() or=20
If there's any proxy server in between you and your server, make sure=20
that it isn't interfering with cookies or anything.
Hope this helps! Sorry about the earlier post.
On 1/12/2004 1:41 PM, Nathaniel Price wrote :
> On 1/12/2004 1:07 PM, Corbin B. Siddall wrote :
>> 4. All pages do indeed have a proper open_page() that references the
>> appropriate extended class as well as ending close_page() tags.
> Unless you've changed it, the syntax should be page_open() and=20
> page_close(). However, if you say that it has been running without any
> changes at all for 11 months, that would mean one of two things:
> --page.inc or page4.inc was changed to have open_page() and=20
> close_page() functions wrap around the real functions, or the names of
> the functions themselves were changed, and somehow, your page(4).inc=20
> got reverted to the default. If page_open() isn't executed, your=20
> PHPlib-dependent scripts won't work at all.
> --You mistyped the function names in your email and the problem is=20
> something else. In that case, forget what I just said.
> In any case, since it sounds like PHPlib is not working at all, the=20
> best way to go about finding the problem would be to do the following:
> --If you've set PHP's error reporting so that it doesn't report=20
> errors, or reports fewer than the default, set it back to report E_ALL
> errors. (Remember to set it back when you're finished)
> --Make sure that prepend.php (or prepend.php3) is being included on=20
> all of your PHPlib-dependent scripts. If you use the auto_prepend_file
> php setting to include it, make sure that PHP is, in fact, doing that.
> If not, make sure that your include_path is set up to point to your=20
> phplib installation. The phpinfo() function is very useful in checking
> for this sort of thing.
> --Make sure that your local4.inc (or local.inc) configuration is set=20
> up correctly, and that your prepend.php (or prepend.php3) file is=20
> including the right set of classes for your installation.
> --Make sure that page_open() and page_close() are being executed on=20
> these pages. Make sure that the functions aren't being overridden by=20
> some other included php file that has a function of the same name=20
> within it.
> --Make sure that the class files (the *.inc files) themselves haven't=20
> been modified, or that any modifications are expected and desired (and
> bug-free, of course).
> Hate to say this, but generally things don't just "stop working".=20
> Something must have changed--I would go over things with a=20
> fine-toothed comb to find out what. If you have backups of your phplib
> installation, I'd look over those to see if there are differences with
> what you have currently.
> Hope this helps... Let us know if you find out anything more.
> Nathaniel Price
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> Phplib-users mailing list