the change handler of the edit config from a displayeditfield still triggers, even if not shown/disabled. sadly this enabled 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.csa...@proxmox.com> --- www/manager6/storage/LvmThinEdit.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/manager6/storage/LvmThinEdit.js b/www/manager6/storage/LvmThinEdit.js index c3b55d87d..63f1fd78f 100644 --- 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(''); -- 2.30.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel