|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #35550 SchemeHandlers in xslt do not return the complete result in some cases
Submitted: 2005-12-04 22:44 UTC Modified: 2005-12-14 06:30 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: markus at emedia-solutions-wolf dot de Assigned:
Status: Wont fix Package: XSLT related
PHP Version: 4.4.1 OS: Debian/Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: markus at emedia-solutions-wolf dot de
New email:
PHP Version: OS:


 [2005-12-04 22:44 UTC] markus at emedia-solutions-wolf dot de
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="">

  <xsl:param name="site-file" select="'cocoon://abs-menulinks'"/>
  <xsl:variable name="site" select="document($site-file)"/>

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 /


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2005-12-04 22:49 UTC]
Please try using this CVS snapshot:
For Windows:

 [2005-12-04 22:51 UTC] 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-05 08:25 UTC]
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-05 08:36 UTC] markus at emedia-solutions-wolf dot de
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.
 [2005-12-14 06:30 UTC]
Only critical (read: security exploits and some crash bugs) fixes are applied for PHP 4. This is not one.
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat Nov 27 06:03:14 2021 UTC