Closed volomike closed 11 years ago
This is definitely something I'll consider implementing.
It seems a bit out of scope... his links basically give you a plugin to add updating capabilities. With this feature, it would take the boiler plate way out of boiler plate.
This is one of those things that I've wrestled with for quite some time.
The point of the Boilerplates is really to provide a foundational approach that anyone can use to begin building plugins and widgets using best practices.
Because WordPress already includes a mechanism for doing just this via the repository, I want to more closely align with that than anything else.
As such, I'm going to close the issue. I definitely appreciate the feedback, but I think I'll be excluding this from the Boilerplates.
Consider taking a look at this when you get a chance:
http://www.wptavern.com/forum/plugins-hacks/1129-using-non-official-plugin-repository.html#post10180
http://w-shadow.com/blog/2010/09/02/automatic-updates-for-any-plugin/
Perhaps you could consider integrating something into your sample here, but reduce the code down as much as possible and make it easy to follow? The other thing that something like this needs to do is use $wpdb to run a schema.php file to load CREATE TABLE IF NOT EXISTS stuff if the plugin uses special tables, and then to call the plugin's custom getOptions() and updateOptions() static class methods after that so that it uses the latest downloaded plugin codebase to apply the options changes.