We're hunting for a really elusive bug that has popped its head up a few times now in Blocks 3.0. Unfortunately we cannot duplicate the bug here on our computers. It seems to happen only with Master Pages. We're looking for a few brave souls that use Master Pages on a regular basis. You don't have to be a technical whiz or even have experienced any problems -- we'd just like to hear from you and perhaps invite you to a little bit of Blocks beta testing.
If that sounds like you, send us an email and let us know.

We're in the midst of testing out Blocks 3.0. It's mostly a private sort of thing, but things are looking better every day and we'd like to expand our list a bit. If you're interested in having a look then send us a quick email and let us know.

And if you're interested, but not THAT interested, then just follow along with the twitter. You can get all the gory details.

Want to see a sneak peak of what's coming? Check out this post for a little screencasting goodness.

Another casualty of the changes we made for PostcardViewer was the the Blocks page block. This one required that you actually had to publish your site -- so it took a couple days before people noticed.

Blocks 2.1.2 fixes this problem and nothing else. But all are recommended to download it since without it Page blocks with blog content simply won't publish.

Go get your download.

Since YourHead software is really just little old me, and I tend to make somewhat slow progress, I thought I'd just start shipping as many bug fixes as I can. It gives everyone the opportunity of using the buggy software TODAY, and offers a little hope that something better might come very soon.

I won't usually release daily builds, but tonight I'll make an exception. I've fixed a couple of nasty bugs and added a couple important features and I thought people might be interested.

Since these releases are coming rapid-fire, I'm not going to post them to another website, so if you want to catch 'em all you should probably bookmark our RSS feed. I'll post the change list just like this one:

------------------------------------------------------------
PB Build 2 Change List
------------------------------------------------------------
- page width now reads correctly from from saved files
- added background and stroke settings to the interface and output -- missing in preview
- potential fix for z-index
- shift key no longer causes selection toggle if clicking on the resize handles
- removed some Console clutter
------------------------------------------------------------

I'm excited to say that I've just had my fourth release to my private beta testers. Things are really starting to take shape. The bugs aren't quite so debilitating, crashing, or embarrassing.
Depending on how the next few days go I'll either be releasing a public beta or at least expanding my beta pool to a few more folks.

Well, it looks like the onload event handler had some more interesting effects than I could have possibly predicted. However, at least these might be fixable. Check out my post over on the forum.

It looks like there's a bug somewhere (and I don't THINK it's in my code) that prevents the DOCTYPE header from being written to the file. All I have to do is put an "onload" anywhere in a valid spot in the content and the DOCTYPE disappears. At least so long as the output style is not set to Default -- in which case things are hunky-dory.

Anyway, I'm going to do a release without the effects, #1 because I like the border feature and #2 because it fixes a fairly nasty bug involving links.

I'll be talking with everyone I can to show them the DOCTYPE bug. Hopefully we'll get to the bottom of it and we'll have some cool effects.

This bug was really ugly. I've removed the offending zoom feature, in favor of a brand new onload zoom feature. As usual I'm trying to eat my own dogfood and I'm using the feature on my homepage. Check it out. Yes, I'll add more option -- later.

I've written a ton on the whys and wherefores of this ugly bug over on the rapidweaver forum, so I'm not going to write it all again. The short version of the story is this: The zoom just can't be done well in Safari, and if it can't be "great" then I'd rather not do it at all. So I'm stepping back a few yards (stayed up very late for a few days) and I'm punting on that feature (removing it in favor of something that I think you might like).

Go get the download and let me know what you think.