In regards to XSLTs, I’d love some sort of registry where you could add XSLTs and then reference them elsewhere from a dropdown. As for <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16648> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16648, I’m curious why we’d have XSLTs publicly accessible. If you’re referencing “cgi-bin/koha/xslt/OPACXSLTResultsDisplay.xslt”, then anyone can come along and read what you have in your XSLT. I suppose Koha is open source, so that’s not really the end of the world, but it just seems odd to be allowing public access to that asset when you’re using it on the server. Why fetch it via Apache when you already have it on your system? Unless you’re getting a XSLT from some other server… but then it’s a separate issue. But yeah. I like the idea of a registry… where you could choose XSLTs for the Z39.50 filtering, MARCXML->HTML display, exports, etc. I’m doing OAI-PMH imports right now and I want to filter using XSLT, but it’s painful for library users to define these XSLT filepaths. There should be a simple option for users who aren’t developers/sysadmins. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595 From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Barton Chittenden Sent: Wednesday, 15 June 2016 12:20 AM To: Owen Leonard <oleonard@myacpl.org> Cc: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Using the file upload feature for more customization Owen, I've been wrestling with the issue of CSS and XSLT as well, my proposed solution is Add Content system preferences for all CSS and XSLT sysprefs that accept a URL. ( https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16648 ) that should be relatively easy to implement, simply because we can re-use code from sysprefs like intranetuserjs. I do like the idea of a flexible file uploader though; it's definitely more flexible... On Tue, Jun 14, 2016 at 9:31 AM, Owen Leonard <oleonard@myacpl.org <mailto:oleonard@myacpl.org> > wrote: Now that there is a generic file upload tool, could that be used to offer more customization options in areas where file selections are used? I'm imagining a system where you define upload categories: CSS, image, audio file, XSLT. Then wherever a setting allows you to select a file in that category Koha would list your uploaded files as options. Currently it's a problem for libraries who want to define their own set of item type icons or load a separate CSS file: Where does the file go? I just wanted to throw that idea out there in case it sounded interesting to someone. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/