$_SERVER['PATH_TRANSLATED'] is also empty in any condition.

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

This is not a bug, Apache is doing the right thing.  PATH_TRANSLATED is the translation of PATH_INFO.  See http://cgi-spec.golux.com/ 

The patch was reverted, and we're going to mark this PR as a documentation problem for the following reasons:

1. PATH_TRANSLATED itself hadn't been implemented in either Apache2 SAPI as of 4.3.2-RC1.

http://cvs.php.net/diff.php/php4/sapi/apache2filter/sapi_apache2.c?r1=1.107&r2=1.108&ty=h

2. PATH_TRANSLATED is merely a supplementary piece of information on the request URL and its availability is implementation-dependent.

3. As defined in the specification Shane mentioned, PATH_TRANSLATED should not be present when PATH_INFO is not populated because PATH_TRANSLATED is a translated form of PATH_INFO. In this point, Apache1 SAPI does somewhat an evil thing.

We recently upgraded PHP from 4.3.0 to 4.3.2, and some of
our scripts are now broken because they use PATH_TRANSLATED
to compute the document root directory of the web site,
but PATH_TRANSLATED is now empty.  Is there another reliable
method to find the document root?
We are running the NSAPI version of PHP on iPlanet 
Web Server 6.0.

Is there any chance to implement it? Some old scripts may rely on this feature, including REDIRECT_URL (used in phpdoc's livedocs).

No, read the other comments. Resetting this to a Documentation problem, which it is.

This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.

Thank you for the report, and for helping us make our documentation better.

This was already in the migration from PHP 4 to PHP 5 appendice.
I've just copied the note to the apache function reference.

I just spent a good amount of time trying to figure out why PATH_TRANSLATED suddenly stopped working on me.  Therefore I think you still have a couple documentation issues regarding this.

1) The first place I looked, and the first place I would suspect other people would look, to see if the variable stopped being supported at a certain revision is:
http://us3.php.net/reserved.variables

2) The example code for highlight_file() should be changed to not use the non-existant PATH_TRANSLATED variable:
http://us4.php.net/highlight_file

Agreed, especially since this change took place in PHP 4.3.2 and not PHP 5.0.0.  Should that note be removed from the migration5 docs?

I added a note within the PATH_TRANSLATED docs, updated the note in ref.apache, and replaced PATH_TRANSLATED with SCRIPT_FILENAME in the highlight_file() example.  Thank you Kevin for the report.

There is another open bug report out there that requests every BC break to be documented...like this one.  Once done, this information will be added there as well.

All documentation has been updated and will show up when the manual is next built. Thanks for the report.

google.com