Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    p_cir_51: xml/xsl parse errors: "No template exists named patron-address-split"

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    We are getting parse errors when we try to print (mail) the overdues report from p_cir_51.

    History: we were getting parse errors. This seems to have been resolved last year by downloading new java, this did not work this time. Now we are getting the parse errors again.

    After the form opens that says "xml/xsl parse errors"

    Three pages open after clicking "ok" (I believe it is the third page you are looking for. I only show the first few lines from the first two pages with 'etc...' to note that more follows. The third page that starts "error.." is the entire error message.)

    first page:

    xmlns:xsl="" version="1.0"> <xsl:output method="xml" indent="yes"/> etc...

    second page:

    <?xml version="1.0"?>
    <subject>Notice from the Library</subject>


    third page:

    Error at xsl:call-template on line 43 of file:/C:/.../alephcom/files/ABC50/PrintTemplates/eng/overdue-summary-00.xsl:
    No template exists named patron-address-split Transformation failed: Failed to compile stylesheet. 1 error detected.

    The message: "No template exists named patron-address-split" appears because a ./form_eng/overdue-summary-nn.xsl or plain-overdue-summary-nn.xsl (called by p_file_51) has the following line:

    <xsl:call-template name="patron-address-split"/>

    The system then looks for a line like the following in funcs-address.xsl (or plain-funcs-address.xsl):

    <xsl:template name="patron-address-split">

    The ./abc01/form_eng/funcs-address.xsl (the generic form) did not have such an "patron-address-split" template -- but the generic *did* include patron-address-direct , which is also needed.

    I copied the lines for the "patron-address-direct" from the old, customized form into the new funcs-address.xsl: from:

    <xsl:template name="patron-address-direct">



    so that funcs-address.xsl now has both the "patron-address" and the "patron-address-split" -- (and have run util i/6 to recreate the html.pck).

    Once the pc client doing this printing is restarted, or "Connect" is done and the new html.pck is transferred, you should no longer see the "No template exists named patron-address-split" message.

    • Article last edited: 10/8/2013