Configuration for Page Elements

There is a new feature request as part of the ILIAS page editor revision that tackles the described problem below, see Configuring the availability of general purpose page elements. Therefore, this request is set to "Outdated / redundant".

1 Initial Problem

With the increasing number of possible content types in an ILIAS page, we should have a general option to configure the ILIAS page editor and which types of content can be added. This would help to handle the complexitiy of this feature.

At the time being, all content types that are available for the component are presented in the drop-down and can be added to the page.

2 Conceptual Summary

• The administration of the ILIAS Page Editor should be extended and allow to enable/disable which type of page content can be added in which components.
• Listed page element types should cover native ILIAS elements as well as types provided per plugin.
• For each page element type it should be possible to choose an "In all components" and an "in none..." option. This makes it easier for administrators to set these changes.

3 User Interface Modifications

3.1 List of Affected Views

• All Page editor Edit tabs
• General Administration > Editing > ILIAS Page Editor 
  • ILIAS Learning Modules
  • Wikis
  • SCORM Editing
  • Glossaries
  • Test and Assessment
  • Repository Pages
  • (new) Portfolio
  • (new) Blogs

3.2 User Interface Details

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

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

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security Implications

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Kunkel, Matthias [mkunkel]
• Maintainer: Killing, Alexander [alex]
• 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.

• maybe by optes project

9 Discussion

JF 30 Mar 2015: We appreciate the feature and schedule it for 5.1 (global deactivation of element types for all contexts).