Posts in the Tech Category

Okay, so my “Whole Magilla” feeds—both full-content and summary—are working again, and the main archive page actually shows content.  The problem in both cases, as I mentioned in my previous post, was that WordPress’ code was throwing 404 responses.  In the case of the archive page, it would literally put up a 404 page generated by WordPress, instead of list the most recent posts.  For the Magilla feeds, the RSS files were being served up, but with HTTP 404 headers.  In feed readers that respected HTTP headers, like Firefox or NetNewsWire (and probably most others), that meant the feeds were broken.  Other feeds, such as the tech-only feed, were unbroken, but of course the most popular feeds are the Magilla feeds.

In the end, a post from Alex King showed me the way to a “fix”.  I put that word in quotes because this is really more of a hack.  No, actually, it’s just gross, but it works.  In order to get WP to stop throwing inappropriate 404s, I commented out lines 35 through 135 of classes.php in the WordPress core.  Here’s the beginning and end of the block I commented out:

if (! empty($rewrite)) {
   // If we match a rewrite rule, this will be cleared.
   $error = '404';

[...a ton of redacted lines...]

      $this->did_permalink = false;
   }
}

There you go: with one hundred lines of code commented out, my feeds and archive page work again.  This is not a good idea, but it’s all I could figure out to do.  Obviously, having modified a core file, I’m taking a chance that this won’t cause other problems.  So far I haven’t seen any, but you never know.  I’m also making upgrades much harder on myself, given that the new core file won’t have my modifications.

Similarly, I commented out the mod_rewrite.c block WP added to the end of my .htaccess file, so that I can use my own rewrites and not invoke WP’s rewriting.  With every upgrade, I’ll have to check that file to make sure the block didn’t get added back.

I’m mostly posting this as a reference for anyone who might run into similar problems with their WP 2.x installation.  It’s my hope that a future version of WP will offer some kind of hook or option that will let me easily disable WP’s rewriting and error handling code, since I already have a web server that’s configured to do those things for me.  I don’t mind if it’s a hook that I can address via a plugin as opposed to an option in the preferences, but I’d like to have it.  It would make WP a little more attractive to power users as well, since they’d know that they could do their own rewriting and error handling without having to fight with WP’s internals.

• Fixing My WordPress Install was published on Thursday, February 1st, 2007.
• It was assigned to the WordPress category.
• There have been seventeen replies.

So I upgraded to WordPress 2.1, and it immediately broke stuff.  For example, check out the RSS feed validator’s results for the summary version of my all-posts feed (full-content feed validation results; same problem).  I think it’s just so cool how the software manages to get the sever to return a 404 for a file that’s clearly being served.

Of course, I only got to that point after commenting out the IfModule mod_rewrite.c stuff WP apparently tacked onto the end of my .htaccess file.  Before that, the above-referenced feed URLs just brought up the home page of the site while preserving the feed URL in the address bar.  Keen.

Exactly the same progression of trouble has applied to the Distractions feed, too.  At first the server (or WP) was filling in the home page, and now it returns the feed along with a 404 response.

I’ve also had the same problems with the main page of the post archive—at first, it redirected to the home page.  Now it just returns a 404, although unlike the feeds, it doesn’t also create a full page to go with the 404.  At least, I don’t think it does.  I can’t see it, anyway.  A shame, too, that it does its own thing rather than use the 404 page I already defined in the .htaccess file.

Anyone have any guesses at all as to what’s going wrong, and how I can get WP to stop throwing around inappropriate 404s?  I assume this has something to do with my .htaccess file’s Rewrite rules—which worked just fine in WP 1.5.2, by the way—and the new error handling routines.  Or maybe it’s just the new error routines.

Oh, and while we’re at it, what’s the story on the “new tabbed editor” that’s supposed to let you “switch between WYSIWYG and code editing instantly while writing a post” that was mentioned in the WP 2.1 announcement?  Because I’ll be switched if I can find it.

Ah, the joys of upgrading…

Addendum: anyone know of a quick and simple way to just disable WordPress’ internal rewrite code, so I can go back to using my .htaccess file?  That might solve the problem just as well as trying to hack my way around the problem with WP, and a lot more simply.

