Bug 50128 - Improve documentation of customization options
Improve documentation of customization options
Status: RESOLVED WONTFIX
Product: UCS manual
Classification: Unclassified
Component: Domain services / LDAP
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Docu maintainers
https://docs.software-univention.de/h...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-09-09 08:58 CEST by Christian Völker
Modified: 2024-04-17 13:19 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019090521000721
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Völker univentionstaff 2019-09-09 08:58:14 CEST
We have a possiblity implemented to configure the look&feel according to the needs of the customer.

I had a support case where the customer requested to change the logo on the login page. 

I recommended to simply change the underlying image file /usr/share/univention-web/js/dijit/themes/umc/images/login_logo.svn and told him it would not be update-safe.

I got blamed as we have a recommended way to do so according to our documentation. 

Forwarding the documentation to the customer he preferred to use my recommendation as he is not a native developer and no examples or explanations are given how to use the custom.css.

At least we should add an example which shows all the possible options and how to use this possibility.
Comment 1 Nico Gulden univentionstaff 2024-04-17 13:19:07 CEST
This bug hasn't seen any update for several years. I close it.

If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.