"James Hughbanks" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > This is more of an apache question,
Hmm...well, I guess it's a little of both. The reason I asked here is that I didn't upgrade apache, but I did upgrade php. > but to check if the module is compiled you can do a > shell> httpd -L > but that will not work if it is a loaded module, just if you compiled > it in, Right. I'm linking to it dynamically, but the interesting thing is that looking back in my logs, I see this: [Sun Aug 10 04:02:05 2003] [notice] Apache/1.3.14 (Unix) PHP/4.0.3pl1 configured -- resuming normal operations Whereas now, I see this: [Mon Aug 18 00:36:09 2003] [notice] Apache/1.3.14 (Unix) configured -- resuming normal operations So was I really loading it dynamically, or was it linked in statically? I'm not sure, but I'm pretty sure that it was loading dynamically for a few reasons: 1) I didn't really have to change my httpsd.conf. 2) It contained an AddModule ... libexec/libphp4.so 3) libexec did, in fact, have a libphp4.so from 4.0.3 > in that case, you might be using PHP correctly, but not specifying > the AddType for PHP > [...] Like I said, I didn't really have to change anything in my .conf, and the AddTypes were already there (plus, I verified this as part of following the install steps). I agree that apache acts like the AddType is not there. But it *really* acts like libphp4.so isn't getting loaded at all. But since there is no error message in the log file saying why it isn't loading, I haven't got a clue what could be wrong. Do I need to rebuild apache? Upgrade to a newer version? Dave
