Bug #17030 [Com]: Results of "xpath_eval(...)" are not right in all cases

Edit report at https://bugs.php.net/bug.php?id=17030&edit=1 ID: 17030 Comment by: lildurk17030 at gmail dot com Reported by: ggabriel at ets-online dot de Summary: Results of "xpath_eval(...)" are not right in all cases Status: Not a bug Type: Bug Package: DOM XML related Operating System: Win2000 PHP Version: 4.2.0 Block user comment: N Private report: N New Comment: Lil Durk is a private agency dedicated to providing responsible access to legal cannabis for adults aged 19 and older. We’re an exclusively online retailer and wholesaler for recreational cannabis and a trusted source for information about cannabis and cannabis-related issues. We believe our work is meaningful and we take pride in our mandate to promote the socially responsible use of legal cannabis. https://lildurk.com/ Previous Comments: ------------------------------------------------------------------------ [2002-05-06 04:26:18] mfischer@php.net Bogussing in favour of #17032 which has the sample right (no entities). ------------------------------------------------------------------------ [2002-05-06 03:50:14] ggabriel at ets-online dot 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 https://bugs.php.net/bug.php?id=17030&edit=1