• WP 2.1 Breakage was published on Monday, January 29th, 2007.
• It was assigned to the WordPress category.
• There have been twenty-one replies.

In case you’re one of the people who’s been following the Twitter stuff, and you’re on OS X, then kindly allow me to direct your attention to Twitterific 1.1.  Despite its paltry 0.1 increase in version number, it’s acquired some great new features.

The most wonderful addition, in my opinion, is a preference setting that lets you make the window act modal, or not, as you prefer.  Having set my copy to “act as normal window”, at least half my problems with Twitterific were abolished.  They’ve also changed the auto-hide behavior so that it will auto-hide a short interval after popping up, whereas before it would only auto-hide after a manual refresh (at least, that’s how my copy behaved).  This makes it a lot easier to ignore in the background, since it won’t behanging around until you bring it to the foreground.  Perhaps this is a side effect of it acting like a normal window.  Regardless, it’s welcome.  In addition, I like the ability to define a hotkey to bring up the Twitterrific window and the “launch when I login” option.

They’ve also added a post character counter, so you know how close you are to hitting the tweet cap.  That’s nice to see, though as I understand it, the number of characters permitted for a post is dependent on the number of characters in your username.  Twitterific just gives you a flat 141 characters—which, given the basic nature of Twitter, seems like it really ought to be more than enough.

Now, if it just let me define my own background-foreground colors and made it easier to replace the alert sound, I’d regard it as being pretty much perfect.  (Yes, I can dig into the package contents and replace the alert sound, but I’d rather there was a preference setting so that I don’t have to futz around inside the package every time I update the software.)

Oh, and if you’re a Twitterific user, you absolutely want to add Twitterific as a friend, since they use that channel to tweet release announcements and tips on using Twitterific.  If I’d had them added to my Twitter account, I wouldn’t have had to post about my frustration over trying to change usernames—they’d tweeted the answer the day before I posted here—and could have thus been spared the shame of broadcasting to the world my ignorance of the proper spelling of “terrific”.  Though I suppose in that case, I’d still be ignorant, so maybe it’s better I posted after all.

Well, either way, if you’re using Twitterific 1.0 or an OS X user interested in using Twitter, check out the new version.

• Twitterific 1.1 was published on Sunday, January 28th, 2007.
• It was assigned to the Personal and Web categories.
• There have been four replies.

I’m entirely willing to admit that this is me being a half-blind doof, but how do I change the Twitter account in Twitterrific?  I set it up to talk to one of my accounts, and I want to change that so it logs into and updates the other account.  I poked around the application preferences, dug through the package contents, and searched my hard drive for related preference and application support files.  I came up empty.  So now, O LazyWeb, help me, please!

(Anyone who knows me well is probably now surprised that this was not a post about how frustrated I am that they left off the second “f” in the application’s name.)

Update: the login information is stored in the Keychain (thanks, Dan!).  I altered the login information via Keychain Access, and that fixed things.  What I found interesting is that Twiterrific stores an e-mail address as the login, not the username.  So what happens if someone signs up two usernames via the same e-mail address?  How would Twitterrific tell the difference?

• Twitterrifically Frustrated was published on Tuesday, January 23rd, 2007.
• It was assigned to the Tech category.
• There have been thirteen replies.

After a couple of months of fairly determined avoidance, I finally joined Twitter a week ago.  I’m already thinking about leaving.  Have been for the last six days, in fact.

There are two easily-explained reasons why I want to just walk away.  The first is that in order to have a public comment stream and also be able to share more private messages with my friends, I have to have two accounts.  If I could post friends-only messages to an otherwise public account, then I’d only need one account.

And why would I use a public commentary service for private information?  Because it is a very good way of keeping my friends informed of where I am, where I’ll be headed next, what’s happening in my family life, and so on.  That’s not public information, to my mind.  Using Twitter is a lot easier than setting up a private blog to distribute the same information.  (Side note: if you had a friendship request with me declined, this is why.  No, I don’t hate you.)

