In this case the cbi description div will not be generated and when
switching to another trigger later, attempts to change the description
div contents will fail.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
In this case the cbi description div will not be generated and when
switching to another trigger later, attempts to change the description
div contents will fail.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
This commit creates the possibility that not only kernel-led-triggers can
be selected but also application-led-triggers from user space.
This is done via a plugin mechanism. The application-led-triggers are scripts
that set kernel-led-triggers on system events or services. Until now this
has not been possible. The package rssileds is a kind of
application-led-trigger.
The following new packages are added:
* luci-app-ledtrig-rssi (application-led-trigger)
* luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices
* luci-app-ledtrig-usport (kernel-led-trigger) optional trigger
Since we have now a plugin mechanism I have added the following triggers
as a dependency. So this triggers are now installed per default on LuCI
installation.
* kmod-ledtrig-default-on
* kmod-ledtrig-heartbeat
* kmod-ledtrig-netdev
* kmod-ledtrig-timer
The kernel trigger kmod-ledtrig-usbdev was removed with the commit
d0b50c2770
So I have not ported the relevant code anymore.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Since the modal overlay map was unable to read the current trigger value,
it mistakingly allowed the removal of the device option value.
Fix it by finding the option object through lookupOption() instead of
relying on a reference.
Fixes: #3216
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
