mirror of
https://github.com/4IceG/luci-app-sms-tool.git
synced 2026-04-27 03:45:48 +03:00
[GH-ISSUE #23] Error trying to go to Configuration tab #19
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/luci-app-sms-tool#19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jimbolaya on GitHub (May 16, 2023).
Original GitHub issue: https://github.com/4IceG/luci-app-sms-tool/issues/23
I am running OpenWRT v22.03.5 on x86_64.
I've downloaded and installed luci-app-sms-tool_1.9.6-20230501_all.ipk and sms-tool_2021-12-03-d38898f4-1_x86_64.ipk (since there didn't seem to be a newer one).
I've got a Quectel EC25-G modem installed and it's working great. Everything I've tried with this tool has worked, sending and receiving sms and the AT command interface.
However, when I click on the Configuration tab, I get a LuCI error:
Did I miss a dependency?
I'm not sure how to troubleshoot this myself, so I thought I should submit a report.
Thank you for making this available, it should come in handy.
@4IceG commented on GitHub (May 16, 2023):
Hi @jimbolaya ,
You are using a fairly up-to-date release of OpenWrt so I would recommend installing this version of the package https://github.com/4IceG/luci-app-sms-tool-js. An older version of the package will not work properly even with the luci-compat package installed (missing dependency).
At the beginning of the package description I explained for which version of OpenWrt the package is recommended, as you can see users do not read the description ;).
@jimbolaya commented on GitHub (May 16, 2023):
I apologize, but going back I didn't see any reference to luci-app-sms-tool-js.
It must be the fault of the translation tools.
@4IceG commented on GitHub (May 16, 2023):
Nothing wrong, I just hoped that I described everything very simply, and yet there are still problems and questions.