[Chameleon] Installing Chameleon on FC4

[Mike Leahy]

Hello list,

I'm trying to see if I can get our applications running in a Linux
environment.  I've got everything setup on FC4, with apache 2.0.54, PHP
5.0.4, MapServer 4.8.0-beta2, PHP/MapScript (this module loads fine
in-line in PHP using dl function, but fails if included in the PHP
startup - has anyone else had a similar problem?).

Here's the result of ms_GetVersion() after I dl() the mapscript module
in a PHP test script:

MapServer version 4.8.0-beta2 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG
OUTPUT=WBMP OUTPUT=PDF OUTPUT=SWF OUTPUT=SVG SUPPORTS=PROJ
SUPPORTS=FREETYPE SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT
SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER
SUPPORTS=FASTCGI SUPPORTS=GEOS INPUT=TIFF INPUT=EPPL7 INPUT=POSTGIS
INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

I've most recently tried setting up chameleon, and I'm fairly sure I've
got the chameleon.xml and cwc2.xml configuration files setup properly,
but I'm getting a blank page when I try to load one of the Chameleon
samples.  I know the sample mapfile "chameleon.map" works fine, as I can
load it directly though the mapserver cgi-bin executable as a WMS.  I
also have been able to determine that the startup sample scripts end
when the $oApp->CWCInitialize() function is executed. In the httpd
error_log file, the only notice of a problem I get is as follows:

[client 127.0.0.1] PHP Warning:  Invalid argument supplied for foreach()
in /var/www/chameleon/htdocs/common/appcontext/appcontext.php on line 276

the corresponding code in appcontext.php is:

foreach ($this->aoContext as $oContext)
{
  $result = $oContext->getContextValue( $szParam );
  if ($result !== false)
  break;
}

I've had similar 'blank page' issues when installing Chameleon in
windows.  I've also noticed many other users run into this, and it
usually relates to some configuration issue.  However, I'm at a bit of a
loss with this in my FC4 configuration.  Has anyone got a clue what
settings/requirements in PHP, Apache, or Chameleon that I have overlooked?

As an aside, does anyone know why this error doesn't get reported to the
page in the browser?  If I put an intentional syntax error, it appears
as normal in the browser...

Thanks in advance for any help,
Mike