public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager 4/4] ui: dc options: add missing field title to registered tag edit grid
Date: Thu,  5 Nov 2026 13:53:21 +0100	[thread overview]
Message-ID: <20261105125423.3788112-5-d.csapak@proxmox.com> (raw)
In-Reply-To: <20261105125423.3788112-1-d.csapak@proxmox.com>

This header wasn't shown by accident, so it never surfaced that this was
missing. Since the header is now visible, add the proper title.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
 www/manager6/dc/RegisteredTagsEdit.js | 1 +
 1 file changed, 1 insertion(+)

diff --git a/www/manager6/dc/RegisteredTagsEdit.js b/www/manager6/dc/RegisteredTagsEdit.js
index 29aefa28..6e93c223 100644
--- a/www/manager6/dc/RegisteredTagsEdit.js
+++ b/www/manager6/dc/RegisteredTagsEdit.js
@@ -54,6 +54,7 @@ Ext.define('PVE.dc.RegisteredTagsEdit', {
                 {
                     name: 'tags',
                     xtype: 'pveListField',
+                    fieldTitle: gettext('Tag'),
                     maskRe: PVE.Utils.tagCharRegex,
                     gridConfig: {
                         height: 200,
-- 
2.47.3





  parent reply	other threads:[~2026-11-05 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 12:53 [PATCH manager 0/4] ui: small fixes for tag editing Dominik Csapak
2026-11-05 12:53 ` [PATCH manager 1/4] ui: form: list field: don't modify the class definition Dominik Csapak
2026-11-05 12:53 ` [PATCH manager 2/4] ui: form: list field: fix type for header text assignment Dominik Csapak
2026-11-05 12:53 ` [PATCH manager 3/4] ui: dc: options: add emptytext to user tag access edit grid Dominik Csapak
2026-11-05 12:53 ` Dominik Csapak [this message]
2026-11-05 23:44 ` applied: [PATCH manager 0/4] ui: small fixes for tag editing Thomas Lamprecht

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=20261105125423.3788112-5-d.csapak@proxmox.com \
    --to=d.csapak@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal