SlipCSS looks for a path to a file. It would be better if it was like the UserCSS fields for Intranet and OPAC so that the average user can just enter CSS in that field instead of needing access to a web server to upload their CSS file.
Same for NoticeCSS
*** Bug 9517 has been marked as a duplicate of this bug. ***
I'm bumping the priority on this -- it causes support issues in hosted environments -- granting partners access to those files, and supporting users who are trying to edit their own files are both pain points.
This was talked about again today at a library. Anyone interested in tackling it?
This came up again -- My thought at this point is that there should be pairs of sysprefs: xxxCSS -- the URL of the CSS -- these sysprefs already exist in Koha (SlipCSS, NoticeCSS) xxxUserCSS -- the content of the CSS page. The URL would be generated and could be used in xxxCSS. So, for example, NoticeUserCSS would contain the content of the CSS, and would be automatically be available at http://${intranet_base_url}/css/Notice.css, and NoticeCSS would then be set to the value of http://${intranet_base_url}/css/Notice.css. This means that we don't have to change SlipCSS or NoticeCSS at all -- we just need to add SlipUserCSS and NoticeUserCSS, then do a bit of configuration.
*** This bug has been marked as a duplicate of bug 16648 ***