ID: 35550 User updated by: markus at emedia-solutions-wolf dot de Reported By: markus at emedia-solutions-wolf dot de Status: Open Bug Type: XSLT related Operating System: Debian/Linux PHP Version: 4.4.1 New Comment:
Ok thanks. I've already filed a bug at sablotron also. Maybe this get's fixed, otherwise I have to switch to PHP5, but this is still a bit hard at many webhosters. Previous Comments: ------------------------------------------------------------------------ [2005-12-05 08:25:56] [EMAIL PROTECTED] AFAIK, there's noone feeling responsible (and noone with the needed knowledge) for the Sablotron support in PHP 4 right now in the developer team. Maybe you're in luck and someone knows the inner workings of this extension and is in the mood to fix it, but I wouldn't count on it. The last real commit was almost 3 years ago. But in general, PHP4 with Sablotron is dead since a looong time, better switch to PHP 5 sooner than later :) ------------------------------------------------------------------------ [2005-12-04 22:51:42] markus at emedia-solutions-wolf dot de Doesn't has PHP5 another XSLT processor instead of Sablotron? Then it would by no means backward compatible and is useless for me at the current state of development, since I need PHP4 support. I've also checked the sablot version and I have 1.0.2 installed which is the latest release for now. ------------------------------------------------------------------------ [2005-12-04 22:49:23] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.1-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.1-win32-latest.zip ------------------------------------------------------------------------ [2005-12-04 22:44:32] markus at emedia-solutions-wolf dot de Description: ------------ I tried to use the scheme handlers from sablot but have an irritating issue. I'd like to create a cocoon compatible framework with php and therefore some extensive xslt processing is required. There could be some types of custom schemes in the xsl stylesheets like 'cocoon:/something' or 'cocoon://somethingelse'. The first case (cocoon:/) works as expected, but the second part gives me only '/' as rest instead of '/somethingelse' or even better '//somethingelse'. Reproduce code: --------------- <?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> <xsl:param name="site-file" select="'cocoon://abs-menulinks'"/> <xsl:variable name="site" select="document($site-file)"/> </xsl:stylesheet> Expected result: ---------------- For my registered scheme handler I expected to get 'cocoon' as scheme (this does work) and '//abs-menulinks' as rest. Actual result: -------------- The rest only contains the leading / ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=35550&edit=1
