Multiple PHP Warnings in XSLTProcessor::importStylesheet()

Question

Errors:

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
Undefined variable in /transform.php on line 24

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
compilation error: file /protocols.xsl line 18 element template in /transform.php on line 24

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
Failed to compile predicate in /transform.php on line 24

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
Undefined variable in /transform.php on line 24

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
compilation error: file /home6/oneninfi/public_html/craigfreeman/iphone/project1/protocols.xsl line 22 element template in /transform.php on line 24

Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: 
Failed to compile predicate in /transform.php on line 24

Warning: XSLTProcessor::transformToXml() [xsltprocessor.transformtoxml]: 
No stylesheet associated to this object in /transform.php on line 35

PHP:

$xsl = new XSLTProcessor();
    $xsldoc = new DOMDocument();
    $xsldoc->load($_GET['xsl'].'.xsl'); // protocols.xsl
    $xsl->importStyleSheet($xsldoc); // LINE 24

    if(isset($_GET['sectionNumber']))
        $xsl->setParameter('', 'sectionNumber', $_GET['sectionNumber']);
    if(isset($_GET['protocolNumber']))
        $xsl->setParameter('', 'protocolNumber', $_GET['protocolNumber']);
    if(isset($_GET['entryNumber']))
        $xsl->setParameter('', 'entryNumber', $_GET['entryNumber']);

    $xmldoc = new DOMDocument();
    $xmldoc->load($_GET['xml'].'.xml');
    echo $xsl->transformToXML($xmldoc); // LINE 35

XSL:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:param name="protocolNumber"></xsl:param>
    <xsl:param name="sectionNumber"></xsl:param>
<xsl:output method="html" encoding="UTF-8"/>
<xsl:template match="page/section[@id=$sectionNumber]"> // LINE 18
    <xsl:apply-templates select="protocol[@id=$protocolNumber]"/>
</xsl:template>

<xsl:template match="protocol[@id=$protocolNumber]"> // LINE 22
  <h4>(<xsl:value-of select="$sectionNumber"/>.<xsl:value-of select="@id"/>)&nbsp;<xsl:value-of select="@title"/></h4>
    <!-- Applies templates to all child elements -->
    <ol><xsl:apply-templates/></ol>
</xsl:template>

<xsl:template match="start">
  <span class="start"><xsl:value-of select="@level" /></span>
</xsl:template>

<xsl:template match="stop">
  <span class="stop"><xsl:value-of select="@level" />&nbsp;STOP</span>
</xsl:template>

<xsl:template match="note">
  <span class="note"><span class="noteType"><xsl:value-of select="@title" /></span>:&nbsp;<xsl:value-of select="." /></span>
</xsl:template>

<xsl:template match="step">
   <li><span class="step"><xsl:value-of select="."/></span></li>
</xsl:template>

</xsl:stylesheet>

XML:

<?xml version="1.0" encoding="UTF-8"?>
<page type="Protocols">
    <section id="3" title="Adult Cardiac Life Support">
        <protocol id="0" title="Cardiac Arrest - General Procedures">
            <start level="All Levels"/>
                <step>Verify patient is pulseless and apneic.</step>
                <step>Initiate or continue CPR.  CPR is to be continued at all times, except during defibrillation and /or interruptions &lt; 10 sec for patient transfer.</step>
                <step>Assure airway patency and begin use of BVM.  Provide initial BLS airway management, including Oropharyngeal or Nasopharyngeal Airway.</step>
                <step>Apply AED or SAED if available.  If AED already in place, wait until current shock sequence completion to switch to another AED or manual monitor – may use previously applied patches if compatible with new unit.</step>
                <step>Follow prompts provided by AED/SAED device.</step>
                <step>Utilize ALS, or initiate timely transport toward ALS (ALS intercept or hospital if closer).  If ALS not available, no more than 3 shocks should be delivered at the scene.  Defibrillation should not be performed in a moving ambulance.</step>
                <step>Advise receiving hospital ASAP.</step>
            <stop level="EMT"/>
            <start level="EMT-I, CC &amp; P"/>
                <step>If AED/SAED not already applied, quick look using manual monitor and defibrillate PRN after CPR of at least 5 cycles (about 2 minutes).  Apply limb leads and pads in between shock sequences as appropriate.</step>
                <step>Obtain vascular access.</step>
                <step>Secure definitive airway.  If BLS airway is sufficient to maintain chest rise, continue until additional time or resources are available.  If unable to intubate, continue use of BLS airway adjuncts or use alternate airway device.<br/><br/>emove Bag Valve device whenever transferring patient, moving patient in and out of Ambulance, or other times 
when Bag Valve device may dislodge the device.<br/><br/>Reassess airway patency after any movement of patient.</step>
            <stop level="EMT-I" />
            <start level="EMT-CC &amp; P"/>
                <step>Give medications as listed in the following specific arrhythmia / dysrhythmia protocols. 
</step>
                <note title="NOTE">Should IV/IO access not be available, Epinephrine, Atropine, and Lidocaine may be administered via ETT under 
direct, on-line Medical Control.</note>
        </protocol></section></page>

PHP5 XML/XSL enabled

Thoughts? Anything obvious??

What does $xsldoc->load($_GET['xsl'].'.xsl'); return?

Ivan Nevostruev
– Ivan Nevostruev

2009-11-10 20:46:51 +00:00
Commented Nov 10, 2009 at 20:46 — Ivan Nevostruev
– Ivan Nevostruev, Commented Nov 10, 2009 at 20:46
Check my answer for exact explanation of your problem.

user357812
– user357812

2010-11-25 22:14:58 +00:00
Commented Nov 25, 2010 at 22:14 — user357812
– user357812, Commented Nov 25, 2010 at 22:14

