-
Notifications
You must be signed in to change notification settings - Fork 324
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config-mode, autoupdater: Names of branches are ignored #1961
Comments
The list is not sorted, as the site generates uci entries which in return are used to generate the dropdown in the web view. For using the name setting in the web-view you can try this patch: From cd2fbfce9a0dd29516ac8c006b39c3d81f864632 Mon Sep 17 00:00:00 2001
From: David Bauer <mail@david-bauer.net>
Date: Wed, 25 Mar 2020 17:31:43 +0100
Subject: [PATCH] gluon-web-autoupdater: use name key for prettyname
---
.../luasrc/lib/gluon/config-mode/model/admin/autoupdater.lua | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/gluon-web-autoupdater/luasrc/lib/gluon/config-mode/model/admin/autoupdater.lua b/package/gluon-web-autoupdater/luasrc/lib/gluon/config-mode/model/admin/autoupdater.lua
index adf7cbd6..7cd1e13e 100644
--- a/package/gluon-web-autoupdater/luasrc/lib/gluon/config-mode/model/admin/autoupdater.lua
+++ b/package/gluon-web-autoupdater/luasrc/lib/gluon/config-mode/model/admin/autoupdater.lua
@@ -24,7 +24,7 @@ end
o = s:option(ListValue, "branch", translate("Branch"))
uci:foreach("autoupdater", "branch",
function (section)
- o:value(section[".name"])
+ o:value(section[".name"], section["name"])
end
)
o.default = uci:get("autoupdater", autoupdater, "branch")
--
2.26.0 On first sight, the |
Thanks for the patch, I'll try! Simply omitting "name" breaks compilation:
|
@blocktrron Regarding the sorting: with the current site.conf structure, the best we could do is sort by label - which isn't too bad I guess. |
…t by label Use the value of the `name` site.conf field as label (it was accidentally unused before). Our site.conf currently doesn't define a specific order for the branch entries. To avoid changing branch orders, sort entries by this label. Fixes: #1961
…t by label Use the value of the `name` site.conf field as label (it was accidentally unused before). Our site.conf currently doesn't define a specific order for the branch entries. To avoid changing branch orders, sort entries by this label. Fixes: #1961
According to the gluon docs it is possible to give the different firmware branches names, like in this site.conf excerpt:
I would expect that the "name" would show up in Luci/Config Mode's Autoupdater module, so that the users could choose between "Maximum stability" and "Bleeding edge". But the web interface shows only "stable" and "experimental" - what's in "name" seems to be competely irrelevant - or is it shown anywhere?
Additionally the order in which the branches are shown in the web interface seems to be pretty random and neither in the same order as configured in site.conf (what I would expect) nor alphabetically.
This affects latest Gluon (2020.1), 2019 and probably all olders, too.
The text was updated successfully, but these errors were encountered: