The Server Pages
:: TSP Menu
- Home
- Authors
- Glossary
- RSS Feed

:: Servers
- CPanel
- Hosting
- Linux
- Windows

:: Webmaster
- Databases
- Design
- Search Engines

:: Scripts
- Scripts

:: Documentation
- PHP Manual

:: Other
- Errors & Solutions
- TechPunt
- Wojjie

search for in the

xslt_set_base> <xslt_getopt
[edit] Last updated: Sat, 12 May 2012

view this page in


(PHP 4 >= 4.0.3)

xslt_processPerform an XSLT transformation


mixed xslt_process ( resource $xh , string $xmlcontainer , string $xslcontainer [, string $resultcontainer [, array $arguments [, array $parameters ]]] )

The xslt_process() function is the crux of the XSLT extension. It allows you to perform an XSLT transformation using almost any type of input source - the containers. This is accomplished through the use of argument buffers -- a concept taken from the Sablotron XSLT processor (currently the only XSLT processor this extension supports). The input containers default to a filename 'containing' the document to be processed.



The XSLT processor link identifier, created with xslt_create().


Path to XML file or placeholder for the XML argument.


Path to XSL file or placeholder for the XML argument.


The result container defaults to a filename for the transformed document. If the result container is not specified - i.e. NULL - than the result is returned.


Instead of files as the XML and XSLT arguments to the xslt_process() function, you can specify "argument place holders" which are then substituted by values given in the arguments array.


An array for any top-level parameters that will be passed to the XSLT document. These parameters can then be accessed within your XSL files using the <xsl:param name="parameter_name"> instruction. The parameters must be UTF-8 encoded and their values will be interpreted as strings by the Sablotron processor. In other words - you cannot pass node-sets as parameters to the XSLT document.

Containers can also be set via the arguments array (see below).

Return Values

Returns TRUE on success or FALSE on failure. If the result container is not specified - i.e. NULL - than the result is returned.


Version Description
4.0.6 This function no longer takes XML strings in xmlcontainer or xslcontainer. Passing a string containing XML to either of these parameters will result in a segmentation fault in Sablotron versions up to and including version 0.95.


The simplest type of transformation with the xslt_process() function is the transformation of an XML file with an XSLT file, placing the result in a third file containing the new XML (or HTML) document. Doing this with Sablotron is really quite easy...

Example #1 Using the xslt_process() to transform an XML file and a XSL file to a new XML file


// Allocate a new XSLT processor
$xh xslt_create();

