fix the double loadMask, (it exists, because extjs has a default
loadmask for gridpanels)
also move static configuration to class definition
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
in extjs 5/6 there is a caching issue, where they
save dom elements for reuse, but the garbage collector
can set them to null
when the framework now reuses the "cached" element it is null,
and any action on it produces an error, which breaks the site
for details see the forum link in the comment
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
when we click on a node/container/vm and quickly
click on something else, there might be a race condition,
where the store finished loading and we try to change
dom elements, which are not there anymore
so we change the store.on to me.mon, which
deletes the handler when the component is gone
in the logview panel we use API2Request, where
we cannot do this, so we check if the component
is destroyed manually
also we change this whenever we change a dom element
in a callback
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
* replace scrollable with autoScroll and move to prototype body
* use 'activate' to load store on F5
* do not set a height on the StatusView component: it hides some rows,
and the framework sets a good working default height
if the selected node has its status changed between stop &
running, the node was removed and then readded
during the remove / add process the 'selected' status of the node
was lost if it has one
instead of deleting / readding the node, we update now its content
this was the default behaviour for server nodes, but not for leaf nodes
this fixes a graphical bug where starting/stopping a VM/container would lose
the current selection in the ressource tree
instead of removing the current content and setting the new
we add the new content to the next card of the content container
(which now has the card layout, same as in the wizard)
then seamlessly change the active card, and then destroy the old card
with a delay
this has three reasons:
on a change, the panel does not flicker anymore
we give the old content time to finish ajax request (avoid race
conditions)
and we (hopefully) load the new content faster as the destroy
process can take some time
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
on destroy, stop the store loading, else
we try to update dom elements which are not there anymore
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
in the event of a destroyed or stopped object/updateStore,
we do not want to execute queued requests, thus we
need to unqueue them
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
with this patch, the upload/template buttons
are disabled, when the selected storage
has the respective contents disabled
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
move static configuration to class definition
change applyIf to apply
and change show event to activate
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
the framework triggers the convert function
when you click on a grouping header
since there is no volid there, we have to check this,
otherwise we get an error
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we move the static configuration to the class definiton
change applyIf to apply
and change the show event to activate
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we move the static configuration to the class definition
we change the deprecated autoScroll to scrollable
we change applyIf to apply (when appropriate)
we change "new Ext..." to Ext.create
we change the event from show to activate
also we change the button height of the upload to 32
so that it matches the textfield (looks weird otherwise)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we fix this by moving the static configuration (especially value and
displayfield) to the class definition
also we remove the scrollbar hack (it works properly now)
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
reasoning identic to
commit 8f8e8a2e06
adapt KVComboBoxes to pass store items using 'comboItems' parameter
commit f2782813cd
ext6migrate fix model behaviour for KVComboBox
if the files pveproxy-ssl.pem and pveproxy-ssl.key are
available for a node (i.e., in /etc/pve/<node>/), they will
be used as TLS certificate and private key for the web
interface and API of this node.
Note: the Spice and non-websocket VNC connections are still
using the self-signed certificate and key in pve-ssl.pem
and pve-ssl.key.
the intial value of the node selector is null,
but when the store is loaded, it becomes an empty array
this triggers the 'dirtychanged' event and causes
the edit windows to enable the OK/Submit Button,
even when no change is made
this fix sets the default value to an empty array,
which fixes the mentioned behaviour
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we have to move the static fields to the class
configuration, otherwise the combobox does not work
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
