> I tried $_POST["formvariablename"] and $_ENV["envvariablename"] and I get
> javascript parse errors!  This is all getting too strange and mysterious.
> There must be something I missed out during the configuration stages.
>
> Perhaps it would help out better if you (or anyone else) could
> tell me how
> you configure the php.ini and httpd.conf files in a W2K environment using
> the latest php4 and Apache releases.


The configuration is the same regardless of server settings.

Once you turn register_globals = on, then PHP 4.2.1 should behave like your
old PHP, since that's the only setting causing problems.

The HTTP_xxx_VARS arrays *ARE* deprecated, but they still work, and
conceivably will for some time, since there's a _LOT_ of code out there that
relies on them.  I don't think the PHP guys will screw so many of their
users because of a design decision.

If you're getting javascript parse errors, then your problem is that you
have PHP code generating bad HTML and Javascript.  Javascript parsing
happens on the client side, so you need to take a look at the source you're
serving from PHP and see what the problem is.

There's a couple of likely scenarios:
*  You're writing PHP code outside of the <?php ?> delimiters.
*  You're using single-quoted strings to print variable values.
   (single-quoted strings are not parsed for variable substitution)
*  You're using a PHP extension who's API has changed.  This is the
   least likely scenario, but I've been bit by this one.  The postgres
   AND xslt extension functions have both changed since the release of
   PHP 4.0, and I've had to patch a couple sites to deal with that.


If you're still having problems, post some code snippets and we'll find
where your problems are.


take care,

nik