there we implemented deleteEmpty, which we can use in some cases.
this also fixes a bug in the ControllerSelector where
an empty field would be allowed (but should not)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
when having an lxc mountpoint/rootfs on a storage which does not
allow the 'rootfs' content (e.g. somebody disabled it after creating
a container there), trying to edit the mp/rootfs broke the gui
now we check if the record exists
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
when having a simple directory as rootfs,
trying to edit it in the gui broke it, because
we tried to disable the backup checkbox which did not exists
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a subclass of Ext.form.field.Number with the settings for
Integers (allowDecimals: false and allowExponential: false and default
step size 1)
and use it where we only accept integers
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if we do not disable the storageselector with bind mounts,
it automatically sets the first storage which can hold
containers (because of allowBlank: false) and triggers
the dirty flag but clicking on reset does not delete
the value there
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the initial loading of the storage selector fires a 'change'
event via the 'onLoad' method of its parent class
at that point the value of the storage selector is empty,
and the callback function fails
