Bug #17032 Updated: Results of "xpath_eval(...)" are not right in all cases

ID: 17032 Updated by: bigredlinux@yahoo.com Reported By: ggabriel@ets-online.de Status: Open Bug Type: DOM XML related Operating System: Win2000 PHP Version: 4.2.0 New Comment: I have been married to this extension for the last several months, so I thought I would report some info. The DOM extension as of 4.2.1 is behaving correctly, I get the expected 1 result for both queries. Perhaps the user does not have a recent enough version of libxml2 (the extension was allowing this prior to php 4.2.1). Anyway, this would not be a bug in the php extension even if it didn't work, but rather the underlying libraries and would be appropriate for the libxml2 mailing list. Close this bug, it works. Previous Comments: ------------------------------------------------------------------------ [2002-05-06 04:26:32] mfischer@php.net Re-Opening (sample is right, no entities). ------------------------------------------------------------------------ [2002-05-06 04:02:15] derick@php.net Please do not submit the same bug more than once. ------------------------------------------------------------------------ [2002-05-06 03:53:07] ggabriel@ets-online.de For the following sample: <foo> <oops> some data </oops> </foo> the following problem occured: $expr1 = "//foo"; $expr2 = "//*[name()='foo']"; $path1 = xpath_eval($context, $expr1); # no result ??? WRONG $path2 = xpath_eval($context, $expr2); # one result !!! OK The two expressions "//foo" and "//*[name()='foo']" should lead to the same result, but they do not. I have turned Off all magic_quotes in php.ini . It's to mention, that I use the PHP 4.2.0 Extensions for DOM XML support in my PHP 4.1.0 Version. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17032&edit=1