Comments on: WordPress 1.5 Ellington http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/ Protect yourself from government gaffes, bureaucratic blunders and incumbent incompetence Mon, 06 Feb 2012 16:25:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Gary http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-316 Gary Thu, 10 Mar 2005 14:08:17 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-316 Yea, that can be problematic later. Unfortunately, it looks like I'm going to give up on WP as the engine for my quasi-CMS sites...it's just way too buggy. I get nervous having to hack here, tweak there, to get some things working while major things such as comment moderation, pinging, and category-based permalinks don't work properly. I'll continue (maybe) using it on my own sites where I mind less having to do so much work to make it functional, but I'm not about to put it out there under clients and then face dealing with upgrading a highly hacked product when the time comes. I whined loudly about MT's fee structure, but I've spend 20 times the value in time fixing WP in ways I never had to with MT. /rantoff Yea, that can be problematic later. Unfortunately, it looks like I’m going to give up on WP as the engine for my quasi-CMS sites…it’s just way too buggy. I get nervous having to hack here, tweak there, to get some things working while major things such as comment moderation, pinging, and category-based permalinks don’t work properly. I’ll continue (maybe) using it on my own sites where I mind less having to do so much work to make it functional, but I’m not about to put it out there under clients and then face dealing with upgrading a highly hacked product when the time comes. I whined loudly about MT’s fee structure, but I’ve spend 20 times the value in time fixing WP in ways I never had to with MT. /rantoff

]]> By: Michael Hampton http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-315 Michael Hampton Sat, 05 Mar 2005 21:51:12 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-315 It wasn't my intention to fork WordPress at all, just to provide an interim solution for a couple of the more serious bugs I got bitten by (as did a lot of other people as well). I fully intend to install 1.5.1 when it's available, assuming it actually works and they don't check in any showstopper bugs at the last minute. :) It wasn’t my intention to fork WordPress at all, just to provide an interim solution for a couple of the more serious bugs I got bitten by (as did a lot of other people as well). I fully intend to install 1.5.1 when it’s available, assuming it actually works and they don’t check in any showstopper bugs at the last minute. :)

]]> By: Gary http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-314 Gary Fri, 04 Mar 2005 16:28:33 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-314 Very cool...I'm thinking about doing a stripped psuedo-CMS version (pull everything related to comments, tbacks, members, unnecessary archives, etc.), since I've got some sites ahead that I want to use WP for and they will be normal sites. But if you're bored and want to take a crack at it...... Very cool…I’m thinking about doing a stripped psuedo-CMS version (pull everything related to comments, tbacks, members, unnecessary archives, etc.), since I’ve got some sites ahead that I want to use WP for and they will be normal sites. But if you’re bored and want to take a crack at it……

]]> By: Michael Hampton http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-311 Michael Hampton Mon, 28 Feb 2005 23:02:16 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-311 Gary, the copy of strayhorn currently being distributed from wordpress.org (as of this very minute) matches exactly the reference copy I downloaded on 17 Feb and used when creating this package. In other words, no, these are not fixed in strayhorn. If they were, I wouldn't have needed to do anything, now would I? :) The text seems to imply that strayhorn was released on 15 Feb, which is <a href="http://wordpress.org/news/2005/02/strayhorn/" rel="nofollow">incorrect</a>. Ellington was created using code from 2005-02-14, the last nightly in which pages and categories worked properly, and strayhorn, rather than 2005-02-15. See, I am capable of making mistakes! Thanks for pointing this out. Gary, the copy of strayhorn currently being distributed from wordpress.org (as of this very minute) matches exactly the reference copy I downloaded on 17 Feb and used when creating this package. In other words, no, these are not fixed in strayhorn. If they were, I wouldn’t have needed to do anything, now would I? :)

The text seems to imply that strayhorn was released on 15 Feb, which is incorrect. Ellington was created using code from 2005-02-14, the last nightly in which pages and categories worked properly, and strayhorn, rather than 2005-02-15.

See, I am capable of making mistakes! Thanks for pointing this out.

]]> By: Planeta WordPress » Blog Archive » Solución a los problemas con las páginas y categorías en Wordpress 1.5 http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-310 Planeta WordPress » Blog Archive » Solución a los problemas con las páginas y categorías en Wordpress 1.5 Mon, 28 Feb 2005 16:56:22 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-310 [...] na versión no oficial parcheada de Wordpress 1.5 ‘Strayhorn’, de nombre clave ‘Ellington’ que podeis descargar desde su página web. Antes de utilizar es [...] [...] na versión no oficial parcheada de WordPress 1.5 ‘Strayhorn’, de nombre clave ‘Ellington’ que podeis descargar desde su página web. Antes de utilizar es [...]

]]> By: Gary http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-309 Gary Mon, 28 Feb 2005 13:45:05 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-309 This is great, but a question: since the official release ended up as the 2-17 release, do you know if this was fixed anyway in the now "official" strayhorn release of 2-17? This is great, but a question: since the official release ended up as the 2-17 release, do you know if this was fixed anyway in the now “official” strayhorn release of 2-17?

]]> By: SteamedPenguin: Not Your Usual Meal » Blog Archive » A WordPress Patch http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-307 SteamedPenguin: Not Your Usual Meal » Blog Archive » A WordPress Patch Mon, 28 Feb 2005 02:17:53 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-307 [...] tive Commons Licensed A WordPress Patch IO ERROR has a WordPress patch that might be useful to some people. This entry was pos [...] [...] tive Commons Licensed A WordPress Patch IO ERROR has a WordPress patch that might be useful to some people. This entry was pos [...]

]]> By: Michael Hampton http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-306 Michael Hampton Sun, 27 Feb 2005 22:46:03 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-306 The page cache and category cache are a great idea, and my release simply backs out the changes. Long-term, they should remain, but be fixed. There is also a user cache in the new code, but as far as I can see, it works properly. I've already posted my bug report to mosquito, where as of today it remains in "new" status. But some people (like myself) need a fix NOW. The page cache and category cache are a great idea, and my release simply backs out the changes. Long-term, they should remain, but be fixed. There is also a user cache in the new code, but as far as I can see, it works properly. I’ve already posted my bug report to mosquito, where as of today it remains in “new” status. But some people (like myself) need a fix NOW.

]]> By: craig http://www.homelandstupidity.us/2005/02/27/wordpress-1-5-ellington/#comment-305 craig Sun, 27 Feb 2005 21:39:13 +0000 http://www.ioerror.us/2005/02/27/wordpress-15-ellington/#comment-305 Have you submitted your changes to the WordPress developers? If you are not aware, there is a hackers' mailing list you can subscribe to at: http://lists.automattic.com/mailman/listinfo/wp-hackers. Kudos to you for doing something constructive and not simply complain! That's great to see! Have you submitted your changes to the WordPress developers? If you are not aware, there is a hackers’ mailing list you can subscribe to at: http://lists.automattic.com/mailman/listinfo/wp-hackers.

Kudos to you for doing something constructive and not simply complain! That’s great to see!

]]>