The Spark tries to check for plugin updates by downloading their descriptions from the http://www.igniterealtime.org/updater/plugins.jsp
It would be really good if anyone can fix it.
The Spark tries to check for plugin updates by downloading their descriptions from the http://www.igniterealtime.org/updater/plugins.jsp
It would be really good if anyone can fix it.
I am unsure what is happening. On the server I verified
<Parameter name="spark-plugins-path" value="/staticfiles/builds/spark/plugins"/>
$ ls /staticfiles/builds/spark/plugins
sparkphone.jar transferguard.jar translator.jar
Probably need @guus help here.
ok, I created a ticket [SPARK-2345] - Ignite Realtime Jira to not forget about this.
Err, I wonder if downloadable plugins for Spark were ever a thing? We do not have them listed on the website, for example. As far as I know, Spark bundles plugins in its installation, but doesn’t download them separately.
Do Spark instances in the wild already perform these update checks? Upon a successful check, what do clients do? Automatically install things? Pop up a confirmation dialog?
I worry about accidentally breaking every Spark client out there by re-enabling (or possibly enabling for the first time) this feature again.
Yes, it will show a confirmation dialog with the Install button that will download a plugin.
If we fix the directory then yes, it may be a lot of clients will show the message.
We can limit their amount by rising the minimal required version, and it’s better to do given how many plugins wasn’t re-tested in a while.
There is also a security risk because the plugin updater doesn’t verify TLS cert. So it may be better to fix the updater and release a now version of the Spark itself.
BTW the default plugin URL also can be changed for new versions. This may be another way to prevent unexpected plugin updates in old clients