Show Advanced KnowledgeHide Advanced Knowledge

Regulation of individual styles via RBAC / via Edit Settings

1 Initial Problem

Sometimes users come accross the option "Create Individual Style". They are delighted but do not understand the repercussions of creating their own style:

• Styles are created as fork. Later, support requests follow, why everything looks so different in their own course. (The last occurs very regularly since the new standard style with 5.4).
• Their own styles are not CI-compliant. 

Globally "Forcing a style on all objects" will supress the option to create an indiidual style. However unfortuately this is a nuclear option that does not allow for for any exceptions. But sometimes there are cases warranting style-deviations.

2 Conceptual Summary

»» The selection of the style is moved to the Settings tab. This is only accessible via the "Edit Settings" right. This significantly prevents uncontrolled growth.

3 User Interface Modifications

3.1 List of Affected Views

Subtab "Style" in Settings (e.g. Course)
Tab "Style" in process "customize page"

3.2 User Interface Details

Tab or Subtab would not be available

3.3 New User Interface Concepts

none.

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Privacy Information

It has no impact on personal data and privacy.

6 Security Implications

We do not see any changes for special security issues.

7 Contact

• Author of the Request: Samoila, Oliver [oliver.samoila]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Technische Hochschule OWL

9 Discussion

10 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.