The second reason is that I don’t have a way to filter out people who are swamping my Twitter stream.  Yes, I’m very glad that you have so much to say, but you’re burying the other people who are just as interesting but not quite so loquacious, obsessive, or just plain bored.  In my current short list of friends, I have two that are, um, extra-expressive.  (Both women, in fact.  No comment?)  I want these people to remain friends so they can get my updates, infrequent though they may be.  I also want to see what the rest of my friends and followed are saying.  How to resolve it?

Sadly, “leave” only filters their stuff out of phone and IM updates, neither of which I use.  It doesn’t take them out of the RSS feed nor the web view, both of which I use.  Is the solution to de-friend them and let them just follow me?  Sure, for the public account.  For the private personal-info account, that solution fails; they’ll stop getting my updates.  I just wish there was a way to say “this person is my friend, but I’d only like to get updates from them through the following services”.  That way I could set the chatterers to show up in the web view and nothing else, thus restoring some sense of balance and diversity to my RSS feed and thus to Twitterific.

Then there’s the bonus reason I want to throw the whole thing into my bit-bucket:  the way people are using Twitter right now, it’s rapidly becoming the most inefficient and unusable version of IRC ever.  Look, people, if you want to chat, then get a chat room.  You know?

I know, Twitter is new and growing.  Feature sets and social conventions are still in flux and expected to evolve.  Personally, I feel like there’s the kernel of a really good service in there, only not quite the one they’re offering.  I’m not saying Twitter is useless or somehow wrong: it clearly provides something that some people want, and it does what it does fairly well.  I just have the sense that there’s a similar service with a different focus that would provide something that some other people want, myself among them.  Anyone else feel the same way?

• The Twitters was published on Sunday, January 21st, 2007.
• It was assigned to the Personal and Web categories.
• There have been thirty-seven replies.

If you’ve been waiting to register for An Event Apart Boston, running March 26-27, the detailed schedule has been announced and the brand-new store has opened its doors.  Hie thee hence to sign up for two great days with nine amazing speakers in Boston’s historic Back Bay!  You’ll be glad you did.

(Pssst!  Just between us, you’ll be even more glad if you input the discount code AEAMEYE when you register.  It’ll give you a further $50 off the already-discounted Early Bird price, for a total savings of $150.  Add to that the discounted room rate at the conference hotel, and you could save something like $450 off the regular conference registration and room rates.)

The overwhelming feedback we got from 2006 attendees was that they wanted more, more, more.  More speakers, more insight, more time.  So that’s exactly what we’re doing with AEA Boston.  This is going to be the best Event Apart yet—with that speaker lineup, how could it not be?  Ethan Marcotte’s “Web Standards Stole My Truck”, Dan Cederholm’s “Interface Design Juggling”, Steve Krug’s “The Web Usability Diet”… and eight more sessions just as fascinating.  Furthermore, we’ll close out Day Two with live critiques of sites submitted by attendees, making recommendations on design, copy, code, and more.

One thing we’re not changing as we move from one day to two days is how we take care of attendees.  We’ll have delicious food for lunch and breaks both days, so you can relax and chat with your colleagues in attendance and not have to worry about finding a food court and running back to catch the afternoon sessions.  Our buddies at Media Temple will be throwing a first-night party for everyone so you can unwind and maybe do a little networking.  The fine folks at Adobe will have some great stuff to raffle off, with your registration as your raffle ticket.  In fact, it’ll be so great that they can’t even tell us what it is yet!  And those are just the high points.

Amazing speakers, a great location, great service, and big savings.  What more could you ask?

• Register for AEA Boston! was published on Thursday, January 11th, 2007.
• It was assigned to the An Event Apart and Projects categories.
• There have been three replies.

Last Thursday, I came down from the office to discover a stack of five boxes on the front porch.  Three were for Kat, who is one of those annoying people who plans way ahead for Christmas, and two others were my author copies of CSS Web Site Design (formerly “CSS Hands-On Training”).  This is a title I did for lynda.com, and published by Peachpit, and it’s most tersely described as “Eric Meyer on CSS, but for beginners”.  It’s also the hard-copy version of the video training title “CSS Site Design“, and includes all the videos and exercise files from the video title on a CD-ROM bundled with the book.

