I'll bite. Tried this afternoon with the latest version. Get: Downloading update from http://downloads.wordpress.org/plugin/all-in-one-seo-pack.zip
Unpacking the update Removing the old version of the plugin Could not remove the old plugin Always fails on removing old plugin. This happened with the half-dozen plugins I tried. Note that I am on Dreamhost, which occasionally does unexpected things. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Sunday, March 09, 2008 8:39 PM To: [email protected] Subject: wp-testers Digest, Vol 37, Issue 19 Send wp-testers mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://lists.automattic.com/mailman/listinfo/wp-testers or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of wp-testers digest..." Today's Topics: 1. Dashboard on some browsers looking auwful (Francesc Hervada-Sala) 2. Testers wanted: Plugin update testing (DD32) 3. Re: Testers wanted: Plugin update testing (Kirk M) 4. Re: Testers wanted: Plugin update testing (DD32) 5. Re: Testers wanted: Plugin update testing (DD32) 6. testing wp e-commerce on 2.5 (Dan Milward) 7. 2.5 and MU (Dan Milward) 8. RTL styles for 2.5 admin broken (Ran Yaniv Hartstein) ---------------------------------------------------------------------- Message: 1 Date: Sun, 9 Mar 2008 19:23:46 +0100 From: Francesc Hervada-Sala <[EMAIL PROTECTED]> Subject: [wp-testers] Dashboard on some browsers looking auwful To: Wordpress Testers <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Hello, on my dashboard I cannot see the author names in the gray boxes with the secondary rss feed. This happens since a few weeks, now with trunk r7188 too, on Linux, KDE 4.01, FireFox 2.0.0.12. Furthermore I tested it with Microsoft IE 7 on Windows Vista and not only the gray boxes are too small, but also the 4 big main boxes appear at a single column, not in 2 columns. I think this is awful. Maybe that happens to other users, too? I submitted a ticket with some screenshots: http://trac.wordpress.org/ticket/6061 Best regards, -- Francesc Username: hervada ------------------------------ Message: 2 Date: Mon, 10 Mar 2008 10:58:33 +1100 From: DD32 <[EMAIL PROTECTED]> Subject: [wp-testers] Testers wanted: Plugin update testing To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=iso-8859-15 Hi all Testers, Wordpress 2.5 is due to be released sometime soon(When ever its ready i believe - But thats another threads discussion). But so far theres been very little bug reports flowing in for the plugin updater, So, I ask of you, The Testers, To grab the latest SVN copy of WordPress, install an old plugin (One thats available on WordPress.org) and hit the "updgrade automatically" link on the plugins page. An alternative to downloading a older version of the plugin, is to simply change the version header of a existing plugin, For testing, i've mainly been using akismet: (after changing) <?php /* Plugin Name: Akismet Version: 2.1.0 Author: Matt Mullenweg Author URI: http://photomatt.net/ */ Do the upgrade proceedure and it should click click over pretty smoothly to update it If anyone has a problem while attempting an upgrade, Please post back with the messages shown on the upgrade page. (I'll then follow up with a plugin i have which should help pin-point the problem) Note: How the upgrade proceedure works: + WordPress notices theres a new plugin version available, displays links on plugin page + User clicks upgrade link + WordPress asks for FTP details to connect to the local account to perform the upgrade (Note: At present, FTP is FORCED to be used for beta testing) + WordPress connects via ftp + WordPress attempts to locate the WordPress folder + WordPress downloads the latest .zip + WordPRess extracts the files from the .zip to a temporary directory + WordPress deletes the old plugin files + WordPress copies the new files into their place + WordPress deletes its temporary files, And upgrade complete It could fail at any one of those steps, And given the number of failure points, I'm supprised theres only been 2 reports of it not working correctly (Both since fixed up) I also stress, WordPress trunk is still pre-beta stage, It is not designed to work in production environments right now, While i use it on a live site without any problems, I cant guarantee you wont have trouble, Try running it on a test install first, then it everythings running allright, only then decide to try it on your live setup :) Cheers, DD32 ------------------------------ Message: 3 Date: Sun, 9 Mar 2008 21:20:48 -0400 From: "Kirk M" <[EMAIL PROTECTED]> Subject: Re: [wp-testers] Testers wanted: Plugin update testing To: <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; format=flowed; charset="iso-8859-15"; reply-type=original I've been using the latest nightly builds (not currently set up for SVN), currently running 03/09/08. On both my test site and my main which is using the latest 2.5, the upgrade fails with the following: >Downloading update from http://downloads.wordpress.org/plugin/akismet.zip >Unpacking the update >Incompatible archive This has been going on over the last several nightly builds no matter which plugin upgrade I tested. I actually haven't had a successful upgrade yet. Just as a note, the OneClick plugin works with no problem in WP 2.5 if that helps any. -------------------------------------------------- From: "DD32" <[EMAIL PROTECTED]> Sent: Sunday, March 09, 2008 7:58 PM To: <[email protected]> Subject: [wp-testers] Testers wanted: Plugin update testing > Hi all Testers, > Wordpress 2.5 is due to be released sometime soon(When ever its ready i > believe - But thats another threads discussion). > > But so far theres been very little bug reports flowing in for the plugin > updater, So, I ask of you, The Testers, To grab the latest SVN copy of > WordPress, install an old plugin (One thats available on WordPress.org) > and hit the "updgrade automatically" link on the plugins page. > > > An alternative to downloading a older version of the plugin, is to simply > change the version header of a existing plugin, For testing, i've mainly > been using akismet: > (after changing) > <?php > /* > Plugin Name: Akismet > Version: 2.1.0 > Author: Matt Mullenweg > Author URI: http://photomatt.net/ > */ > > Do the upgrade proceedure and it should click click over pretty smoothly > to update it > If anyone has a problem while attempting an upgrade, Please post back with > the messages shown on the upgrade page. (I'll then follow up with a plugin > i have which should help pin-point the problem) > > > Note: > How the upgrade proceedure works: > + WordPress notices theres a new plugin version available, displays links > on plugin page > + User clicks upgrade link > + WordPress asks for FTP details to connect to the local account to > perform the upgrade (Note: At present, FTP is FORCED to be used for beta > testing) > + WordPress connects via ftp > + WordPress attempts to locate the WordPress folder > + WordPress downloads the latest .zip > + WordPRess extracts the files from the .zip to a temporary directory > + WordPress deletes the old plugin files > + WordPress copies the new files into their place > + WordPress deletes its temporary files, And upgrade complete > > It could fail at any one of those steps, And given the number of failure > points, I'm supprised theres only been 2 reports of it not working > correctly (Both since fixed up) > > I also stress, WordPress trunk is still pre-beta stage, It is not designed > to work in production environments right now, While i use it on a live > site without any problems, I cant guarantee you wont have trouble, Try > running it on a test install first, then it everythings running allright, > only then decide to try it on your live setup :) > > Cheers, > DD32 > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers ------------------------------ Message: 4 Date: Mon, 10 Mar 2008 12:41:39 +1100 From: DD32 <[EMAIL PROTECTED]> Subject: Re: [wp-testers] Testers wanted: Plugin update testing To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=iso-8859-15 On Mon, 10 Mar 2008 12:20:48 +1100, Kirk M <[EMAIL PROTECTED]> wrote: > I've been using the latest nightly builds (not currently set up for SVN), > currently running 03/09/08. On both my test site and my main which is using > the latest 2.5, the upgrade fails with the following: > >>Downloading update from http://downloads.wordpress.org/plugin/akismet.zip > >>Unpacking the update > >>Incompatible archive > > This has been going on over the last several nightly builds no matter which > plugin upgrade I tested. I actually haven't had a successful upgrade yet. > Just as a note, the OneClick plugin works with no problem in WP 2.5 if that > helps any. I've got a similar error on my main webhost, I think its a incompatibility between the PHP version, the OS, and the Zip decompressor in use. In wp-admin/update.php replace the function show_message() with this one: function show_message($message) { if( is_wp_error($message) ){ if( $message->get_error_data() ) $message = $message->get_error_message() . ': ' . $message->get_error_data(); else $message = $message->get_error_message(); } echo "<p>$message</p>"; } And see what the result is, It'll probably be something like: "Incompatible archive: Unable to find End of Central Dir Record signature" I'll look into what the OneClick plugin is using, I thought it was using the same zip handling class that is currently being used in WordPress, But i may be wrong. > -------------------------------------------------- > From: "DD32" <[EMAIL PROTECTED]> > Sent: Sunday, March 09, 2008 7:58 PM > To: <[email protected]> > Subject: [wp-testers] Testers wanted: Plugin update testing > >> Hi all Testers, >> Wordpress 2.5 is due to be released sometime soon(When ever its ready i >> believe - But thats another threads discussion). >> >> But so far theres been very little bug reports flowing in for the plugin >> updater, So, I ask of you, The Testers, To grab the latest SVN copy of >> WordPress, install an old plugin (One thats available on WordPress.org) >> and hit the "updgrade automatically" link on the plugins page. >> >> >> An alternative to downloading a older version of the plugin, is to simply >> change the version header of a existing plugin, For testing, i've mainly >> been using akismet: >> (after changing) >> <?php >> /* >> Plugin Name: Akismet >> Version: 2.1.0 >> Author: Matt Mullenweg >> Author URI: http://photomatt.net/ >> */ >> >> Do the upgrade proceedure and it should click click over pretty smoothly >> to update it >> If anyone has a problem while attempting an upgrade, Please post back with >> the messages shown on the upgrade page. (I'll then follow up with a plugin >> i have which should help pin-point the problem) >> >> >> Note: >> How the upgrade proceedure works: >> + WordPress notices theres a new plugin version available, displays links >> on plugin page >> + User clicks upgrade link >> + WordPress asks for FTP details to connect to the local account to >> perform the upgrade (Note: At present, FTP is FORCED to be used for beta >> testing) >> + WordPress connects via ftp >> + WordPress attempts to locate the WordPress folder >> + WordPress downloads the latest .zip >> + WordPRess extracts the files from the .zip to a temporary directory >> + WordPress deletes the old plugin files >> + WordPress copies the new files into their place >> + WordPress deletes its temporary files, And upgrade complete >> >> It could fail at any one of those steps, And given the number of failure >> points, I'm supprised theres only been 2 reports of it not working >> correctly (Both since fixed up) >> >> I also stress, WordPress trunk is still pre-beta stage, It is not designed >> to work in production environments right now, While i use it on a live >> site without any problems, I cant guarantee you wont have trouble, Try >> running it on a test install first, then it everythings running allright, >> only then decide to try it on your live setup :) >> >> Cheers, >> DD32 >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-testers > > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > ------------------------------ Message: 5 Date: Mon, 10 Mar 2008 12:50:43 +1100 From: DD32 <[EMAIL PROTECTED]> Subject: Re: [wp-testers] Testers wanted: Plugin update testing To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=iso-8859-15 On Mon, 10 Mar 2008 12:41:39 +1100, DD32 <[EMAIL PROTECTED]> wrote: > I'll look into what the OneClick plugin is using, I thought it was using the same zip handling class that is currently being used in WordPress, But i may be wrong. the OneClick plugin reverts to using exec('unzip ...') in any cases where the PclZip library(same as WP is using) fails. I dont like the idea of having that in the main WordPress code though. ------------------------------ Message: 6 Date: Mon, 10 Mar 2008 14:52:40 +1300 From: Dan Milward <[EMAIL PROTECTED]> Subject: [wp-testers] testing wp e-commerce on 2.5 To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-15; format=flowed We will begin testing WP e-Commerce properly tomorrow - we have already had it running on a few of the recent nightly builds but we have not spent a "huge" amount of time on it... Incidentally... has anybody else tested this already without telling me about it :P Ciao, Dan DD32 wrote: > Hi all Testers, > Wordpress 2.5 is due to be released sometime soon(When ever its ready i believe - But thats another threads discussion). > > But so far theres been very little bug reports flowing in for the plugin updater, So, I ask of you, The Testers, To grab the latest SVN copy of WordPress, install an old plugin (One thats available on WordPress.org) and hit the "updgrade automatically" link on the plugins page. > > > An alternative to downloading a older version of the plugin, is to simply change the version header of a existing plugin, For testing, i've mainly been using akismet: > (after changing) > <?php > /* > Plugin Name: Akismet > Version: 2.1.0 > Author: Matt Mullenweg > Author URI: http://photomatt.net/ > */ > > Do the upgrade proceedure and it should click click over pretty smoothly to update it > If anyone has a problem while attempting an upgrade, Please post back with the messages shown on the upgrade page. (I'll then follow up with a plugin i have which should help pin-point the problem) > > > Note: > How the upgrade proceedure works: > + WordPress notices theres a new plugin version available, displays links on plugin page > + User clicks upgrade link > + WordPress asks for FTP details to connect to the local account to perform the upgrade (Note: At present, FTP is FORCED to be used for beta testing) > + WordPress connects via ftp > + WordPress attempts to locate the WordPress folder > + WordPress downloads the latest .zip > + WordPRess extracts the files from the .zip to a temporary directory > + WordPress deletes the old plugin files > + WordPress copies the new files into their place > + WordPress deletes its temporary files, And upgrade complete > > It could fail at any one of those steps, And given the number of failure points, I'm supprised theres only been 2 reports of it not working correctly (Both since fixed up) > > I also stress, WordPress trunk is still pre-beta stage, It is not designed to work in production environments right now, While i use it on a live site without any problems, I cant guarantee you wont have trouble, Try running it on a test install first, then it everythings running allright, only then decide to try it on your live setup :) > > Cheers, > DD32 > _______________________________________________ > wp-testers mailing list > [email protected] > http://lists.automattic.com/mailman/listinfo/wp-testers > > ------------------------------ Message: 7 Date: Mon, 10 Mar 2008 14:56:42 +1300 From: Dan Milward <[EMAIL PROTECTED]> Subject: [wp-testers] 2.5 and MU To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Normally WordPress MU catches up a few weeks after WordPress right? Will this still be the same case for 2.5 given the size and complexity of this update. Or do we think it will be a bit longer? I'm not in a great rush to know... but this coupled with BuddyPress is going to really rock!!! Its very exciting times!!! Ciao, Dan ------------------------------ Message: 8 Date: Mon, 10 Mar 2008 05:39:03 +0200 From: "Ran Yaniv Hartstein" <[EMAIL PROTECTED]> Subject: [wp-testers] RTL styles for 2.5 admin broken To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=UTF-8 I tried the RTL stylesheets for the 2.5 admin, both with the default locale (just by adding $text_direction = 'rtl'; to wp-confing.php) as well as with the Hebrew locale which is also fully localized to Hebrew, and RTL language. In both cases, the RTL styles are completely broken - not just a few local bugs, they just don't work at all. I don't think it's a local problem with my setup because I tried it on several different computers. Is this just something that wasn't finished yet or is this the way it is supposed to ship? Screenshots: http://files.ranh.co.il/wp-25-rtl-1.png http://files.ranh.co.il/wp-25-rtl-2.png -- -- RYHb!, ranh.co.il ------------------------------ _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers End of wp-testers Digest, Vol 37, Issue 19 ****************************************** _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