// Process the document
if (xslt_process($xh'sample.xml''sample.xsl''result.xml')) {
"SUCCESS, sample.xml was transformed by sample.xsl into result.xml";
", result.xml has the following contents\n<br />\n";
} else {
"Sorry, sample.xml could not be transformed by sample.xsl into";
"  result.xml the reason is that " xslt_error($xh) . " and the ";
"error code is " xslt_errno($xh);



While this functionality is great, many times, especially in a web environment, you want to be able to print out your results directly. Therefore, if you omit the third argument to the xslt_process() function (or provide a NULL value for the argument), it will automatically return the value of the XSLT transformation, instead of writing it to a file...

Example #2 Using the xslt_process() to transform an XML file and a XSL file to a variable containing the resulting XML data


// Allocate a new XSLT processor
$xh xslt_create();

// Process the document, returning the result into the $result variable
$result xslt_process($xh'sample.xml''sample.xsl');
if (
$result) {
"SUCCESS, sample.xml was transformed by sample.xsl into the \$result";
" variable, the \$result variable has the following contents\n<br />\n";
} else {
"Sorry, sample.xml could not be transformed by sample.xsl into";
"  the \$result variable the reason is that " xslt_error($xh);
" and the error code is " xslt_errno($xh);



The above two cases are the two simplest cases there are when it comes to XSLT transformation and I'd dare say that they are the most common cases, however, sometimes you get your XML and XSLT code from external sources, such as a database or a socket. In these cases you'll have the XML and/or XSLT data in a variable -- and in production applications the overhead of dumping these to file may be too much. This is where XSLT's "argument" syntax, comes to the rescue. Instead of files as the XML and XSLT arguments to the xslt_process() function, you can specify "argument place holders" which are then substituted by values given in the arguments array (5th parameter to the xslt_process() function). The following is an example of processing XML and XSLT into a result variable without the use of files at all.

Example #3 Using the xslt_process() to transform a variable containing XML data and a variable containing XSL data into a variable containing the resulting XML data

// $xml and $xsl contain the XML and XSL data

$arguments = array(
'/_xml' => $xml,
'/_xsl' => $xsl

// Allocate a new XSLT processor
$xh xslt_create();

// Process the document
$result xslt_process($xh'arg:/_xml''arg:/_xsl'NULL$arguments);
if (
$result) {
"SUCCESS, sample.xml was transformed by sample.xsl into the \$result";
" variable, the \$result variable has the following contents\n<br />\n";
} else {
"Sorry, sample.xml could not be transformed by sample.xsl into";
"  the \$result variable the reason is that " xslt_error($xh);
" and the error code is " xslt_errno($xh);

Example #4 Passing PHP variables to XSL files


// XML string
$xml '<?xml version="1.0"?>
 change me

// XSL string
$xsl '
<xsl:stylesheet version="1.0" xmlns:xsl="">
<xsl:output method="html" encoding="ISO-8859-1" indent="no"
 omit-xml-declaration="yes"  media-type="text/html"/>
 <xsl:param name="myvar"/>
 <xsl:param name="mynode"/>
 <xsl:template match="/">
My PHP variable : <xsl:value-of select="$myvar"/><br />
My node set : <xsl:value-of select="$mynode"/>

$xh xslt_create();

// the second parameter will be interpreted as a string
$parameters = array (
'myvar' => 'test',
'mynode' => '<foo>bar</foo>'

$arguments = array (
'/_xml' => $xml,
'/_xsl' => $xsl



The above example will output:

My PHP variable : test<br>
My node set : &lt;foo&gt;bar&lt;/foo&gt;



Please note that file:// is needed in front of the path when using Windows.

xslt_set_base> <xslt_getopt
[edit] Last updated: Sat, 12 May 2012
add a note add a note User Contributed Notes xslt_process
anonymous 28-Jun-2007 08:05
It is possible that the xslt_process call can expose information about Apache's installation location if null values are passed to the signature.

for example:
= xslt_create();
$result = xslt_process($xslt, null, null);

The error you will recieve is:
Warning:  Sablotron error on line none: cannot open file 'C:\Program Files\Apache Group\Apache2/' in C:\webroot\htdocs\projects\www\sales\test.php on line 4

Although trying to read a 'null' XML file and 'null' XSL stylesheet are rather silly, consider an attacker tries to upload an arbitrary file and execute it with similar code.

the user may then gain enough information to attack your site.
16-Aug-2006 04:30
To let xslt_process() work correctly, you have to set xslt_set_base()
Here is my example code (Tested on: Windows 2000/XAMPP 1.4.15/PHP 4.4.0/Sablotron 1.0.2):

= xslt_create();
$filebase = 'file://' . getcwd () . '/test/';
$xml = 'document.xml';
$xsl = 'document.xsl';
$resultdoc = 'result.html';
$parameters = array('mynode' => '<foo>bar</foo>','sample' => 'A sample value');

$result = xslt_process($xh,$xml,$xsl,$resultdoc,NULL,$parameters);
if (!
sprintf("Cannot process XSLT document [%d]: %s",xslt_errno($xh), xslt_error($xh)));
"Result: ".$result."<br />";
?><a href="test/<?=$resultdoc?>">The result document</a><?
ken at guest dot ie 04-Apr-2006 04:46
After experiencing an ”xml declaration not at start of external entity” error with XML recieved from a remote server. The server now sends response headers back and these were getting in the way.

This fixed it:

$fp = fsockopen($queryhost, 80);
if($fp) {
    fputs($fp, $header);
    while(!feof($fp)) {
        $xml .= fgets($fp, 128);

//ensure string starts with the XML declaration.
$xml = substr($xml, strpos($xml, “<?xml”) );

$xsltproc = xslt_create();
$result = xslt_process($xsltproc,‘arg:/_xml’, $xsltfile, NULL, array(/_xml’ => $xml));
08-Jul-2005 03:35
just to let you know an an apostrophe   can generate a  "not well-formed (invalid token)" error message. I spent a couple of hours to find it, until i found another user with similar problem:
lets hope that hosting providers will soon adopt php5
csarven at gmail dot com 30-Mar-2005 07:17
I found using the output buffer to be efficient, when dealing with php scripts, with xml data.

= xslt_create();

'main.php');          //main.php contains php and xml
$xml_file = ob_get_contents();

$arguments = array('/_xml' => $xml_file);

$result = xslt_process($xh, 'arg:/_xml', 'index.xsl', NULL, $arguments);

if (!
$result) echo 'XSLT processing error: ' .xslt_error($xh) ;
else echo

ppekaar at hotmail dot com 07-Aug-2004 05:19
In response to "twa at carlbro dot dk" above I have finally solved how to combine two XML sources and one XSL stylesheet.  The above comment was nearly right,

for the php


= xslt_create();

$arguments = array('/_xml' => $xmlSingle, '/_xsl'=>$xsl, '/xml2'=>$xml_rates);
$xslResult = xslt_process($xh, 'arg:/_xml', 'single_availability_filter.xsl', NULL, $arguments,$parameters);


Please note that I have put in a blank variable "
/_xsl => $xsl", the actuall XSL file is listed directly in the xslt_process fucntion.

Note that we have a third XML data source which is called xml2 and is set a value
$xml_rates.  In your XSL stylesheet you can now call this XML data via the following line

<xsl:variable name="
filter_rates" select="document('arg:/xml2')/RackRates"/>

the missing link was putting in the the arg:/

Also please note that I am using xslt_set_base which set the base filepath for all your XSL documents.

Hope this helps. 
Justin Ramos 17-May-2004 06:24
The xslt_ functions no longer work in PHP/5.0; the XSLT extension has been removed. To apply an XSL transformation to an XML document, you must use DomDocument (from DOM) and XsltProcessor (from XSL):

= new DomDocument();
$xsl = new DomDocument;
$proc = new xsltprocessor();
ajenks at paradise dot net dot nz 07-Feb-2004 10:00
By combining some of the user added notes and some experimentation, here's how I finally got the query string broken down and passed in as top-level parameters:

With a little more effort, this could be turned into a completely generic transform script - i.e. by adding query parms for the xml and xsl files also and excluding them from the $params array (though this lat bit may not be necessary).

Thanks to all those other users whose tips make up most of this solution!


// Process query string to $params array

$vars = explode("&", $_SERVER['QUERY_STRING']);
for (
$i=0;$i<=count($vars);$i++) {
$var = explode("=", $vars[$i]);
$params[$var[0]] = $var[1];

// Fire up the engine

$xslt = xslt_create();
$xml = 'test.xml';
$xsl = 'test.xsl';

$result = xslt_process($xslt, $xml, $xsl, NULL, array(), $params);
if (
$result) {
else {
"Error:" . xslt_errno($xslt);


greg _at_ rhythmicdesign _dot_ com 22-Jan-2004 08:45
Figuring out the syntax to get parameters in was difficult but this works for me:

// Allows user to pass argument from URL as script.php?foo=VALUE

$xml = file_get_contents ('n.xml') ;
$xsl = file_get_contents ('n.xsl') ;

 // Perform the transformation
$args = array (
        '/_xml'    =>    $xml,
        '/_xsl'    =>    $xsl
$params = array (
        'foo'    =>    $foo
) ;

 $html = xslt_process($xsltproc, 'arg:/_xml', 'arg:/_xsl', NULL, $args, $params);

then in the XSL FILE:
<xsl:param name="foo"/>

<xsl:template match="/">
    <test><xsl:value-of select="$foo"/></test>


Note: the param definition and the '$' dollar sign
ohlesbeauxjours at yahoo dot fr 10-Jun-2003 05:57
Thanks, Martin !

As a matter of fact, your way of doing is probably more logical than mine :)
The point is that scheme handler strangely adds a slash to your URI , if it doesn't start by any slash.

So if you call : document('',page/@url)
...then $rest gets /

But if you call : document('',page/@url)
...then $rest gets //

Another approach could consist in enclosing the scheme "http" in the XML attribute : <page url="">
and simply doing a : $file = fopen("http:".$rest,"r");

It all depends on the context...

See also :
martin_a_thomas at yahoo dot com 27-May-2003 04:06
I had a little trouble making the http scheme handler work until I removed the line with the strip function and then changed the fopen
from 'http://' to 'http:' -

$file = fopen("http:".$rest,"r");

Regards // Martin
ohlesbeauxjours at yahoo dot fr 03-Apr-2003 06:14
The XSLT document() function can only open local files.
But thanks to the Sablotron handlers, you can easely write an http-handler (or even ftp- !!).

This sample opens a particular XHTML page on the W3C, and will parse it to get the TITLE tag content.
The interesting point, here, is that the url to open ( is defined... inside an XML  document :)

// XML content :
$xml='<?xml version="1.0"?>
    <page url="">W3C Recommendation page</page>';

// XSL content :
$xsl='<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="">
<xsl:output method="html" encoding="ISO-8859-1" indent="no" omit-xml-declaration="yes" standalone="yes" media-type="text/html"/>
<xsl:template match="/">
    The title is : <xsl:value-of select="document(concat(\'http:\',page/@url))/html/head/title"/>

function handGetAll($processor,$scheme,$rest) {
 switch($scheme) {
        case 'http':
            $file = fopen("http://".$rest,"r");
                $c .= fgets($file, 1024);
            return $c;

$xh = xslt_create();
xslt_set_scheme_handlers($xh,array("get_all" => "handGetAll"));
echo xslt_process($xh,'arg:/_xml', 'arg:/_xsl',NULL,array("/_xml"=>$xml,"/_xsl"=>$xsl));
twa at carlbro dot dk 14-Jan-2003 10:12
Hi... I'm back with the result :)

After a good discussion on the official Sablotron / PHP mailing list I found out how to fix the problem I had with PHP 4.3.0. So now I will just summarize it here. The full discussion can be found online on this address:

The problem is actually an error in my code (huh? I thought I wrote error-free code). In my XSLT file I use the document() method provided by Sablotron. In my previous example I use this syntax:
The real syntax is actually:
The reason why this worked in previous versions of PHP was due to an error in the Sablotron lib (anyway so I think).

Another thing that I would like to share is the syntax of the 2nd, 3rd and 5th argument in the xslt_process() method. In the official examples on this page the names "_xml" and "_xsl" is used. But according to the Sablotron people any name can be used. And if you are wondering if you need the preceding "/" or not - then Lenar Lhmus from the sab-php mailing list told me it would be wise to use it. Normally it works either way, but it is always the best thing to use the slash. For the full discussion on this subject see the other thread at:

twa at carlbro dot dk 13-Jan-2003 01:13
It seems to be undocumented how to get the XSL parser to use two XML files at the same time to produce the output. It is possible though. Here is how it's done with the XML data in a variable:

First you need to change the 5th argument.
$xh = xslt_create();
$args = array('/_xml'=>$xml1, '/_xsl'=>$xsl, 'xml2'=>$xml2);
$result = xslt_process($xh, 'arg:/_xml', 'arg:/_xsl', NULL, $args);

Inside the XSLT document you then need to do this:
<xsl:template match="/">
      <xsl:value-of select="/foo" />
      <xsl:value-of select="document('xml2')/bar" />

This creates a XML result containing a root node called "root" containing two nodes. One called "foo" with the content of the root node in $xml1 and one called "bar" with the content of the root node in $xml2.

In the $args array I don't know if it is best to write "'xml2'=>$xml2" or "'/xml2'=>$xml2". Both work. I think it has something to do with the level of the argument (/level1/level2/level3). Maybe this site reveals the true syntax:

I don't know if there is another - more elegant way - to do this. But I can't find any documentation on it.

For the moment I can't get this to work in PHP 4.3.0/Windows because there seems to be a problem with the Sablotron that is shipped with this version (I have not tried the UNIX version though). I think a new version of the sablot.dll will fix this problem. But for the moment I can't seem to get PHP to work with this new version. If anyone knows how to do this then please send me a mail. I'll post anything that I find out.

geiryork at start dot no 04-Jan-2003 07:43
An important detail if you want to use the last argument to include parameters to the template:
($xslt, 'foo.xml', 'foo.xslt', NULL, array(), array('foo' => 'FOO'));

In the xsl file:
<xsl:stylesheet version="1.0" xmlns:xsl="">

<xsl:param name="foo"/>
<xsl:template match="/">
<xsl:value-of select="foo"/>

Note the <xsl:param name="foo"/> is specified *outside* the template tag, but can be referenced inside it.
sanj at wiredesign dot com 11-Nov-2002 11:34
Okay, now this is a neat function once you play around with it
bit...we're basically using it in two to preview data
from a mysql database, and the other to actually publish the
output to a .htm file. The following example shows us grabbing
data from the database and then using the xslt_process() function
 to combine this data file a .xsl file residing on the server...


$query = mysql_query("select * from mytbl where mytbl_id=1");

$mydata = mysql_fetch_array($query);

$xmlString  = '<?xml version="1.0"?><data>';
$xmlString .= '<mytbl_id>'.$mydata["mytbl_id"].'</mytbl_id>';
$xmlString .= "<mytbl_title>".$mydata["mytbl_title"]."</mytbl_title>";
$xmlString .= "<mytbl_filename>".
$xmlString .= "</data>";

//create instance of xslt parser
$xh = xslt_create();

//store xmlString in an array using a key '/_xml'
$arguments = array('/_xml' => $xmlString);

//to write data to a file
xslt_process($xh, 'arg:/_xml', 'style.xsl', 'result.htm', $arguments);

//to view in brower
echo(xslt_process($xh, 'arg:/_xml', 'style.xsl', NULL, $arguments));


The above function works well, although you can't seem to view
 the resulting htm document in the browser and write to a file at
 the same time...instead you have to call the function twice, once
 to write data to a file and once to display data in a browser.

here's a simple style.xsl file that works with this example...

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="">
<xsl:template match="/">
    <h1>Here's my data!</h1>
    <xsl:value-of select="data/mytbl_title" /><br />
    <xsl:value-of select="data/mytbl_filename" /><br />


Sanj Maghera
tom at hubalek dot net 11-Nov-2002 03:52

keep in mind that fifth parameter of function xsl_process() is __arguments__ and sixth is __xsl parameters__. I spent a lot of time learning difference between arguments and parameters ;-)

jordigasulla at yahoo dot com 30-Sep-2002 02:28
The output of the XSLT process doesn't have to be necessarily HTML. If you receive a lot of data in the XML and want to distribute it along all your page, you can convert all your page to XHTML or force the output to be PHP code and then eval()uated. For instance, your XSL document (part of it) could look like:

<xsl:text disable-output-escaping="yes">$networth=</xsl:text><xsl:value-of select="networth" /><xsl:text disable-output-escaping="yes">;</xsl:text>

and your PHP code could look like:

$result = xslt_process($xh, 'arg:/_xml', 'arg:/_xsl', NULL, $arguments);
if ($result) {

that way, you can use the variable $networth in wherever you want inside your PHP file, like:

<? print $networth; ?>
dragan at iskrassoderwas dot de 01-Aug-2002 05:09
Your input into xslt-process can of course be of external-php-script-nature. This way, you can use PHP scripts that output XML code to make up the transformation:

// Transforming "Dynamic XML" through static XSL
// Gonna contain PHP-XML output
$arguments = array(
'/_xml' => $xml,

$xh = xslt_create();

// Read plain PHP-XML output
$xmlData = fopen ("http://somehost/xmloutputtingscript.php", "r");

// Stack up output into one String
while ($line = fgets ($xmlData))
$xml .= $line;

// Process the document
$result = xslt_process($xh, 'arg:/_xml', 'mystylesheet.xsl', NULL, $arguments);

// Print out your transformed document
echo $result;

j dot metzger at steptown dot com 06-Jul-2002 02:12
This in example on using variables from php in xsl-stylesheets (Sablotron 0.95)


<xsl:param name="foo" />

and how to pass the param from php to Sablotron
(I'm using Sablotron 0.95)

The php-wrapper to Sablotron has changed somewhat in 4.0.6, so I'm using the new (experimental) syntax.

Maybe this could change again in the future

I use 4.2.1 which is compiled with:
'./configure' '--with-mysql' '--with-apxs' '--enable-xslt' '--with-xslt-sablot=/usr/local/lib' '--with-expat-dir=/usr' '--with-dom' '--with-zlib-dir=/usr'

When you want to use a param passed to the xslt_process you have to put it in the top level of the xslt-script, otherwice it won't work (means: before defining any template)
Afterwards you can use the passed param with

<xsl:value-of select="$yourparamname" />

in the template.


====> xsl-stylesheet <====

<?xml version="1.0"?>

<xsl:stylesheet version="1.0"

<xsl:output method="html" version="1.0" encoding="UTF-8" indent="no" omit-xml-declaration="yes" doctype-public="-//W3C/DTD XHTML 1.0 Transitional//EN" doctype-system="" standalone="yes" media-type="text/html" />

<xsl:param name="tpsession" />

<xsl:template match="/root/output">
   this is the template stuff. and this is the param

<xsl:value-of select="$tpsession" />



====> end of xsl - stylesheet <====

o.k. -> to call the xslt_parser (Sablotron 0.95 in my case) with params do this:


/* php script */

$xh = xslt_create();
$arg = array(    '/_xml'   =>$t_xmlString,
'/_xsl'    => $t_xslString );
$param = array('tpsession' = session_name()."=".session_id());
$result = @xslt_process($xh, 'arg:/_xml', 'arg:/_xsl',NULL,$arg,$param);

/* end of php-script */


That's it -> have fun
tkearns at fastmail dot fm 10-Jun-2002 09:18
For those of you wondering what the hell is up with the very strange format for refering to in-memory data, see

normally you pass a file name (or URI) using the 'file:' syntax. The 'arg:' syntax introduced by sablotron does not refer to a file system path, it refers to an ARGument - and of course, arguments are in-memory. In the case of PHP, the argument reference is an index to the array in parameter 5 of the xslt_process() function. I think the forward slash is just to maintain the convention of path notation.

Someone with more knowledge on the topic could probably provide a more concise definition. If so, it would be nice to have it included as part of the standard documentation set.

Some wrapper functions would make things easier still.

Here's a wrapper I wrote.

function XtDataWithFile($xmlData, $uriXSLT) {
    $args = array ( '/_xml' => $xmlData );
    $xp = xslt_create();
    $out = xslt_process($xp, 'arg:/_xml', $uriXSLT, NULL, $args);
    return $out;

of course you could do XtFileWithData() can XtDataWithData()
msopacua at idg dot nl 03-Jun-2002 04:00
Took me a while to figure this one out, but no matter what your stylesheet encoding and xml encoding says - argument values, need to be UTF-8.

Version 4.2.1 and sablot 0.90.
tim at zero-interactive dot com 02-May-2002 01:11
[Editors note: this is basic URI syntax. Any URI, is specified as: <protocol>:location. Any resource, that can point to a network, needs '//' to indicate it's "network awareness". F.E.: ftp://, http:// and yes - file://.]

For those of you wanting to know how to fix the annoying bug telling you that an econding type of '' is unacceptable ....

Win2K, PHP 4.2.0

When processing files, you need to prefix each filename with "file://" or else you will get the above mentioned error.  Then you just need to set the encoding in your xslt file to get it to work.

You must use this prefix with your xml, xsl and output files if you are using all three like I am.

Happy hunting!!!
patrice dot lazareff at lbb dot fr dot invalid 18-Apr-2002 06:04
This function's syntax has changed since PHP 4.0.x, here is a quick workaround for those who use a same script with various versions.
Note that in order to work with PHP 4.0.x, the commented part must not be directly within the code (or a parse error will occur).
This is why I commented it out here and call this bit of code via an include.

// PHP 4.0.6/4.1.x difference
$minor = explode(".",phpversion());
if($minor[1] >= 1) // PHP 4.1.x -- preferred

/* here is the included code
$arguments = array(
'/_xml' => $final_xml,
'/_xsl' => $xsl_content

$html_out = xslt_process($xh, 'arg:/_xml', 'arg:/_xsl', NULL, $arguments);

end of included code */

} else // PHP 4.0.6 -- works okay
    xslt_process($xsl_content, $final_xml,$html_out);

echo $html_out;
theseer at php dot net 14-Mar-2002 07:22
Note that this extension changed quite heavily in the latest releases. The documentation and howtos on the web may not match your version of php !

To verify your extension, check the configure information

 ( <?php phpinfo(); ?> )

 for either

      --with-sablot  ( old )
    --enable-xslt --with-xslt-sablot (new).

Most ( all?) web documents i found describe the use of the old extension, which also changed in the process of development.

This extension is marked experimental for a reason ;)
lennart at rsd-online dot dk 19-Feb-2002 08:14
Relative paths using xsl:include

i addition to francis's note above you can set the base path with the xslt_set_base function like this on windows like this.

xslt_set_base('file://c:/path to xslt files/')

from you xsl file use the
<xsl:include href="file.xls">

If you wish to have full access to all files in you site only specify the root path and then use
<xsl:include href="somepath/file.xls">

God speed.
francisf at videotron dot ca 12-Feb-2002 04:00
Just because that I have look around and see other look around without any solution, so for prosperity, I give somethings that surely a lot of people know but a lot don't too.

OK, if you want to do xsl:include in your xsl file that will be parsed by your php page with xslt and sablot installed,

you have to put that in your xsl page (on a linux machine):
<xsl:include  href="file:///pathtomyxslfile/xy.xsl">

yes you do have 3 "///", the 2 first are used by sablotron and the third one is used for your path as: /pathtomyxslfile/xy.xsl

It was in the sablotron doc, well part of it.

Tested on:
php 4.1.0
sablot 0.80

Thanks you and take care.
chris_coupal at hotmail dot com 28-Jan-2002 06:06
If you are getting the data from a database and creating the XML data stream for transformation, you can add the parameters for the stylesheet into the XML data. Once in the data, you can reference them from the XSL stylesheet directly.
ascii_NO_SPAM_ at _NO_SPAM_microcore dot dk 17-Jan-2002 09:42
I noticed a slight difference in html output when upgrading to php4.1.1 on Windows.

I found the garbled output to be caused by [indent="yes"] in <xsl:output /> and simply changed it to [indent="no"].
Bill Humphries <whump at mac dot com> 06-Jan-2002 04:48
It appears that the xslt_process function does not like to have NULLs passed into it for the Argument and Parameter arrays. However, you can pass it an empty Argument array (modulo any typos):

$xh = xslt_create();
$args = array();
$params = array( 'foo' => 'bar' );
$result = xslt_process($xh,
if ($result)
 print $result;
} else {
 print "Error: ".xslt_error($xh);

That way you don't have to worry about providing methods for reading files into the argument array.

show source | credits | sitemap | contact | advertising | mirror sites