Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
New Feature: custom css include #3259
This PR adds the ability for site admins to specify a custom css /path/to/css/file.css to override or supplement existing css in the Admin panel -> Setting -> System panel.
My hope is that this will at least temporarily make plugin devs have an easier time with being able to control what their plugin interface looks like. Originally I didn't include the client side, but decided that someone might want it there also. This should also be a solution for #3064
Even though I don't have tested this PR nor intend to use it, I have an idea/suggestion on how to improve it ;)
My suggestion is to define (hardcode) a custom css folder, like the plugin folder, where folks can put the css files and then select via a dropdown (with all css files of that css folder) instead of a text input field.
In case you want to do it really fancy, you could implement a multi-select dropdown, so the users/admins can select several files which will then be combined, so they'd be flexible and could keep css in several files instead of one file in case they like/want to do so.
Btw. also an Disabled or None option / value would be possible in the dropdown which is nice too I think :)
I was initially going to do that (re: hardcode dir).... but decided that I wanted people to have the freedom to not have to move their .css files out of their plugin folders. I'm all about plugins not needing to have to edit the core files to work and look the way their devs want them too.
I figured the first step was getting the concept into core, and then if people want to make it better-er (multi select drop downs, toggles to enable/disable, fancy AJAX popups, etc) they can do so.
Since there has been no commits or responses since July 2016 on the original osTicket project, I have decided to create a fork.
There are many developers who have created awesome improvements by pull requests, which are eagerly waiting for merging.
This is an attempt to incorporate most pull requests to get create an improved version of osTicket. Hopefully this can later be reintegrated in the original project, or if the original project is dead as a rebranded project.
Would you mind to offer your pull request again to this fork?