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> 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
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/