Tim Heuer figured out the right stored procedure to modify in Subtext 2.5.2.0 to disable tracking of referrals altogether. I'm all for this since it means less need to monitor my database and remove/shrink the referral table. I updated my Subtext Database Maintenance page so you can fix your DB up with a single click. Enable/disable, push-button style. All yours, free, YMMV. Do note that it does actually modify the stored proc, so if you've got your DB locked down or you've customized stuff, this may not be something you want to do. You have been warned.

About a year and a half ago I updated my Subtext database maintenance page from the original I had posted about three years ago. While the database hasn't changed much between Subtext 2.1.0.5 and 2.5.2.0 (the 2.1.0.5 maintenance page does still work), I updated the page to provide a little more info and do the cleanup in a more automated fashion. As a refresher, this page lets you... Clear the error log. See how many referrals you have in your database. Remove search engine and spam referrals from the database. ...

As mentioned in an earlier article, I updated to the latest Subtext and was having email problems. I have the problem solved now so I do get notified when comments and contact form submissions come in. For those more technical and interested in what happened... ...it was a lot of things conspiring against me. The Subtext contact form specifically doesn't send you email if you're logged into your own blog. It checks to see if you're logged in and, if so, just skips the whole send procedure but still says "Email sent!" making for...

After some unfortunate problems with the handling of medium trust, Subtext has released a new version to which I've upgraded. Things seem to be working reasonably well with the exception of email. I no longer actually receive emails coming from the Contact form, nor do I get notified when comments are made. I gather I'm not the only person with the problem, either. I'm working on that, but in the meantime... sorry. Catch me on Twitter if you need to get in touch or send me email directly: tillig-at-paraesthesia-dot-com. I do love me some Subtext, but I...

Last year about this time I posted a database maintenance page that I created for cleaning up Subtext database things. Since then I've upgraded to Subtext 2.1.0.5 and, while the old page still works, my blog has become more popular so the referral cleanup is more difficult. There are so many records coming in that even with a long timeout set, there's too much and the delete operation times out. That leaves a huge amount of junk in the transaction log and is just problems. I updated the page so you can select which referrers you want to delete...

The Subtext blog project has moved its home from SourceForge over to Google Code. The code finished migrating over today and the SourceForge project has been marked read-only. I'm excited - the interface is so much lighter weight and easy to get around in. Check it out!

This is my first post on the upgraded blog using Subtext 2.1.0.5. After a failed upgrade, I ran through an upgrade on a full staging environment, got it working, and repeated the process in production... huh, I guess that's sort of what you're supposed to do, anyway, isn't it? I won't lie; my heart was pounding near out of my chest while I was doing the upgrade, scared I'd have to call upon my web host to restore me from a backup (I don't have admin access so I can't do it myself). Right-o. Anyway, it looks like I'm up and running, which...

It's been a long time in the making, but since the last time I tried to upgrade my blog to the latest Subtext failed so miserably, I wanted to build up a full staging environment and test the heck out of it before trying to do it in production. To that end, I got a Windows Server 2003 VM up and running, complete with my web host's slightly-customized Medium trust configuration files and a copy of a recent database backup, and ran through the upgrade process. Turns out it's a good thing I did it in staging first. I discovered a...

A few months back I was working on my blog and did some database maintenance to help slim down the size of things with respect to referral logs based on some logic posted by Phil Haack. Just a couple of days ago, I wanted to see how things were looking in there and noticed the database was starting to get a little big again. The problem with doing database maintenance, at least for me, is that I don't have a dedicated SQL instance and I don't have administrative rights, so I can't, for example, run a database backup to truncate the transaction...

While I was attempting my upgrade, I figured I'd also look and see where my database space was going since I've had to have a size increase a couple of times now and I'm not generating tens-of-megabytes worth of content. The culprits: the subtext_URLs and subtext_Referrals tables. Which is to say, my list of referral sites and the links to the associated blog entries. The URLs table was in the 40MB range, which is pretty out of hand. I did a quick search to see if this was common and found this entry on Phil Haack's site from a couple of years...

Well, I gave it the old college try, but I ended up pretty well trashing my site in the course of my attempt to upgrade to Subtext 2.0, so I had to get restored from backup. Yow! There seemed to be something odd to begin with when the upgrade process wouldn't run - it sort of locked me out of the site. I got around that only to see it say I needed to "install," not "upgrade." Ummm... well, OK. So I did that. The database got upgraded, but then I hit the final wall: I'm in a medium trust environment...

I'm still working on a decent solution to the absolute URL problem I'm seeing in my RSS feed (which is why the images in my RSS feed appear broken - the images are sourced from a relative URL, like "/images/foo.gif" which, paired with FeedBurner, make it look like the images are supposed to come from FeedBurner, and they're not). Anyway, I have a sort of general-purpose HttpModule for filtering response output and converting URLs to absolute format, but it's not working with Subtext's RSS feed when compression is turned on.  I think I'm inserting myself too late in the request lifecycle so...

I just finished converting over to Subtext, and, all things considered, it went reasonably well. A lot of work went into the migration, though - a lot more than I really feel should have.  But at least I'm moved over. What I ended up having to do: Get a SQL 2005 database (pMachine was stored in MySQL). Write a BlogML export utility for pMachine (which I will be contributing to the BlogML project). Write a utility that creates a map of old IDs for my blog posts to new Subtext friendly URLs....