From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager 4/4] ui: dc: tag edit: use more specific documentation section
Date: Wed, 28 May 2025 11:29:24 +0200 [thread overview]
Message-ID: <20250528092927.253490-5-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250528092927.253490-1-c.heiss@proxmox.com>
Now that there is a dedicated section for configuring tags, link to that
instead of to the documentation of the datacenter configuration file.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
www/manager6/dc/OptionView.js | 2 +-
www/manager6/dc/RegisteredTagsEdit.js | 2 +-
www/manager6/dc/UserTagAccessEdit.js | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/www/manager6/dc/OptionView.js b/www/manager6/dc/OptionView.js
index 930500a61..d37bef3c1 100644
--- a/www/manager6/dc/OptionView.js
+++ b/www/manager6/dc/OptionView.js
@@ -370,7 +370,7 @@ Ext.define('PVE.dc.OptionView', {
xtype: 'proxmoxWindowEdit',
width: 800,
subject: gettext('Tag Color Override'),
- onlineHelp: 'datacenter_configuration_file',
+ onlineHelp: 'gui_tags',
fieldDefaults: {
labelWidth: 100,
},
diff --git a/www/manager6/dc/RegisteredTagsEdit.js b/www/manager6/dc/RegisteredTagsEdit.js
index b46326ae8..c3ad929b0 100644
--- a/www/manager6/dc/RegisteredTagsEdit.js
+++ b/www/manager6/dc/RegisteredTagsEdit.js
@@ -3,7 +3,7 @@ Ext.define('PVE.dc.RegisteredTagsEdit', {
alias: 'widget.pveRegisteredTagEdit',
subject: gettext('Registered Tags'),
- onlineHelp: 'datacenter_configuration_file',
+ onlineHelp: 'gui_tags',
url: '/api2/extjs/cluster/options',
diff --git a/www/manager6/dc/UserTagAccessEdit.js b/www/manager6/dc/UserTagAccessEdit.js
index 61c38c074..d9ef3f9cc 100644
--- a/www/manager6/dc/UserTagAccessEdit.js
+++ b/www/manager6/dc/UserTagAccessEdit.js
@@ -3,7 +3,7 @@ Ext.define('PVE.dc.UserTagAccessEdit', {
alias: 'widget.pveUserTagAccessEdit',
subject: gettext('User Tag Access'),
- onlineHelp: 'datacenter_configuration_file',
+ onlineHelp: 'gui_tags',
url: '/api2/extjs/cluster/options',
--
2.49.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-05-28 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 9:29 [pve-devel] [PATCH manager 0/4] improve some onlineHelp links Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 1/4] ui: qemu: AudioEdit: enable online help link Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 2/4] ui: qemu: HDTPM: " Christoph Heiss
2025-05-28 9:29 ` [pve-devel] [PATCH manager 3/4] ui: panel: TagConfig: link to more specific online help section Christoph Heiss
2025-05-28 9:29 ` Christoph Heiss [this message]
2025-07-07 9:16 ` [pve-devel] [PATCH manager 0/4] improve some onlineHelp links Christoph Heiss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250528092927.253490-5-c.heiss@proxmox.com \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.