From: Christian Korber <redacted>
Date: Thu, 21 May 2026 14:20:18 +0000 (+0200)
Subject: luci-base: fix order of clone bug
X-Git-Url: http://git.99rst.org/?a=commitdiff_plain;h=41e3fc3703ddf8b1ca3fb5f12ae1624110bae6f6;p=openwrt-luci.git

luci-base: fix order of clone bug

If a rule was manipulated via cli, the rule was appended to the end if
cloned.
Somehow the reason appears to be that `name` was incorrectly assigned,
because name was the event Object this way.

Signed-off-by: Christian Korber <redacted>
---

diff --git a/modules/luci-base/htdocs/luci-static/resources/form.js b/modules/luci-base/htdocs/luci-static/resources/form.js
index 3d87b3d786..54fca6930d 100644
--- a/modules/luci-base/htdocs/luci-static/resources/form.js
+++ b/modules/luci-base/htdocs/luci-static/resources/form.js
@@ -2761,7 +2761,7 @@ const CBITableSection = CBITypedSection.extend(/** @lends LuCI.form.TableSection
 	 * @param {string} name
 	 * @returns {null}
 	 */
-	handleClone(section_id, put_next, name) {
+	handleClone(section_id, put_next, ev, name) {
 		let config_name = this.uciconfig || this.map.config;
 
 		this.map.data.clone(config_name, this.sectiontype, section_id, put_next, name);