Comments for Geof's Relentless Kvetching About WordPress http://gfmorris.wordpress.com Just another WordPress.com weblog Sat, 26 Jul 2008 04:31:27 +0000 http://wordpress.org/?v=MU Comment on On WP 2.2.3 and WP 2.3 by Geof F. Morris http://gfmorris.wordpress.com/2007/09/11/on-wp-223-and-wp-23/#comment-8332 Geof F. Morris Sat, 06 Oct 2007 17:56:26 +0000 http://gfmorris.wordpress.com/2007/09/11/on-wp-223-and-wp-23/#comment-8332 Odd ... my memory limit is there, too, and I've had nary an error. Odd … my memory limit is there, too, and I’ve had nary an error.

]]> Comment on On WP 2.2.3 and WP 2.3 by Jason http://gfmorris.wordpress.com/2007/09/11/on-wp-223-and-wp-23/#comment-8308 Jason Sat, 06 Oct 2007 00:01:36 +0000 http://gfmorris.wordpress.com/2007/09/11/on-wp-223-and-wp-23/#comment-8308 Not that my brief brush with wordpress 2.3.0 is proving to be very worthwhile... running upgrade.php blows up, running into the 8mb php memory limit. (even without any plugins activated) --Jason Not that my brief brush with wordpress 2.3.0 is proving to be very worthwhile… running upgrade.php blows up, running into the 8mb php memory limit. (even without any plugins activated)

–Jason

]]> Comment on An Agreeable Openness by On WP 2.2.3 and WP 2.3 « Geof’s Relentless Kvetching About WordPress http://gfmorris.wordpress.com/2007/08/24/an-agreeable-openness/#comment-7540 On WP 2.2.3 and WP 2.3 « Geof’s Relentless Kvetching About WordPress Wed, 12 Sep 2007 01:03:50 +0000 http://gfmorris.wordpress.com/2007/08/24/an-agreeable-openness/#comment-7540 [...] « An Agreeable Openness [...] [...] « An Agreeable Openness [...]

]]> Comment on An Appropriate Response by An Agreeable Openness « Geof’s Relentless Kvetching About WordPress http://gfmorris.wordpress.com/2007/08/04/an-appropriate-response/#comment-6953 An Agreeable Openness « Geof’s Relentless Kvetching About WordPress Sat, 25 Aug 2007 01:20:52 +0000 http://gfmorris.wordpress.com/2007/08/04/an-appropriate-response/#comment-6953 [...] « An Appropriate Response [...] [...] « An Appropriate Response [...]

]]> Comment on Start the Clock on WP 2.2.2 by An Appropriate Response « Geof’s Relentless Kvetching About WordPress http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-6512 An Appropriate Response « Geof’s Relentless Kvetching About WordPress Sun, 05 Aug 2007 01:37:27 +0000 http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-6512 [...] Appropriate Response August 4th, 2007 Back in July when I last wrote here, Matt asked: What exactly do you want us to [...] [...] Appropriate Response August 4th, 2007 Back in July when I last wrote here, Matt asked: What exactly do you want us to [...]

]]> Comment on Start the Clock on WP 2.2.2 by Otto http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5973 Otto Wed, 11 Jul 2007 14:47:31 +0000 http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5973 This seems like an extremely low-risk problem. All you can do with it is redirect from one site to another. Okay, so that could be the cause of other issues, but it's not like anybody can break into your site with this or anything. This seems like an extremely low-risk problem. All you can do with it is redirect from one site to another. Okay, so that could be the cause of other issues, but it’s not like anybody can break into your site with this or anything.

]]> Comment on Start the Clock on WP 2.2.2 by Matt http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5960 Matt Tue, 10 Jul 2007 21:48:45 +0000 http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5960 What exactly do you want us to say? If it's important, then we're working as fast as we can to get a release out and promote the heck out of it. (Think 2.1.1.) If we consider it low priority, then it waits for the next regular release, but we get raked over folks who think every little problem is the sky falling. What exactly do you want us to say?

If it’s important, then we’re working as fast as we can to get a release out and promote the heck out of it. (Think 2.1.1.) If we consider it low priority, then it waits for the next regular release, but we get raked over folks who think every little problem is the sky falling.

]]> Comment on Start the Clock on WP 2.2.2 by Geof F. Morris http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5953 Geof F. Morris Tue, 10 Jul 2007 12:06:53 +0000 http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5953 Perhaps I am, Matt, but that's because Nature abhors a vacuum, and we're getting nothing from the WP devs---no scope of the bug's reach, no determination of its severity, no timeline for having the fix published. I'd argue that you have a much bigger PR problem than you have a code problem. Perhaps I am, Matt, but that’s because Nature abhors a vacuum, and we’re getting nothing from the WP devs—no scope of the bug’s reach, no determination of its severity, no timeline for having the fix published. I’d argue that you have a much bigger PR problem than you have a code problem.

]]> Comment on Start the Clock on WP 2.2.2 by Matt http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5948 Matt Tue, 10 Jul 2007 05:30:47 +0000 http://gfmorris.wordpress.com/2007/07/09/start-the-clock-on-wp-222/#comment-5948 I think you're getting drawn in by sensationalists. I think you’re getting drawn in by sensationalists.

]]> Comment on WordPress Security Scanning by Geof F. Morris http://gfmorris.wordpress.com/2007/07/03/wordpress-security-scanning/#comment-5943 Geof F. Morris Tue, 10 Jul 2007 00:12:41 +0000 http://gfmorris.wordpress.com/2007/07/03/wordpress-security-scanning/#comment-5943 Philipp: I don't think that they should <em>solve</em> the problems, but simply let the user know that they exist. I'm willing to bet that a lot of users don't ever bother to check on updates to their theme or their plugins---if it's not broken, folks aren't going to care about it. [Heck, I don't think that WordPress makes a big enough deal about upgrades with users, but that's another entry entirely.] It would be great to do this kind of scan. That said, there's nothing to stop a plugin developer from developing a plugin for this very purpose: one that performs a check using BlogSecurity's plugin, inserts the necessary <!-- wpscanner --%gt; while the scanning is done, and then removing the HTML comment after testing is done. Hmmm. Philipp: I don’t think that they should solve the problems, but simply let the user know that they exist. I’m willing to bet that a lot of users don’t ever bother to check on updates to their theme or their plugins—if it’s not broken, folks aren’t going to care about it. [Heck, I don't think that WordPress makes a big enough deal about upgrades with users, but that's another entry entirely.] It would be great to do this kind of scan.

That said, there’s nothing to stop a plugin developer from developing a plugin for this very purpose: one that performs a check using BlogSecurity’s plugin, inserts the necessary <!– wpscanner –%gt; while the scanning is done, and then removing the HTML comment after testing is done. Hmmm.

]]>