Given the amount of different setups and FTP servers, I would say that if it works for the user, then that person will greatly appreciate the feature. If it does not work for the user, then I suggest that it be disabled for that user.
It might increase the support, but really, if we don't have this then we can't get ready for an automatic update of the WordPress system. If this is the case, then the feature should note which systems it can work on and offer the automatic upgrade and not even display for those that it is known to not work on. There might be questions as to what people are talking about, but not everyone can use pretty permalinks, so it should be assumed that even less can use the feature. Likewise, if the issue is FTP only, then the direct method should work fine for those that it can support. Maintaining that the library used, could probably be looked at to whether a better one exists or if the current one just needs to be extended, fixed, and supported. While I don't like the thought of having even more support issues, I think the ends will eventually outweigh the initial suffering with increased support and tickets related to the issue. DD32 has been doing an extremely good job at providing support. If it was stripped out now, then it won't most likely be used by as many people. The goal is to support everyone, but realistically, it should be assumed that if 40% or even 20% of the user base can successfully use the feature then it should be determined an initial success. I think that once the direct method is enabled (hey, shouldn't that also need testing?), that even more will be supported. My arguments are quite frankly debatable with no substance and no facts. I just want to say that I very much would not like to have the current feature a plugin and function as it does now, but only having to enable it to get the feature. >> 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 > -- Jacob Santos http://www.santosj.name - Personal Blog http://funcdoc.wordpress.com - WordPress Function Documentation Blog _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
