Re: [wp-testers] WordPress 3.0.3 and Akismet
Dion - Is this why the graphs/pie are not showing up when viewing Akismet Stats (2.5.0)? I had to fall back to 2.4.0 on 4 different (single user) WordPress 3.0.3 sites due to this problem. All 4 sites use the same basic, regularly updated plugins and all previous versions of Akismet have worked properly. Also, I tested out Akismet 2.5.0 in a test site using the nightly builds of 3.1 (via the Beta Tester plugin) and, with no other plugins activated, 2.5.0 is exhibiting the same problem as seen in WP 3.0.3. No graphs/pie are showing when viewing Akismet Stats. On 12/09/2010 12:48 AM, Dion Hulse (dd32) wrote: This is the expected behaviour at present, and by expected, I mean an unfortunate situation of a combination of Pinning WordPress 3.0.x to the 2.4 Akismet branch, and a bug in the WordPress Upgrader. Since Akismet is bundled with WordPress Core, And the auto-upgrade upgrades the buindled plugins/themes at present, the end result will be that the blog will receive the current version of the plugin in the WordPress package. The WordPress 3.0.x branch is (for the first time ever) linked to a specific revision of akismet, specifically, the 2.4 branch. WordPress 3.1 is directed to the Akismet 2.5 branch. Now, Ideally, the WordPress upgrader shouldn't touch the files in wp-content, unless it's to add a new default theme or similar.. But it also doesnt currently respect custom wp-content directories, which also results in those using non-english locale's and custom wp-content directories, not recieving the updated locale files. Hopefully this is something that will change with WordPress 3.2. On 9 December 2010 16:18, Len Kutchmalkutc...@gmail.com wrote: I updated Akismet (on 3 sites) from 2.4.0 to 2.5.0 the other day via the automatic upgrade feature. Earlier this evening I noted WordPress 3.0.3 was released so I updated all 3 sites from 3.0.2 via the automatic upgrade feature. Later on I noticed the Akismet version was bumped down to 2.4.0 again. I thought I was either losing my mind or something funky is going on. I was able to duplicate this on 5 local installs using Xampp. The steps I took: 1. Upgrade Akismet from 2.4.0 to 2.5.0 via auto upgrade 2. Upgrade WordPress from 3.0.2 to 3.0.3 via auto upgrade Akismet is back to 2.4.0 and needs to be upgraded again. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] WordPress 3.0.3 and Akismet
I updated Akismet (on 3 sites) from 2.4.0 to 2.5.0 the other day via the automatic upgrade feature. Earlier this evening I noted WordPress 3.0.3 was released so I updated all 3 sites from 3.0.2 via the automatic upgrade feature. Later on I noticed the Akismet version was bumped down to 2.4.0 again. I thought I was either losing my mind or something funky is going on. I was able to duplicate this on 5 local installs using Xampp. The steps I took: 1. Upgrade Akismet from 2.4.0 to 2.5.0 via auto upgrade 2. Upgrade WordPress from 3.0.2 to 3.0.3 via auto upgrade Akismet is back to 2.4.0 and needs to be upgraded again. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
Re: [wp-testers] WordPress 3.0.3 and Akismet
This is the expected behaviour at present, and by expected, I mean an unfortunate situation of a combination of Pinning WordPress 3.0.x to the 2.4 Akismet branch, and a bug in the WordPress Upgrader. Since Akismet is bundled with WordPress Core, And the auto-upgrade upgrades the buindled plugins/themes at present, the end result will be that the blog will receive the current version of the plugin in the WordPress package. The WordPress 3.0.x branch is (for the first time ever) linked to a specific revision of akismet, specifically, the 2.4 branch. WordPress 3.1 is directed to the Akismet 2.5 branch. Now, Ideally, the WordPress upgrader shouldn't touch the files in wp-content, unless it's to add a new default theme or similar.. But it also doesnt currently respect custom wp-content directories, which also results in those using non-english locale's and custom wp-content directories, not recieving the updated locale files. Hopefully this is something that will change with WordPress 3.2. On 9 December 2010 16:18, Len Kutchma lkutc...@gmail.com wrote: I updated Akismet (on 3 sites) from 2.4.0 to 2.5.0 the other day via the automatic upgrade feature. Earlier this evening I noted WordPress 3.0.3 was released so I updated all 3 sites from 3.0.2 via the automatic upgrade feature. Later on I noticed the Akismet version was bumped down to 2.4.0 again. I thought I was either losing my mind or something funky is going on. I was able to duplicate this on 5 local installs using Xampp. The steps I took: 1. Upgrade Akismet from 2.4.0 to 2.5.0 via auto upgrade 2. Upgrade WordPress from 3.0.2 to 3.0.3 via auto upgrade Akismet is back to 2.4.0 and needs to be upgraded again. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
[wp-testers] WordPress 3.0.3 and Akismet
Ah I see. Thanks for the clarification. ___ wp-testers mailing list wp-testers@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-testers
