Bug #13872 Updated: Sablotron scheme handler does not work
| From: | derick@php.net | Date: | Tue, 13 Nov 2001 10:23:21 +0000 |
| Subject: | Bug #13872 Updated: Sablotron scheme handler does not work | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-70338@lists.php.net to get a copy of this message | ||
ID: 13872
Updated by: derick
Reported By: flex@city.ee
Old Status: Feedback
Status: Closed
Bug Type: XSLT related
Operating System: Debian/Linux
PHP Version: 4.1.0RC1
Assigned To: derick
New Comment:
grrr, closed it is :)
Derick
Previous Comments:
------------------------------------------------------------------------
[2001-11-13 05:22:38] derick@php.net
This should be fixed in CVS now. Can you try it? (This fix is also applied to the PHP-4.1.0 tree).
Derick
------------------------------------------------------------------------
[2001-11-13 05:06:25] derick@php.net
Ok, another bug bites the dust!
Derick
------------------------------------------------------------------------
[2001-11-13 05:03:48] flex@city.ee
Yes, it works, at least for me.
No problems with scheme nor sax handlers now.
Thanks.
Lenar
------------------------------------------------------------------------
[2001-11-13 04:56:10] derick@php.net
This should be fixed in CVS now. Can you try it? (This fix is also applied to the PHP-4.1.0 tree).
Derick
------------------------------------------------------------------------
[2001-10-30 13:08:49] flex@city.ee
Tried to debug this and found that
XSLT_SCHEME(handle).get_all for example doesn't get set so
it returns at the start of scheme_getall function (sablot.c)
without doing anything useful.
The same error appears with xslt_set_sax_handlers when
using handler type which needs handler pair (element, document).
Seems that register_sax_handler_pair() doesn't work the way it should. I don't fully
understand how the code works so
I do not know why exactly this fails. But I hope
you got better starting point now.
------------------------------------------------------------------------
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/?id=13872
Edit this bug report at http://bugs.php.net/?id=13872&edit=1