Archive Info

You are currently browsing the I Hate weblog archives for 'tools' category

WordPress Firewall Script

Jaimie Sirovich just sent me a Facebook chat about his new WordPress Firewall script.  I just installed it, and will post my thoughts about it when I’ve had a chance to evaluate how it does.

After installing, go to the WordPress Admin panel, click on “Settings”, and then “Firewall” to manage the script.

SEO Position Tracker

I saw a nice SEO position tracker today.  You should check out and check your site’s rankings. You can check them against a competitors site and sign up for weekly email reports.  The service is (currently) free. updated

# Inktomi/Yahoo!


Firefox is Garbage?

I never thought I would read anything that claimed Firefox is garbage.  NinjaPirate gives us a list of 6 reasons why we should uninstall it.

The first is his screenshot of Firefox using over 200 Megs of RAM.  That’s a lot.  Of course, currently mine is using less, about 92 Megs of RAM, which is still a lot, but less than NinjaPirate.

One reason he gives is that whenever he looks at (some particularly disgusting kind of) porn online in Firefox he feels guilty.  Is feeling guilty for looking at porn Firefox’s fault?  If you feel guilty doing it, that’s because you think it’s wrong and do it anyway.  That’s your own fault.

He’s right about the name though.  Firefox is a really, really dumb name.  I feel stupid every time I say I use Firefox.  Can’t we come up for a better name for it, like Opera or Lynx?  Oh wait…

How to Keep WordPress from Overwriting Your .htaccess Edits

Recently I was having problems with WordPress overwriting my .htaccess.  I wanted to do some URL rewriting, but WordPress kept erasing my changes.  I realized that WordPress reserves a portion of the .htaccess file for itself, and it is clearly marked as such.  As long as you don’t put your edits in that spot, they won’t be overwritten.

If only I’d read this article first, I wouldn’t have been scratching my head over this issue :) Updated


When Does WordPress Overwrite .htaccess?

I’ve noticed that my modified .htaccess file has been overwritten by WordPress at least twice.  This has broken the archival routine of the bBlog version of

I did install a couple of plugins to WordPress.  I wonder if when they were installed, the .htaccess was overwritten?

Clamping Down on

I’m seeing a very serious bandwidth crunch on Today (so far) I’ve used over 30 gigs. So, in order to clamp down a bit, I’m restricting access to the site to those requests which contain a User-Agent header. It seems that the majority of requests for the lists come from bots with no User-Agent header. I don’t mind if people access the lists, but at least be polite about it. Tell me who you are, for Pete’s sake!

KloakIt users should not suffer any adverse effects, but just in case–especially if you are using a very old version (post v3.5)–I recommend you update to the latest version.

Backwards Compatibility Issues

So, when I decided to convert to WordPress from bBlog, I had to decide what to do with all of my old bBlog entries. I came across various home-grown conversion tools that claimed to convert various versions of bBlog installations to various versions of WordPress installations, but I was really leery about using any of them. For one thing, one of the sites I visited generated one of those nice Google warnings about the site being untrustworthy.

I suppose I could have written some code myself to perform the conversion. It probably wouldn’t have been all that difficult. I’m familiar with MySQL databases and have done some hacking both in WordPress and bBlog.

In the end, though, I decided to maintain the look and feel of my old bBlog entries. Why not just keep the bBlog blog and install WordPress on top of it? Installation was no problem…the only file WordPress need to overwrite was index.php. I just renamed bBlog’s to index_bblog.php. Then, with just a little bit of mod_rewrite trickery, I have both blogs available on the same URL!

Here’s my mod_rewrite code, in case somebody wants to do something similar:

RewriteEngine On
RewriteBase /

RewriteCond %{QUERY_STRING} postid=(.*)$ [NC]
RewriteCond %{REQUEST_FILENAME} !(index_bblog\.php.*)$ [NC]
RewriteRule .* /index_bblog.php?postid=%1 [R=301,L]

RewriteCond %{QUERY_STRING} sectionid=(.*)$ [NC]
RewriteCond %{REQUEST_FILENAME} !(index_bblog\.php.*)$ [NC]
RewriteRule .* /index_bblog.php?sectionid=%1 [R=301,L]

This makes it so anytime bBlog-style entries are requested, because for instance they are still indexed, or linked to from within the entries themselves, the server recognizes them and redirects them to the index_bblog.php file, using the QUERY_STRING info to specify which blog entry is requested. Very handy!

KloakIt Update

Today I released an update to KloakIt which fixes a bug which caused the login screen to hang under certain circumstances.  If you are running KloakIt 3.5, I recommend you update your control panel to include this patch.  Updating is simple.  Just log in, and click the Update button.