This is why I'm also strongly in favour of putting the
upgrade stuff
into a plugin. It really doesn't have to be in the core
from a technical
point of view. And it's much too unstable due to the lot
of different
FTP servers and PHP setups out there. I know that it's
quite late in the
development of 2.5 for such a major design revision, but
that FTP stuff
can really break things. In my opinion, the right thing to
do would be:
Externalize it into a plugin, and add API hooks for it in
wp-admin/plugins.php. If you need help, I'm at your
service (although I
don't think there's much I can do).
Cheers,
Alex
--
Alex Günsche, Zirona OpenSource-Consulting
Blogs: http://www.zirona.com/ |
http://www.regularimpressions.net
*** Want to test the shiny new release of InstantUpgrade?
***
http://www.zirona.com/blog/software/instantupgrade-10-beta/
I'm rather new to wp-testers but a long time follower of the
threads and a longtime user of WordPress (old tech head as
well) and after working with the new plugin auto upgrading
feature I have to agree, with Alex, it might be better to
leave this up to plugins especially since there's already 3
out there (that I know of); Alex's "InstantUpgrade" and
Keith Dsouza's "WordPress Automatic Upgrades Plugin" for
WordPress upgrading and Anirudh Sanjeev's "OneClick" for
upgrading plugins (I've used the latter 2 very successfully
once they got past the initial releases).
Alex is right, for all the myriad setups that WordPress
could possibly be installed in, trying to incorporate auto
upgrading as a core WordPress feature seems to be way more
trouble than it's worth. I'm not being pert when I say you
folks have enough to deal with as it is without having to
untangle *this* can of worms. Let the plugins authors handle
this one for you and keep that part of the core clean.
Just my humble opinion. ;)
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
