Easy Updating of WordPress
Also, when updating from within WP itself, it could just grab the modified files instead of the entire package. That would save bandwidth, time, and it's generally The Right Thing To Do. Lots of updates will NOT have a gazillion of modified files, so in some cases this could make updating a matter of mere seconds.
Oh, and @Godrox: what changes do you have to make that FORCE you to muck about in the core files? Can't it be done through themes or plugins?
The Firefox updating scheme is perfect. The beauty of WordPress for many of my clients is they don't have to know FTP to manage their site.
The plug-ins should also have an update scheme like Firefox.
Sounds good, but:
1) don't ask for ftp logins the way SimpleMachines Forum does when you try to use their updater.
2) provide an option for the original installer to disable it, because it could be fairly unpopular with hosting sites that would want to control the upgrade process.
Similarly, my webhost (globat.com) has a "1-click install" that already does this. A single click, and the entire WP installation is complete in about 60 seconds.
They do not, however, keep WP updated with the latest versions. Adding this feature to the admin console sounds great.
The problem of installing and upgrading web applications has been on my mind for over two years now. It was the topic of my senior report for my BCS degree. It's not a simple problem, but it can be simplified by embracing tradeoffs.
I've recently outlined the challenges for WordPress and posted my suggestions in my blog post Automatic Updates for WordPress.
Here's an exerpt:
Give the web application access to update itself
I believe that it’s an acceptable security trade-off to give the web application access to it’s files and gain the ability to push critical updates as soon as they are ready. Although it’s traditionally a faux pas, I strongly believe we have a better chance maintaining security with this approach.
For anyone that modify WordPress in such a way that an update would mess it up, this just mean WordPress has not totally separated presentation of content from the core files. Are there more to be done here?
Apart from this - I wholehartedly support this and actually wrote something about this in another idea.
I believe that increment updates would go a long way, but a one-click solution is the ultimate goal!
Releasing 2.0.7 10 days after 2.0.6 when only a few pages with relatively minor changes need to be added is a PERFECT reason why this should be as brain-dead simple as a single button click.
Anything more than that is the exact reason why I skip several upgrades, even in the face of danger.
A function to check current version and offer update would make wordpress blogs around the world a whole lot more secure.
This has gotta help both the people maintaining a-lot of WP websites and normal 'users' who simply just dont understand.
Lengthy upgrade? I just wait for Mark to put out his Changed Files ZIP and upgrade from those. Much faster.
RSS feed for this topic
You must log in to post.