Would it be possible to have a method to tell MT to check for updates to installed plugins (much like Firefox will check for updates to extensions)? It's difficult to keep up with upgrades or patches when you've installed more than a handful of plugins. Having a centralized method of just knowing that an update is available would be very useful. It wouldn't have to install the upgrade (though that would be pretty useful as well), just let the user know that an update is ready and where to get it.
Thanks!
Robert
Full Version: Plugin Updates
This would be a cool feature.
However, since a majority of the plugins are developed by people outside of MT, I surmise it wouldn't be their responsibility to keep up with plugin updates. The plugin developer sometimes notify MT if there is an update. And then updates are posted here.
But, if MT developed all of the plugins, then MT would provide updates as needed, just as they do for their versions of MT.
Then again, there could be someone who could develop a plugin that could keep track of updates. Who knows? ? ? ? ?
However, since a majority of the plugins are developed by people outside of MT, I surmise it wouldn't be their responsibility to keep up with plugin updates. The plugin developer sometimes notify MT if there is an update. And then updates are posted here.
But, if MT developed all of the plugins, then MT would provide updates as needed, just as they do for their versions of MT.
Then again, there could be someone who could develop a plugin that could keep track of updates. Who knows? ? ? ? ?
A system would have to established where the plugin developer would set up a small file (perhaps xml) that would have the latest version number and last updated date for this feature to check. The plugin itself would have to have code stating where that xml file is located so the update-checker would know where to look similar to how the title and documentation links are created in the system now. If that code isn't present, the plugin isn't checked.
So the developers self-select into being a part of this, but it wouldn't be a requirement. Given that people are more likely to download updates if they can find them easier than checking each web site (remember, the sixapart web site doesn't tell you it's been updated, just the latest version number, so it's up to the user to determine if it's new for them or not), this could increase plugin adoption (and donations).
Robert
So the developers self-select into being a part of this, but it wouldn't be a requirement. Given that people are more likely to download updates if they can find them easier than checking each web site (remember, the sixapart web site doesn't tell you it's been updated, just the latest version number, so it's up to the user to determine if it's new for them or not), this could increase plugin adoption (and donations).
Robert
I guess a never mind is in order. There's a pretty active thread on Pronet about this very thing today. 
Robert
Robert
Yeah, I've been reading that thread too.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.