Inexplixcable! php SOMETIMES works, other times just a blank browser window!!!

celsus

I recently activated the Apache
1.3 server bundled on my Mac OS X 10.2.1. I installed a
downloaded copy of PHP 4.3.4 -- although the system itself came with PHP
4 (which I never activated).

The classic PHP info query script works just FINE.

Then I threw some simple script pages into my
site directory for testing purposes - and here it gets
weird. A few very simple scripts worked just fine, but almost
everything else I tried gave an empty browser window.

I would view the source, and the HTML parts (if any) would be present,
and the PHP part properly stripped out, but...no script executed!

WHY??

This sounds like something that people have encountered
plenty of times; I know there must be an answer.

The only (unlikely) thing that occurs to me is that Apache 1.3 despises
PHP 4.3.4. and pines for PHP4. Either that, or I need to do some kind of
tweaks on various files...?

Any feedback would be vastly appreciated; I will provide more
details if necessary.

drag0n

A blank screen might show up if you have error reportin OFF and if you have an error in your script, instead of errors being reported, it will be a blank screen with nothing excuted.

celsus

That reply came in less than five minutes!

So, where do I find this "error reporting". Which file do I need to look for..?

drag0n

php.ini

The_Chancer

Why not try the amazing

<?php
phpinfo();
?>

And see what that kicks up...

Also - make sure there are no @ symbols in your code - will block any notices / warnings..

celsus

Yes, I already tried that amazing one, first thing. And it works! I guess you mean it will kick up some precise info pertaining to the situation at hand. I'm not sure exactly what to look for there, but will look....

coditoergosum

Originally posted by celsus
... bundled on my Mac OS X 10.2.1

What might be your problem right there. 😉

That is pretty strange though. What is your code doing that is causing it? Doing any queries or opening files or anything like that?

Random errors suck. They're the hardest to troubleshoot. I would double and triple check your code to make sure it's not doing something funny. Try to narrow it down to the single line or chunk of code that causes the problem.

If you can't find any problems with your code you may want to ditch the setup that came bundled and do a fresh install. Apache 1.3 should have no problems with any version of PHP. I've used php3 and php4 with great success on 1.3 (in case you're curious: I'm running apache 2.0.14 and php5.0 b2... which runs great).

celsus

Thank you for your thoughtful analysis.

The scripts I've tried are so bonehead simple that it's hard to imagine what might be wrong with them. I didn't write them myself, but grabbed them off a free scripts website.

Clearly, the basic setup works no problemo! Phpinfo comes right up, and so do SOME others -- but not all.
So it IS looking like script errors.

In the phpnfo, I found the following, which seem relevant:

 display_errors  off    off

 error _reporting  2047  2047

I've no idea what 2047 refers to, but display_errors sounds like it ought to be ON ??

I have located the php.ini file, but it's 'invisible'.
Any hint on how to edit such files, possibly from the command line?

If I get errors to display, then I'll know whether its a code problem or something else.

I have a mind to reinstall the whole kaboodle from the CD-rom, and then activate the bundled version of PHP4 rather than the Entropy download version of 4.3.4 I'm currently running. But.....I want to ride this out to the bitter end for the sake of the learning experience and whatever guidance it may offer other newsters who happen upon this thread.

Cheers!

dalecosp

I'd have a look at the http server logs, possible some messages are there.

Yeah, if this is a devel machine, (sounds like it) you may want error reporting on in php.ini.

It is also changeable via ini_set, or just by the function [man]error-reporting/man, which, if you'll read the page, you'll see the reason for the "2047" value in the ini file....

Scripts from around the 'Net tend to be notoriously error-prone; one possibility, of course, is that they were written for register_globals=ON, which is no longer the default case when PHP is installed.....

bigswifty

for what its worth, this website does the same thing from time to time, many is the time that I will follow a link and get back raw html or a blank page with "done" in the status bar.

your problem could very well be the mac os, that can't be the most stable or bugfree apache platform available.

go buy a junkbox ibm on ebay and run linux on it, or a win nt based os.

dalecosp

Originally posted by bigswifty
your problem could very well be the mac os, that can't be the most stable or bugfree apache platform available.

go buy a junkbox ibm on ebay and run linux on it, or a win nt based os.

LOL!

Do you know what's under the hood of OSX?

coditoergosum

Originally posted by dalecosp
Do you know what's under the hood of OSX?

Sure, it runs a chopped up version of the BSD kernal, but it's not configured to run as a server... it's configured to run as a multimedia machine (which is why Apple is still in business). Out of the box I wouldn't trust it as a server in any kind of environment, but since it does run BSD behind the scenes I'm sure you could probably set it up to run well as a server.

(Does anyone know if the Apple version of Apache takes advantage of the new multi-threading capabilities of OS X?)

celsus

Aw heck, I'm so far from knowing what a BSD kernel is it'd make your skin turn blue and fall off. As for multiple threading, eh..I once worked in a textile factory where they spun thread from raw synthetic fibre, but I don't think it was a multi-threader since it only spun a single strand onto a spool. ( I believe they called it a 'gill-spinner')

As for Mac OS X server, well, if I ever get into the web hosting biz I'll get me a turbo-charged 12-cylinder muscle engine with a REAL server, but for now this OS X Apache looks like a good 'nuff injun to run as a testing server for developing apps locally along with websites. Unless wiser heads think otherwise....(?)

I'll stick doggedly to my present path and do all the digggings and debuggings to get to the bottom of present mysteries, and I am grateful for the wise counsel I have read on this board. One of these days I'll even figure out what a BSD is. (Nothing like a BLT, I hope....)

celsus

To all who have followed this thread: I have gotten into my php.ini file and done 2 things: 1) set display errors to ON, and 2.) set register globals to ON.

The effect has been absolutely ZERO. It is still doing exactly what it did before, namely, php pages have shown up blank....

Any further ideas before I reinstall the whole Mac OS X Jaguar system with its 'native' version of PHP, to see if it makes any difference.....?