"Disable wptexturize" is the second plugin I've created for WordPress. To be honest, as far as plugins go, they don't get much simpler than this one. Aside from the header info, it consists of a grand total of three lines of code. Those three lines, though, make a world of difference to someone trying to run a site where formatting is important.
The purpose of this plugin is to stop the wptexturize filter from running on your content, the excerpt for your content (if you use it), and the comments left by your visitors. The texturizer mangles your code by converting what you actually type to what it thinks you mean. For example, the difference between "--" and "–" or straight quotes (what normal people use) and smart quotes (what Microsoft Word uses) is night and day when you're trying to run a command on a *nix system or compile a bit of code.
Earlier today I rolled out a bunch of updates to the packages in the repo. If you use any of these you'll need to run a "yum update" to pull them in. Complete details on the updates are at the bottom of this post.
The only update I would consider "critical" is MySQL. Bug #31001 was found after the release of the sources and is probably a deal-breaker for anyone using InnoDB tables as "ORDER BY DESC" no longer works. This respin includes a patch to fix that glitch.
Yeah, I know last month I said that I probably wouldn't be doing any more releases of MySQL from the Enterprise-only sources but I guess I lied. As soon as I saw that 5.0.48 was out I checked it out from BitKeeper and started working to turn that into a package that I could use to build my RPMs. Not wanting to unleash an untested copy of MySQL on the masses, and not knowing how my readers would react to my releasing packages made from an unofficial source tarball, I decided to keep that one private for a while and test it on my own systems.
Well, just about when it got to the point when I was going to release it to the wild, some kind soul went and released the official tarball for 5.0.48 Enterprise. The 5.0.48 binaries currently in my repo are made from the official sources, not my original BitKeeper sources. That said, given how well they worked out for me I am still not opposed to, in the future, releasing Enterprise versions of MySQL that are made from the BitKeeper sources and then later doing a respin if the official source tarball leaks out. If you have a concern about that, let me know.
Whew! Given that it's been 8 months since the release of Apache's httpd 2.2.4 I was starting to wonder whether or not the httpd developers were on an extended vacation. That said, they've just released version 2.2.6 of their wonderful web server. That vacation theory must have been wrong, given that they skipped version 2.2.5 (something that is rarely done) and went straight to 2.2.6. This release is a big one, fixing five potential security issues and numerous bugs to provide a more stable platform.
Well, it's been 3 months since the last release of PHP 5.2 but 5.2.4 is finally here. Unlike the earlier releases of PHP 5.2 which have included both performance/memory optimizations as well as fixes for critical bugs (security issues and otherwise), this release is aimed at improving the overall stability of the 5.2 release chain (no doubt aiming to improve the image of PHP 5.2 with 4.4 being discontinued at the end of the year) by fixing more than 120 small bugs, as well as taking the opportunity to fix a few low-level security holes.
The PHP development team didn't slap a "0mg!!! j00 m|_|$7 |_|pd473 j00r php 0r 3l$3 j00 \/\/1ll b3 h4ck3d!!!" tag on this one but stability is always a good thing so I would recommend that all of my readers upgrade when they get a chance. Really though, since I do all the work, do you really have an excuse NOT to update?