Bug 55409 - Rename old settings/portal* UDM modules so they can't conflict with the new ones
Summary: Rename old settings/portal* UDM modules so they can't conflict with the new ones
Status: CLOSED FIXED
Alias: None
Product: UCS
Classification: Unclassified
Component: Portal
Version: UCS 5.0
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 5.0-4
Assignee: Florian Best
QA Contact: Dirk Wiesenthal
URL: https://git.knut.univention.de/univen...
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-10 11:20 CET by Florian Best
Modified: 2024-12-17 11:44 CET (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2022-11-10 11:20:43 CET
The old settings/portal* modules still are visible in the dropdown menus in UMC as "Portal: Entry", etc.
So they are partly duplicated because the display name of the new portal/* are identical.

Even worse is that if you want to create such portal objects underneath of cn=portal,cn=univention,$ldap_base only the old portal objects are shown because the new ones are missing `superordinate = 'settings/cn'.
Comment 2 Florian Best univentionstaff 2023-06-09 14:53:58 CEST
The Portal modules/labels are now prefixed with "Deprecated".

univention-directory-manager-modules (15.0.22-1)
0768ea54879a | feat(udm portal): rename legacy portal entries
Comment 3 Dirk Wiesenthal univentionstaff 2023-06-19 05:43:44 CEST
Naming: OK
Code review: OK
Changelog: OK
Comment 4 Philipp Hahn univentionstaff 2023-06-21 09:24:42 CEST
UCS 5.0-4 has been released:
 https://docs.software-univention.de/release-notes/5.0-4/en/

If this error occurs again, please use the 'Clone This Bug' option.