I hadn’t seen the information about v1.0, I think that’s most definitely a step in the right direction to land this program in Core. I really can’t express to you how much I like this plugin, and if you can find a way to do this through FTP that wouldn’t require permissions changes, I really think you’re onto something.

Yes, this is the whole idea. I could use PHP’s FTP functions, but unfortunately they don’t exist on all hosts. I’m using the pemftp library now, which is very cool and does everything with raw FTP commands on the TCP stack, but it seems not to be 100% stable. As soon as I’ll have more time again, I’ll continue working on it.

As for upgrades to InstantUpgrade itself, I think now that the plugins upgrader notification is built in, it’s only a couple steps away from having InstantUpgrade require the latest version of the software be installed before attempting to upgrade WordPress.

Indeed, that is one of the benefits of this new feature. However, I want to stay 2.0.x compatible, so it’s not that easy in the end.

The only other thing I know Matt expressed a little hesitation about was in regards to your treatment of Plugins. The reason I understand for the deactivation of plugins is that plugins are the primary reason a WP installation will break upon upgrade. I’ve had this problem happen to me to the point where a plugin broke my WP so bad I couldn’t even access my plugins panel to deactivate it, and I had to enter through FTP and manually delete plugins until I found the right one.

I know, we’ve been discussing that with fellow WP users and devs, and I now agree that it is a useful feature for many. It’s on my list for the next release.

Anyway, I will continue to be a faithful InstantUpgrade user as long as you support it, and I will seriously consider running a cloned site for the express purpose of testing out the 1.0 version on my provider.

That would be cool indeed, but let’s wait a bit till I release a modified alpha of 1.0. The current one is just too screwed to waste time on it.

I hadn’t seen the information about v1.0, I think that’s most definitely a step in the right direction to land this program in Core. I really can’t express to you how much I like this plugin, and if you can find a way to do this through FTP that wouldn’t require permissions changes, I really think you’re onto something.

As for upgrades to InstantUpgrade itself, I think now that the plugins upgrader notification is built in, it’s only a couple steps away from having InstantUpgrade require the latest version of the software be installed before attempting to upgrade WordPress.

The only other thing I know Matt expressed a little hesitation about was in regards to your treatment of Plugins. The reason I understand for the deactivation of plugins is that plugins are the primary reason a WP installation will break upon upgrade. I’ve had this problem happen to me to the point where a plugin broke my WP so bad I couldn’t even access my plugins panel to deactivate it, and I had to enter through FTP and manually delete plugins until I found the right one.

Anyway, I will continue to be a faithful InstantUpgrade user as long as you support it, and I will seriously consider running a cloned site for the express purpose of testing out the 1.0 version on my provider.

And keep up the great work. I know that this, or something similar, will work eventually, as soon as the kinks are worked out. Thanks for helping to break ground.