Jim Garrison · Accepted Answer · 2009-11-10 21:17:47Z

2

One possibility is that the XSL processor is really complaining about   not being declared as an entity. Try changing the doctype to

<!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp '&#160;'> ] >

answered Nov 10, 2009 at 21:17

Jim Garrison

87k20 gold badges162 silver badges197 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

cfree Over a year ago

Good catch! It actually already is, I just cut it out to post here. I won't do that next time...

Jim Garrison Over a year ago

If that wasn't it, then I suspect a bug. I loaded your xsl verbatim into Oxygen/XML and the missing entity was the only problem. After fixing that it passes well-formedness tests.

Jim Garrison Over a year ago

I meant a bug in XSLTProcessor.importStyleSheet(), of course.

cfree Over a year ago

Thanks for checking. Yes, it's something to do with how the XSL processes in PHP. I think it doesn't like attribute comparison testing (ie: node[@id=$parameter])

Community · Accepted Answer · 2017-05-23 12:01:26Z

2

Your stylesheet is not valid XSLT 1.0: you cannot have a variable/parameter reference in a pattern

You can use variable/parameter reference in XSLT 2.0 patterns.

As suggested by @abc you need to pass that test inside the content template.

edited May 23, 2017 at 12:01

CommunityBot

11 silver badge

answered Nov 25, 2010 at 22:14

user357812

1 Comment

grantwparks Over a year ago

A couple years ago, the version of libxml our developers were using allowed variables in the match attribute, but QA was using a newer environment that failed. Trying to figure that one out remotely was fun.

Alexandru Luchian · Accepted Answer · 2009-11-10 21:08:03Z

1

Look at this error: Warning: XSLTProcessor::importStylesheet() [xsltprocessor.importstylesheet]: compilation error: file /protocols.xsl line 18 element template in /transform.php on line 24

On line 18 you have:

<xsl:template match="page/section[@id=$sectionNumber]"> // LINE 18

Where is $sectionNumber defined? PHP cannot see it.

answered Nov 10, 2009 at 21:08

Alexandru Luchian

2,7724 gold badges29 silver badges41 bronze badges

7 Comments

cfree Over a year ago

<xsl:param name="sectionNumber"></xsl:param> sets the sectionNumber parameter in the XSL passed in from the PHP $xsl->setParameter('', 'sectionNumber', $_GET['sectionNumber']);. It is accessed elsewhere in the XSL document by calling $sectionNumber

Alexandru Luchian Over a year ago

Well, anyway, it's not seeing this parameter. That's why the error it says: Undefined variable in /transform.php on line 24

cfree Over a year ago

I agree with you, though I think it's a result of the stylesheet not being imported for whatever reason.

Alexandru Luchian Over a year ago

I was able to reproduce the problem on my computer. I just didn't pass any variable/parameter. The stylesheet is not imported because the $variables get resolved to null so it's an error in the stylesheet.

cfree Over a year ago

It can't be an error, the XSL validates and displays fine using Javascript... I tried manually setting the variables inside the XSL (and not passing any variables in through PHP) and I get the same errors.

|

abc · Accepted Answer · 2010-11-25 17:40:10Z

1

Same problem here. I worked around it by enclosing 'xsl:if' nodes in the 'xsl:template' nodes. In your case, it'd give:

<xsl:template match="page/section"> // LINE 18
    <xsl:if test="@id=$sectionNumber">
        <xsl:apply-templates select="protocol[@id=$protocolNumber]"/>
    </xsl:if>
</xsl:template>

<xsl:template match="protocol"> // LINE 22
    <xsl:if test="@id=$protocolNumber">
        <h4>(<xsl:value-of select="$sectionNumber"/>.<xsl:value-of select="@id"/>)&nbsp;<xsl:value-of select="@title"/></h4>
        <!-- Applies templates to all child elements -->
        <ol><xsl:apply-templates/></ol>
    </xsl:if>
</xsl:template>

answered Nov 25, 2010 at 17:40

abc

111 bronze badge

Comments

Curtis · Accepted Answer · 2012-01-18 09:54:23Z

1

i've experienced the same issue, seems to be an issue in XSLTProcessor if you call an XSL with a parameter, define the parameter on `

<template match="/"><xsl:parameter name="whatever"/">

then you can call xslt->setParameter, it gives errors in the apache log, but it seems to work!

edited Jan 18, 2012 at 9:54

Curtis

104k69 gold badges280 silver badges359 bronze badges

answered Dec 29, 2009 at 8:56

JS.

111 bronze badge

Comments

Alexandru Luchian · Accepted Answer · 2009-11-10 20:39:46Z

0

Looks to me that $_GET['xsl'] is empty.

answered Nov 10, 2009 at 20:39

Alexandru Luchian

2,7724 gold badges29 silver badges41 bronze badges

1 Comment

cfree Over a year ago

It isn't. When I replaced the variable with 'protocols.xsl' and 'domain.com/protocols.xsl' I got the same errors...

dnagirl · Accepted Answer · 2009-11-10 20:54:58Z

0

Your xsl has an error in it. When you load it into the XSLTProcessor object, it fails. Therefore you can't apply it the the xml.

answered Nov 10, 2009 at 20:54

dnagirl

20.5k13 gold badges86 silver badges127 bronze badges

1 Comment

cfree Over a year ago

I don't think so. I don't get any errors when viewing the xsl file directly in a browser and I can get the xsl to transform the xml using Javascript (won't work in all clients, ie the PHP attempt).

Collectives™ on Stack Overflow

Multiple PHP Warnings in XSLTProcessor::importStylesheet()

7 Answers 7

4 Comments

1 Comment

7 Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

4 Comments

1 Comment

7 Comments

Comments

Comments

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related