mirror of
https://github.com/MHSanaei/3x-ui.git
synced 2026-11-19 03:25:01 +03:00
Bulk extend client expiry / traffic + clients page polish (#4499)
* chore(sub): drop unused getFallbackMaster projectThroughFallbackMaster fully supersedes it for both panel-tracked and legacy unix-socket fallbacks. * feat(clients): bulk extend expiry / traffic for selected clients Adds POST /panel/api/clients/bulkAdjust which shifts ExpiryTime by addDays and TotalGB by addBytes for every email in one request. The endpoint is wired into the clients page through a new ClientBulkAdjustModal that opens from the existing multi-select toolbar. Clients with unlimited expiry (expiryTime=0) or unlimited traffic (totalGB=0) are skipped for the corresponding field so bulk extend never accidentally converts an unlimited client to a limited one. Negative values are allowed for refunds / corrections. Translations added for all 13 locales. * fix(db): silence GORM record-not-found spam in debug mode getSetting handles ErrRecordNotFound via database.IsNotFound and falls back to defaults, but GORM's Default logger still logs each miss as an error. With periodic jobs reading unset keys (xrayTemplateConfig, externalTrafficInformEnable) the panel log flooded thousands of times. Switch to a logger.New with IgnoreRecordNotFoundError=true so legitimate slow-query and SQL traces still surface in debug mode. * fix(clients): include inboundsById in columns memo deps Without it, the table's first paint captured an empty inboundsById and rendered each attached inbound as #<id>. Once a sort/filter forced the memo to rebuild it self-corrected, hence the visible flicker on reload. * fix(clients): handle delayed-start expiry in bulk adjust Negative ExpiryTime encodes a delay duration (magnitude = ms until the trial begins on first use). Adding positive addDays was simply arithmetically added, so e.g. a -7d delay + 30d turned into +23d since epoch (1970), making the client instantly expired. Branch on sign now: positive ExpiryTime extends additively, negative extends by subtracting so the value stays negative (more delay). Cross-sign reductions are skipped with an explicit reason instead of silently corrupting the field. * fix(clients): step traffic input by 1 GB instead of 0.1 The +/- buttons on the Total Sent/Received field nudged in 0.1 GB increments which is too granular for typical use. Set step=1 so each press moves a whole GB; users can still type decimal values directly. * fix(inbounds): step Total Flow input by 1 GB instead of 0.1 Matches the same nudge fix applied to the client form's Total Sent/Received field.
This commit is contained in:
@@ -479,8 +479,14 @@
|
||||
"deleteConfirmTitle": "删除客户端 {email}?",
|
||||
"deleteConfirmContent": "将从所有关联入站中移除该客户端并删除其流量记录。该操作不可撤销。",
|
||||
"deleteSelected": "删除 ({count})",
|
||||
"adjustSelected": "调整 ({count})",
|
||||
"bulkDeleteConfirmTitle": "删除 {count} 个客户端?",
|
||||
"bulkDeleteConfirmContent": "每个所选客户端都会从关联的入站中被移除,其流量记录也会被删除。该操作不可撤销。",
|
||||
"bulkAdjustTitle": "调整 {count} 个客户端",
|
||||
"bulkAdjustHint": "正值延长,负值减少。具有无限期限或流量的客户端将跳过该字段。",
|
||||
"bulkAdjustNothing": "应用前请设置天数或流量。",
|
||||
"addDays": "添加天数",
|
||||
"addTrafficGB": "添加流量 (GB)",
|
||||
"delDepleted": "删除已耗尽",
|
||||
"delDepletedConfirmTitle": "删除已耗尽的客户端?",
|
||||
"delDepletedConfirmContent": "删除所有流量配额已用尽或已过期的客户端。该操作不可撤销。",
|
||||
@@ -503,6 +509,8 @@
|
||||
"bulkDeletedMixed": "已删除 {ok} 个,失败 {failed} 个",
|
||||
"bulkCreated": "已创建 {count} 个客户端",
|
||||
"bulkCreatedMixed": "已创建 {ok} 个,失败 {failed} 个",
|
||||
"bulkAdjusted": "已调整 {count} 个客户端",
|
||||
"bulkAdjustedMixed": "已调整 {ok} 个,跳过 {skipped} 个",
|
||||
"delDepleted": "已删除 {count} 个已耗尽的客户端"
|
||||
}
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user