- Detach frontend and backend operation
- Use nchan as communication channel
- Allow window to be closed while backend continues
- Use SWAL as window manager
A plugin file may include a <ALERT> tag which displays a markdown formatted message when a new version is available.
Use this to give instructions or warnings to users before the upgrade is done.
Should solve the odd problem with CA where updates effectively remove the plugin, due to user clicking the CA link to update itself, but auto update (eg) has already updated the plugin (ie: auto update updated it while the CA page was open)
Typo in my original PR #473 that prevents any plugin from installing. My bad -> happened because I was too lazy to merge into my fork the tested code and simply manually did a patch.
Currently, to use the plugin manager as an easy method of running one-off scripts that DO NOT need to be re-run at boot time, the script needs to exit with a non-zero return code to force pluginMan to not copy the .plg to /boot/config/plugins.
The trigger for this is a new <PLUGIN> attribute of "noInstall" When its value is non-null, the .plg will not get saved to /bot/config/plugins, but the .plg can still exit with a proper zero return code.
Admittedly, not too much call for this, but it would have come in handy for my Support / Project template update script for 6.4.1-rc2
plugincheck script doesn't check if a plugin is still installed. Only if the .plg still exists in /tmp/plugins. Update notices will happen until a reboot is issued
