From bd757b70e11906f9f3048382c3a85a6e93ec254b Mon Sep 17 00:00:00 2001
From: Dominik Csapak <d.csapak@proxmox.com>
Date: Tue, 21 Mar 2023 10:16:10 +0100
Subject: [PATCH] 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>
---
 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('');