Univention Bugzilla – Bug 52048
Remove UDM settings/portal*
Last modified: 2024-03-08 10:34:27 CET
Since UCS 5.0 settings/portal* has been replaced with portal/*. The old UDM modules should be removed.
What happens if in a 5.2/5.0 mixed domain, the 5.0 system for whatever reason was to create a settings/portal object? Don't we have to wait for yet another UCS update to remove the schema?
(In reply to Dirk Wiesenthal from comment #2) > What happens if in a 5.2/5.0 mixed domain, the 5.0 system for whatever > reason was to create a settings/portal object? Don't we have to wait for yet > another UCS update to remove the schema? Yes, that would fail. But is this done by anyone? We have the same conflict with Python 2 support for UDM. If we have a mixed 5.2/5.0 system and the 5.2 system install invalid py2-UDM modules UDM is not usable anymore on the UCS 5 system via py2.
QA: changelog: OK udm modules removed: OK upgrade check for old object: OK
univention-updater (16.0.10) 91d760e3c14b | feat(udm): remove UDM settings/portal univention-python (14.0.6) 91d760e3c14b | feat(udm): remove UDM settings/portal univention-portal (5.0.4) 91d760e3c14b | feat(udm): remove UDM settings/portal univention-management-console-module-udm (11.0.5) 91d760e3c14b | feat(udm): remove UDM settings/portal univention-directory-manager-modules (16.0.10) 91d760e3c14b | feat(udm): remove UDM settings/portal ucs-test (11.0.14) 91d760e3c14b | feat(udm): remove UDM settings/portal