Feature Wiki
Tabs
Abandon Local `Default Access` Setting in News
Page Overview
[Hide]- 1 Reasons to Abandon Feature
- 2 Additional Information
- 2.1 Involved Authorities
- 2.2 Technical Aspects
- 2.3 Contact
- 2.4 Funding
- 3 Discussion
- 4 Implementation
1 Reasons to Abandon Feature
When creating news items, you have the option of creating them for registered users or for public access.There is a selection option (radio group) for this whilst drafting a post.
For this setting, a default access value can be set within the container in which the news item is created.
This is what we call the ‘local default’.
In addition, the same setting must be defined globally.Finally, the local default is derived from the global default, which is then displayed to the author of the news item – who can change it anyway.
We can assume that the user writing a news item wishes to make a conscious decision. We can also assume that, from an operational perspective, we want to provide a default setting.
To reduce complexity, however, we wish to remove the level of a local default.
The location of the setting to be abandoned is [Object] » Settings ›› News Settings.
2 Additional Information
2.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: Samoila, Oliver [oliver.samoila]
- Authority to Sign off Code Changes: Joußen, Thomas [tjoussen]
If this request is related to multiple components, please list both authorities for all related components.
2.2 Technical Aspects
The default setting when writing a news item will now always be taken from the global setting.
2.3 Contact
Person to be contacted in case of questions about the request or for funding offers: Samoila, Oliver [oliver.samoila]
2.4 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for abandon this feature, please get into contact with the person mentioned above as 'Contact'.
3 Discussion
Use the following discussion section to express your objections against this request or your consent to get rid of this feature.
JourFixe, ILIAS [jourfixe], 29 JUN 2026: We highly appreciate this suggestion and accept the removal of this feature for trunk.
4 Implementation
{Short description of the final implementation and possible consequences for existing installations.}
Removed Testcases
The following testcases have been removed from Testrail or modified because the feature is no longer part of the ILIAS core.
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 29. Jun 2026, 14:51, Kunkel, Matthias [mkunkel]
