ID: 33299
Updated by: [EMAIL PROTECTED]
Reported By: clicknmix at gmail dot com
Status: Feedback
Bug Type: XSLT related
Operating System: Linux
PHP Version: 5.0.4
New Comment:
Taking XSL out of the equation, what is returned directly from the
calling the myxml function? I cant reproduce this either (tested on
linux and windows). If the myxml function works, try building in debug
mode and set a breakpoint in the xsl extension to find out what type of
object it thinks is being returned there.
Previous Comments:
------------------------------------------------------------------------
[2005-06-15 17:28:58] jon at dsvr dot co dot uk
I've been working with Ritch on this one. He says the same code works
with 5.0.3 but not with 5.0.4, so I've compared the two source files
for the location of the bug, and nothing other than the "{{{ proto"
lines in ext/xsl/xsltprocessor.c seems to be different.
The warnings come about when you return a DOMDocument (rather than a
string) from the php:function, and this causes retval->type ==
IS_OBJECT to be true.
Now, I'm not that familiar with this code, but it seems to me that
maybe the test on line 281 should be true if the object you're
returning is a DOMDocument, and that this equality is true under 5.0.3
but false under 5.0.4, causing the equality on line 295 to be true and
thus generating the first warning as reported above.
------------------------------------------------------------------------
[2005-06-14 19:13:58] Ritch at Bugsoftware dot co dot uk
Ok,
I've spent all day recompiling php and eventualy got the script running
(clicknmix's fom above). The only way to do it was to go back a php
version... to 5.0.3.... Everything else stayed the same including the
configure command used to compile PHP and the libxml/libxslt versions;
libxml 2.6.19
libxslt 1.1.11
I'm running FC3 and clicknmix is running centos so it is a problem
across linux platforms.
I've sent my phpinfo results for both builds to clicknmix so he can
post them @;
http://home.protocol80.co.uk/php5/phpinfo.5.0.3.php.html
http://home.protocol80.co.uk/php5/phpinfo.5.0.4.php.html
This implies that there is something that has changed between these two
versions that upsets this feature. At least in certain circumstances.
Cheers,
Ritch.
------------------------------------------------------------------------
[2005-06-14 08:59:34] [EMAIL PROTECTED]
You changed 3 components at once, bad for pointing the error
at something...
As it works for me (with your combination, but on OSX, not
Linux), would it be possible for you to use the old libxml/
libxslt configuration and test that with php 5.0.4. Or use
thenew libxml/libxslt configuration with php 5.0.1? I have
no idea, what's going wrong here, but as I use that
functionality from a day-to-day basis, I can tell you, it
works for me (and I never heard of that problem before from
others using my software)
------------------------------------------------------------------------
[2005-06-13 19:17:08] clicknmix at gmail dot com
The above comment didnt make it very clear, but Ritch is running on the
same platform as me:
Linux running Apache2 with PHP 5.0.4
libxml2: 2.6.16
libxslt: 1.1.11.
The scripts do work on a previous platform:
Linux running Apache1 with PHP 5.0.1
libxml2: 2.6.8
libxslt: 1.0.19
Additional it's might be worth mentioning using the php:function to
simply return a value works fine. It's only when returning an object it
errors.
------------------------------------------------------------------------
[2005-06-13 10:30:39] Ritch at Bugsoftware dot co dot uk
I have exactley the problem described. Linux/Apache2/PHP5.0.4 with
libxml 2.6.16 & libxslt 1.1.11.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/33299
--
Edit this bug report at http://bugs.php.net/?id=33299&edit=1
