Bug 11884 - SlipCSS and NoticeCSS should be CSS not a file
Summary: SlipCSS and NoticeCSS should be CSS not a file
Status: RESOLVED DUPLICATE of bug 16648
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P3 enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
: 9517 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-03 18:01 UTC by Nicole C. Engard
Modified: 2016-06-03 13:03 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2014-03-03 18:01:30 UTC
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.
Comment 1 Nicole C. Engard 2014-03-03 18:02:22 UTC
Same for  NoticeCSS
Comment 2 Katrin Fischer 2014-03-03 18:58:17 UTC
*** Bug 9517 has been marked as a duplicate of this bug. ***
Comment 3 Barton Chittenden 2015-05-11 21:08:34 UTC
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.
Comment 4 Nicole C. Engard 2016-01-12 15:22:59 UTC
This was talked about again today at a library.  Anyone interested in tackling it?
Comment 5 Barton Chittenden 2016-02-29 17:37:34 UTC
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.
Comment 6 Barton Chittenden 2016-06-03 13:03:07 UTC

*** This bug has been marked as a duplicate of bug 16648 ***