Bug 33244 - Edit of existing UDM object not possible after creating a new one
Edit of existing UDM object not possible after creating a new one
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC - Domain management (Generic)
UCS 3.2
Other Linux
: P3 normal (vote)
: UCS 3.2-0-errata
Assigned To: Dirk Wiesenthal
Felix Botner
:
: 33608 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-11 13:48 CET by Alexander Kläser
Modified: 2013-11-29 11:45 CET (History)
5 users (show)

See Also:
What kind of report is it?: ---
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):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-11-11 13:48:42 CET
I think this is a generic error, but reproducible for shares:

(1) Create a new share and cancel.
(2) Try to open an existing share.

(2) is not possible as the previous reference to the dialogue for creating a new object has not been reset to null. In fact this dialogue had not been shown as there are not choices to make. In consequence every time on clicks on the item in the grid to edit it, a new DetailPage is created and positioned in the DOM, however, this page is never shown or removed.

The problem is the if case in udm.js, as this._newObjectDialog is not reset to null in this specific case:

  createDetailPage: function(...) {
      ...
      this.addChild(this._detailPage);
      if (this._newObjectDialog) {
          ...
      }
  }

Changing it to "if (ldapName) {" should be sufficient, I guess.
Comment 1 Dirk Wiesenthal univentionstaff 2013-11-11 14:11:25 CET
Better set this._newObjectDialog = null when(hideDeferred) in the context of _newObjectDialog.on('Done')
Comment 2 Erik Damrose univentionstaff 2013-11-11 14:52:45 CET
It is a generic error, i can reproduce it for groups
Comment 3 Dirk Wiesenthal univentionstaff 2013-11-20 14:48:56 CET
Fixed in
  univention-management-console-module-udm 4.0.97-2.418.201311201441

YAML created.

No changelog, no 3.2-0-next build yet.
Comment 4 Alexander Kläser univentionstaff 2013-11-28 15:19:50 CET
*** Bug 33608 has been marked as a duplicate of this bug. ***
Comment 5 Felix Botner univentionstaff 2013-11-28 16:35:21 CET
OK - could be reproduced
OK - fixed in ucs_3.2-0-errata3.2-0
OK - YAML
Comment 6 Janek Walkenhorst univentionstaff 2013-11-29 11:45:21 CET
http://errata.univention.de/ucs/3.2/3.html