Univention Bugzilla – Bug 20439
Unmoveable objects should not be displayed as movable in UMC
Last modified: 2015-11-24 10:38:24 CET
Z.Zt. kann man im UDM Richtlinien-Objekte in der Navigation zum "Verschieben" auswählen, wenn man dann aber an einer neue Position wechselt und auf "An diese Position verschieben" klickt, kommt eine Fehlermeldung, dass das Verschieben nicht erlaubt ist. Wenn Richtlinien nicht verschoben werden können (wovon ich jetzt mal ausgehe), sollten sie auch im UDM nicht als verschiebbar angeboten werden.
Das ist einem Kunden mit UCS 3.0-2 wieder aufgefallen.
This issue has been filed against UCS 2.3. UCS 2.3 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer UCS versions, please use "Clone this bug". In this case please provide detailed information on how this issue is affecting you.
Still applies to UCS 4.1.
(In reply to Alexander Kläser from comment #3) > Still applies to UCS 4.1. I mean 4.0-1 :) .
*** Bug 36688 has been marked as a duplicate of this bug. ***
Created attachment 7017 [details] patch It is really simple. The attached patch evaluates the operations 'move', 'remove' and 'edit'.
*** Bug 25329 has been marked as a duplicate of this bug. ***
(In reply to Alexander Kläser from comment #3) > Still applies to UCS 4.1. I applied that patch for UCS 4.1 :) univention-management-console-module-udm (6.0.3-1): r63302 | Bug #20439: evaluate operations 'edit', 'move', 'remove' in the frontend
OK - Bug #25329 OK - Bug #36688 OK - Unmoveable objects should not be displayed as movable OK - Changelog xml
It's not possible to edit printer groups anymore as the handler doesn't define "operations".
Fixed in svn r65384.
OK
UCS 4.1 has been released: https://docs.software-univention.de/release-notes-4.1-0-en.html https://docs.software-univention.de/release-notes-4.1-0-de.html If this error occurs again, please use "Clone This Bug".
*** Bug 32534 has been marked as a duplicate of this bug. ***
*** Bug 33169 has been marked as a duplicate of this bug. ***