From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager v2 2/2] window: migrate: use predefined constant for error alert title
Date: Mon, 7 Apr 2025 11:16:28 +0200 [thread overview]
Message-ID: <20250407091647.202800-2-c.heiss@proxmox.com> (raw)
In-Reply-To: <20250407091647.202800-1-c.heiss@proxmox.com>
This is already defined, so use it where possible.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
Changes v1 -> v2:
* no changes
www/manager6/window/Migrate.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.js
index ab0239eaf..8b1dbef89 100644
--- a/www/manager6/window/Migrate.js
+++ b/www/manager6/window/Migrate.js
@@ -139,7 +139,7 @@ Ext.define('PVE.window.Migrate', {
waitMsgTarget: view,
method: 'POST',
failure: function(response, opts) {
- Ext.Msg.alert(gettext('Error'), response.htmlStatus);
+ Ext.Msg.alert(Proxmox.Utils.errorText, response.htmlStatus);
},
success: function(response, options) {
var upid = response.result.data;
@@ -201,7 +201,7 @@ Ext.define('PVE.window.Migrate', {
migrateStats = result.data;
me.fetchingNodeMigrateInfo = false;
} catch (error) {
- Ext.Msg.alert(gettext('Error'), error.htmlStatus);
+ Ext.Msg.alert(Proxmox.Utils.errorText, error.htmlStatus);
return;
}
--
2.48.1
_______________________________________________
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-04-07 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 9:16 [pve-devel] [PATCH manager v2 1/2] window: migrate: make all user-visible strings translatable Christoph Heiss
2025-04-07 9:16 ` Christoph Heiss [this message]
2025-04-07 10:06 ` Thomas Lamprecht
2025-04-07 10:49 ` 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=20250407091647.202800-2-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal