Bug #16596 Updated: Rlative directory problems in XSL files (xslt extension with Sablotron)

ID: 16596 Updated by: ruudb@stress.utwente.nl Reported By: ruudb@stress.utwente.nl -Status: Feedback +Status: Open Bug Type: Apache2 related Operating System: Linux 2.4.18 PHP Version: 4.2.0RC3 New Comment: sent example script with xsl files that reproduce the problem to aaron and sterling by e-mail Previous Comments: ------------------------------------------------------------------------ [2002-04-19 11:24:48] aaron@php.net I don't see how this is related to the apache2filter, since that module makes no assumptions about paths or current working directories. Perhaps I misunderstand the assumptions that Sablotron is expecting, please advise. ------------------------------------------------------------------------ [2002-04-15 05:22:36] ruudb@stress.utwente.nl The same problem occurs while using the fopen() function with relative paths (also in RC4) ------------------------------------------------------------------------ [2002-04-14 04:32:52] derick@php.net Fix version ------------------------------------------------------------------------ [2002-04-14 04:23:47] ruudb@stress.utwente.nl When using PHP 4.2.0RC3 with Apache 2 filter, the current directory seems to be set to / instead of the directory where the script resides (however, system("pwd); returns the correct current directory). This breaks an XML/XSL oriented website: entries in the XSL files like "<xsl:include href="file://../../xsl/html/all.xsl" />" do not work anymore. The problem does _NOT_ appear with the RC3 when using the Apache 1.3 DSO or Static SAPI in conjunction with Apache 1.3.22, but only when using the apache2filter. The versions used are Apache 2.0.35 and PHP 4.2.0 RC3. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16596&edit=1