Yes, I’m painfully aware that the blog (particularly the comment system) is performing very slowly.
No, I’m not certain what’s causing it, though it seems to be Evil Spammer-related.
Yes, I’m working on it. I’m tracking traffic, tracking files hit, reviewing error logs, renaming scripts, blocking a few IP addies, etc., but there are only vague wisps of gunsmoke in the air (and a few bodies on the ground), no actual smoking gun I can tackle.
No, I can’t do a lot to work on it while at the office, because of firewall issues.
Yes, it is intensely annoying.
No, no schedule on resolution.
57 view(s)
I’ve renamed the mt-tb.cgi script under directory mt4test, as it was getting hammered by spammers, causing the server load to go nuts, etc.
Dude, change over to WordPress.
Aha! And … wow, I had no idea mt4test was still sitting out there; that directory can be gone. (I’ll yank it up tonight.)
I’ll confess that if I had a way to convert to WordPress that would retain all my existing internal links, I’d be sorely tempted. Although, to be fair, it’s actually been like a year since I ran into any serious spammer problems here.
And … thanks, Stacey!
Strangely, I’m still getting a page not found error for
https://www.hill-kleerup.org/blog/2009/02/09/religion_morality_and_civ.html
I’ve flushed my cache and tried with two different browsers. I also tried tunneling to another domain in the hope that it was a cache somewhere upstream from me that I could dodge. No joy!
But even more strangely, to my thinking, I *can* comment on this post.
I guess the universe doesn’t want me to comment on that item.
You mean links in entries to previous entries? Screw it, leave the MT install in place, those links will still work, they’ll just be to the MT version. Any time someone clicks “HOME” they’ll be taken to the new WP version of the site.
So basically implement WP for the “new” blog. Import the MT entries/comments. The main home page becomes the WP page. The existing MT archives are kept in place, the WP version uses a new archive structure, and internal links from within posts that point to the old MT stuff would still be able to point to them (though it would be a “dead end” — maybe do a last template build to to let folks who come there know what’s going on). Turn off the comment/trackback capability within the old MT implementation (to deal with the spammer impact problem).
Tempting … a few issues to resolve:
1. Would need to do this for multiple blogs. Not a huge issue per se.
2. Need to look at how WP handles (if it does) trackbacks, as I use them a fair amount for internal cross-references within posts.
3. I’d need to do some serious looking at how I’d port my WIST system, as I use the data structure there in a very oddball fashion and I’d need to get it to “work” with WP.
4. Learning WP. 🙂
Fewer concerns on this than I immediately thought (#3 is probably the biggest question mark I have).
I’ll add it to my List of Things to Do.
1. Or not. Just get THIS one over to WP. The others aren’t nearly so, er, troublesome.
2. Does them the same way as any other blog platform.
3. Or don’t. Leave it in MT.
4. Ha. MT is ten billion times more complicated, though I am Very Disappointed with WP’s 2.7 backend. Looks like frickin’ MT.
Hrm. Thought it would be the underlying modules that were being attacked, which would be the same across all the MT blogs — but if the attacks are coming through the blog itself (rrg), I can see the advantage of getting this one moved.
Let me see what I can do.