[Koha] [EXTERNAL] Curious XSLT behavior

[David Liddle]

Thank you, Fred, for pointing out those references! Rather than edit
the files—one of which could/would be overwritten in an upgrade, I
decided to put symbolic links to the referenced files in the same
directory. Worked perfectly. And I've added a short README to that
directory so that the next goober knows what to do. Thanks again!

On Fri, Mar 17, 2023 at 3:34 PM King, Fred <Fred.King at medstar.net> wrote:
>
> This works for me for the opac xsl files, and I took a look at the intranet files and they look like they use the same system. Try this:
>
> The Detail and Results need to know the location of MARC21slimUtils.xsl. Put the full path about 9 lines down where it says
>    <xsl:import href="MARC21slimUtils.xsl"/>
>
> You also have to edit the slimUtils file to point to MARC21Languages.xsl. So again, put the full path where it says
>    <xsl:import href="MARC21Languages.xsl"/>
>
> I think you can put them on a different server, as long as Detail and Results know where to find Utils and Utils knows where to find Languages. There's a bug for this and I put the suggestion there, but now I can't find it.
>
> Fred King, MSLS, AHIP
> Medical Librarian, MedStar Washington Hospital Center
> fred.king at medstar.net
> 202-877-6670
> ORCID 0000-0001-5266-0279
> MedStar Authors Catalog: http://medstarauthors.org
>
> You know it's cold outside when you go outside and it's cold.
> --NPS Twitter
>
> -----Original Message-----
> From: Koha <koha-bounces at lists.katipo.co.nz> On Behalf Of David Liddle
> Sent: Friday, March 17, 2023 10:15 AM
> To: koha <koha at lists.katipo.co.nz>
> Subject: [EXTERNAL] [Koha] Curious XSLT behavior
>
>
>
> **ATTENTION: This email originated from outside the MedStar Health network.
>  ** DO NOT CLICK links or attachments unless you recognize the sender and know the content is safe.
>
>
>
> Greetings all! Our consortium of libraries has been using an XSLT stylesheet customized back in 2019 for "XSLTDetailsDisplay". I would like to move this file from:
>
> /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/
>
> which is not a path included when 'koha-run-backups' or 'koha-dump' is run, to:
>
> /var/lib/koha/{instance}/xslt/
>
> which is included in those backup routines. According to the manual for 22.05, which is what we're presently running, there should be no problem with doing this:
>
> https://koha-community.org/manual/22.05/en/html/staffclientpreferences.html?#xsltresultsdisplay
>
> However, I find the following:
> -- When I put the new path in "XSLTDetailsDisplay", the stylesheet is NOT employed.
> -- If I enable that new path in the web server (e.g. "/xslt") and enter the URL of the file, it is NOT employed. (I verified that it is reachable through the URL.)
> -- If I create a symbolic link from the former path to the current path, then the stylesheet IS used for display.
>
> My question is: What have I failed to do to make the desired path work directly?
>
> A related observation I have is this: It seems to me that, for consistency's sake, the XSLT and CSS preferences should function in the same fashion. Perhaps there is an under-the-hood barrier to this being the case.
>
> Thank you for reading! I'm looking forward to receiving guidance from the more experienced.
>
> David Liddle
> IT Manager
> david.liddle at wycliff.de (just not for this list)
>
> Wycliff e.V., https://wycliff.de
> Seminar für Sprache und Kultur, https://spracheundkultur.org/ Internationales Tagungszentrum Karimu, https://karimu.de _______________________________________________
>
> Koha mailing list  http://koha-community.org Koha at lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
> ----------------------------------------------------------------------
> MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopedics, cancer and GI.
>
> IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected... Thank you.
>
> Help conserve valuable resources - only print this email if necessary.
>
>