Considers the newly added options from both browser local storage(preferred)
or from the datacenter config we have to save the last sorting mechanism
there, so we can detect if it changes and trigger the movement/text changes
(otherwise the tree nodes won't be updated/moved)
Signed-off-by:
namely the 'sort-field' (either vmid or name), 'group-templates' (if the
guest templates should be grouped seperately) and 'group-guest-types'
(if the guest types should be grouped or not)
Signed-off-by: Dominik Csapak
---
data/PVE/DataCenterConfig.pm | 37
in cluster options (for datacenter.cfg) and besides the view selector
(for the browser local storage)
the edit window is the same for bot but either makes an api call or
saves the resulting values into the browser local storage.
Signed-off-by: Dominik Csapak
---
not sure about just showing
we'll need it elsewhere too, and it was rather hidden in the
updateTagSettings call.
Signed-off-by: Dominik Csapak
---
www/manager6/Utils.js | 3 +++
www/manager6/dc/OptionView.js | 1 +
2 files changed, 4 insertions(+)
diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
index
this series allows configuring the sorting of the resource tree
options are the sort-field, if guest types are grouped and if templates
are grouped seperately
it's configurable in the datacenter config and the browser local storage
(latter takes precedence)
not completely sure if the
TL;DR: on Windows guests, the guest agent calls into the VSS (Volume
Shadow Copy) subsystem, which has potential to mess up applications
which hook into this themselves like SQL server, as described in the bug
report [0].
Building upon the proposal in that report, add an (default-enabled)
option
Signed-off-by: Christoph Heiss
---
www/manager6/Utils.js | 2 ++
www/manager6/form/AgentFeatureSelector.js | 30 ++-
2 files changed, 31 insertions(+), 1 deletion(-)
diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js
index d8c0bf5a..cb99d7d6
Signed-off-by: Christoph Heiss
---
qm.adoc | 20
1 file changed, 20 insertions(+)
diff --git a/qm.adoc b/qm.adoc
index 8a49283..f029ceb 100644
--- a/qm.adoc
+++ b/qm.adoc
@@ -1061,6 +1061,26 @@ operations that have the potential to write out zeros to
the storage:
On a
Signed-off-by: Christoph Heiss
---
PVE/QemuServer.pm| 8 +++-
PVE/VZDump/QemuServer.pm | 5 +
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
index e4d1a70..e409db1 100644
--- a/PVE/QemuServer.pm
+++ b/PVE/QemuServer.pm
@@
Signed-off-by: Matthias Heiserer
---
Sorry for the long delay!
v1: https://lists.proxmox.com/pipermail/pve-devel/2022-July/053599.html
Changes from v1:
use Field.calculate as suggested by Dominik
src/window/DiskSmart.js | 25 ++---
1 file changed, 22 insertions(+), 3
Am 30/01/2023 um 11:59 schrieb Leo Nunner:
> This patch fixes the issue that when the user supplied any non-standard
> repositories, the changelogs often wouldn't load. For example, providing
> both pve-no-subscription and pbs-no-subscription broke the changelog
> API, since the URL built for
Am 30/01/2023 um 11:59 schrieb Leo Nunner:
> This patch fixes the issue that when the user supplied any non-standard
> repositories, the changelogs often wouldn't load. For example, providing
> both pve-no-subscription and pbs-no-subscription broke the changelog
> API, since the URL built for
12 matches
Mail list logo
