ui: lvm-thin: fix not being able to edit the storage

The change handler of the edit config from a displayEditField still
triggers, even if hidden and disabled. This then enables another
editConfig part of a displayEditField, which triggers an error in the
API.

To fix that, simply check if this field is disabled before setting
the other fields value

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/www/manager6/storage/LvmThinEdit.js b/www/manager6/storage/LvmThinEdit.js
index c3b55d87d4296ae65d21ffb6297f303c75515752..63f1fd78fe25cc954d2c0ac12849e6410945611d 100644 (file)
--- a/www/manager6/storage/LvmThinEdit.js
+++ b/www/manager6/storage/LvmThinEdit.js
@@ -148,7 +148,7 @@ Ext.define('PVE.storage.LvmThinInputPanel', {
                    },
                    change: function(f, value) {
                        let vgField = this.up('inputpanel').lookup('thinPoolSelector');
-                       if (vgField) {
+                       if (vgField && !f.isDisabled()) {
                            vgField.setDisabled(!value);
                            vgField.setVG(value);
                            vgField.setValue('');