Show Advanced KnowledgeHide Advanced Knowledge

Human friendly plugin administration

1 Initial Problem

Installing and managing a plugin for ILIAS is more or less a nightmare. Causes:

• There is no way to install plugins by ILIAS itself. You need to have webserver access.
• The plugin filestructure on the server is developer driven and not understandable for non develeopers (non matching mindsets)
• There is no way to update and remove plugins (remove comes with ILIAS 5.1) whithin ILIAS
• You don't have any information about newer versions of your plugins. You either have to check for updates with git on your server or browser the plugin directory (if your plugin is on that list!) and compare the version there with the version on your server

Overall, as an ILIAS-Administrator you spend plenty of time to manage plugins. Much more then for many other tasks and much more than you will need to on other systems, e.g. wordpress.

2 Conceptual Summary

In the Plugin-Administation in ILIAS it should be possible to

1. browse the directory of available plugins (e.g. the one on ilias.de)
2. install a plugin
3. see information about newer versions of the plugins
4. update a plugin

Furthermore

1. configuration of a plugin must be possible without activating it
2. optical optimization of the plugin overview panel: remove the plugin slot and component info, add the min/max ILIAS Version Info

Releated Requests

• CLI-Setup
• Enhancement of plugin administration

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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 Contact

• Author of the Request: Original request from Schmitt, Pascal, added as 5.4 request Martin Studer sr.solutions
• 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.}

6 Funding

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

• Interestet in part-funding (personal contribution), sr.solutions; 

7 Discussion

Samoila, Oliver [oliver.samoila] 30 APR 2021: Set to "Suggested for ILIAS 8"

8 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}.