After I’d hauled all that into the front hallway, I grabbed my car keys and headed out the back door to run my errand.  At which point I nearly fell over two more boxes, these containing my author copies of the third edition of CSS: The Definitive Guide from O’Reilly.  This is of course an update of the second edition, which contains some updates based on the latest version of CSS 2.1, expanded selector coverage, updated compatibility notes taking IE7’s improvements into account, and corrected errata from the previous edition.  It’s not a major update compared to the second edition, admittedly, but if you don’t already own the second edition, it’s well worth acquiring (if I do say so myself).

It’s a bit funny that both sets of books arrived on my doorstep the exact same day, considering that the two projects started out well separated, and gradually synched up.  At first I was going to write one and then the other, but various complications set in and they started to interweave.  I finished their final reviews with a whole lot of overlap—that was a fun couple of weeks—and now, the waves have fully amplified.

What really cracked me up was that the next day, I got packages from both Peachpit and O’Reilly, each containing a single copy of the respective books, and each containing a note along the lines of “Here’s your advance copy; the rest should arrive in a few weeks!”.

• Two Books Together was published on Friday, November 17th, 2006.
• It was assigned to the CSS and Writing categories.
• There have been six replies.

Let’s cut right to the chase: An Event Apart is growing to become a two-day conference.  We’ll have at least four two-day shows in 2007; see the announcement for more details.

The first show, in Boston, is already confirmed.  We’ve signed the contracts and everything.  Registration isn’t open yet, and won’t be until early January, so you have plenty of time to get the budget approval and be ready to sign up as soon as seats go on sale.  Like I said, early January.  A more specific date will most likely emerge near the end of December.

You’re going to want to get geared up for this, because the speaker list is flat-out amazing:

• Steve Krug (that’s right, Mr. “Don’t Make Me Think!” himself!)
• Dan Cederholm
• Molly Holzschlag
• Andrew Kirkpatrick
• Cameron Moll
• Ethan Marcotte
• Jason Santa Maria
• Eric Meyer
• Jeffrey Zeldman

Honestly, I can hardly wait to hear everyone on the list.  Well, except me.  I hear me all the time.  But everyone else?  Total gold!

Note that this is the speaker list for Boston; the other cities will have different lineups.  Obviously not 100% different, but I expect each one will be fairly different.  Still awesome, of course.

So what are we going to cover?  Best practices.  That’s really what it’s all about, whether we’re dissecting code or talking about usability or whatever.  Jeffrey and I are going to push every last speaker to pack their talks with insights regarding the current state of the art in their respective fields.  We’re going to push ourselves twice as hard to do the same.  What we want is to have everyone walk out saying, “Now I know where things are and where they’re going”.

The size of the event will increase along with the days, from our usual 100 seats to 400 or so.  AEA is now, as I said, a full-on conference.  It’s a big step, but it’s the right one.  The most common feedback from this year’s attendees was that one day just wasn’t enough, and looking back, we have to agree.  That’s especially true given that the feedback from our only two-day event of 2006 indicated that people really liked the length and the amount of information they got out of it.  So it’s time to step up.

Even from this side of the Atlantic, I hear the cries of our European brethren.  When will we visit your worthy shores?  It’s a fair question.  It could happen in 2007, or it might not be until 2008.  How’s that for precise?  I’m sorry, but I can’t do any better than that right now.  Our original plan had been to run a year’s worth of events to shake out the bugs and then look to other lands.  Instead, we discovered that the events were too small, temporally speaking, and needed to be dramatically revamped.

So now we need to run a few of the larger events to get the bugs worked out before going afield.  The good news is that a lot of the bugs are already smoothed out.  We just need to get a handle on the larger format, which has a whole new set of requirements.

So we’ll be at the Boston Marriott Copley Place at the end of March.  I hope you’ll be there too!  (And if you are going to be there and are a member at Upcoming, add yourself to the listing.  Otherwise, feel free to leave a comment here.  Thanks!)

• AEA To Grow in 2007 was published on Wednesday, November 15th, 2006.
• It was assigned to the An Event Apart, Speaking, and Standards categories.
• There have been seventeen replies.