Univention Bugzilla – Bug 48092
Default values for properties are not saved
Last modified: 2020-07-10 17:20:19 CEST
If I open the samba domain object in the LDAP directory browser, I always see the following notification: > Notification > The following empty properties were set to default values in the form. These > values will be applied when saving. > > General - Password - Passwords must meet complexity requirements: true > General - Password - Store plaintext passwords: false The LDAP object: root@master431:~# univention-ldapsearch sambaDomainName=DEADLOCK43 -LLL dn: sambaDomainName=DEADLOCK43,cn=samba,dc=deadlock43,dc=intranet sambaDomainName: DEADLOCK43 sambaSID: S-1-5-21-1415230736-3466347602-1585201122 objectClass: sambaDomain objectClass: univentionObject univentionObjectType: settings/sambadomain sambaNextUserRid: 1000 sambaNextGroupRid: 1000 sambaMinPwdLength: 8 univentionSamba4pwdProperties: 1 sambaPwdHistoryLength: 0 sambaNextRid: 1000 root@master431:~#
(In reply to Jürn Brodersen from comment #1) > My current workaround is a widget override on the text box with a ready > function returning a promise which is fulfilled after a 1s timeout. Not > nice, but it works for now. Let's better fix this correctly as soon as possible. 1 second can easily happen with slow network connections e.g. on mobile devices. Do you know which widgets are affected?
See also Bug #46529, which might is only a workaround for broken widgets.
The following is mostly a guess: This seems to occur with widgets that depend on widgets without a ready function (e.g. TextBox.js). Normally a widget would get its value through DetailPage.js before _getInintialValue is called. But since the dependency mechanism fills out the value, this is not guaranteed to happen In this case all values were supplied through the first udm get call without any additional umcp calls. So this does not need to be triggered through a slow network connection. But I think it might be as well if any umcp calls are involved. I would like to see a fix for this, too. :) But I think this is not trivial to fix.
The get/ call when receiving objects fill in default values into the form. But the form doesn't send all data so that only the difference / changed values are send back to the backend. Therefore for default attributes which are unset no changes are detected and not saved on modify() currently. The cause is: commit 0766ed868dd0c748a1dafdf485c748d1659ca092 Date: Fri May 12 11:17:25 2017 +0000 Bug #41053: set default values of objects when receiving form values