Posts Tagged ‘movable type’

So, that bad idea I was going on about

technology

Just thought I’d let you know, it’s back on like Donkey Kong! Yep, I’m back to going back to going back to the drawing board. Again. This time for reals — I’m being totally cereal, you guys.

Plus, I’ll have a nifty GPL–ed WordPress theme that looks just like this site! So you too can steal my theme and fill it full of crap I’d never use. Like TrackBacks, or lots of ads, or pictures of cats, or…comments.

Point being, soon I’ll be transitioning this site back to WordPress (part 5).

Good times, good times.

/ /

Comment, sucker!

So, I had this idea about WordPress…

technology

Back in 2006, I had this nifty idea to jettison comments. First of all, they added little to the immediate subject. Also, I didn’t like the compromises I had to choose from with either anonymity or registration. The more popular my site became, the harder it was to police…unless there was nothing to police.

That led to be put together my site sans commentary. It seemed like it made sense at the time, so I went with it. First I was using TextPattern (and I still keep that thing around, somewhere — I love it). But I went with WordPress. And I turned the comment off. Permanently.

I guess my decision was based on a combination of hype and contempt. WordPress was just getting exciting, with the new version 2.0 starting to hit its stride. Messing with templates was just enough to keep me interested, and to make a site that worked just how I wanted. Not having to style comments, or figure out how to con people into registering was refreshing.

It wasn’t long, however, before I started to find the problems with the platform. While the system works well as a one–blog producer, it really isn’t that complete as a full–site solution. Plus, to get it to do anything, you needed a plugin.

While I found ways to work around the limitations, I kept on running into the same problem over and over again: why am I making the server do all that work on a page that almost never changes? That was the whole point of moving to Movable Type — to cut down on server load for a resource–light site.

It’s funny now seeing the other blogs that are buying into my 2006 philosophy. I got over that earlier this year, when I decided to be more of who I really am. That, and to interact with who I know you are (or don’t know, I guess). Now I’m all about the comments and the peoples. And I think I’m ready for my soapbox…

Movable Type soapbox

As a sidenote, this is just me telling anyone that’s gearing up for my comments–less WordPress experience: have you thought of just writing the HTML yourself? I mean, it’d make your server happy, plus you’d learn a new skill!

But for those of you who don’t want to cook it yourself, there’s always Movable Type. It will make the pages work exactly the same while allowing just as many comments. Plus, you can stick it to the man (if you’re really all that against–the–man–y).

As another added benefit, you’ll get the pleasure of answering, “well, have you even tried WordPress?” about 50 times a week. That’s always a reassuring way to let you know that people know what they’re talking about.

/ / /

3 Comments »

Halo, wurld

technology

While putting this nifty site together, I figured I would need to do two important things:

1. Reconfigure the comments so people could interact with it.

2. Not delete it before anybody saw it.
Well, as far as the first one goes, Mission Accomplished! Now let’s see how long number 2 lasts. But the reason for this post is because of the nifty comment system I put in (and how simple it was to hack together).

Because, you know, comments are my life-blood. Yeah, icky, I know.

First of all, I had to get the threading going. You can see that threading in the comments below. That is part of the power of Movable Type 4.2.something…and all it took was figuring out how to get the thing to nest correctly.
What I was really pleased about MTOS 4.2.something was that you could create something like Brian’s Latest Comments without using a single plugin. To get it to work, all you need to do is replace the Recent Comments Widget code with this:

<mt:If tag="BlogCommentCount">
<div class="widget-recent-comments widget">
<h3 class="widget-header">Recent Comments</h3>
<ul class="recent-comments-list"><mt:Entries recently_commented_on="10" >
<div class="widget-content">

<li><a href="<$mt:EntryPermalink$>"rel="bookmark"><$mt:EntryTitle$></a>
<mt:Comments lastn="7" sort_order="descend">
<mt:CommentsHeader>
(<$MTEntryCommentCount singular="1" plural="#" none=""$>):</li>
<li>
<small class="recent-comments-list">
</mt:CommentsHeader>
<mt:if name="__last__">
<a href="<$mt:CommentLink$>"><$mt:CommentAuthor$></a>
<mt:if tag="MTEntryCommentCount" gt="5">
[<mt:CommentEntry><a href="<$mt:EntryPermalink$>">…</a>]</mt:CommentEntry>
</mt:if>
<mt:else>
<a href="<$mt:CommentLink$>"><$mt:CommentAuthor$></a>,
</mt:if>
<mt:CommentsFooter>
</small>
</mt:CommentsFooter>
</mt:Comments>
</li>
</mt:Entries>
</ul>
</mt:If>

I swear I have no intention of ever doing any of that Digg-bait-y kind of how-to posts, but I wanted to show off how easy it was to get this to work with just the built-in Movable Type tags. And the first four comments here are just to show off the way things thread, I am not that desperate for comments.

Probably.

/ / / /

5 Comments »

© 2003-2017 John Stansbury. All rights reserved. Entries (RSS) Comments (RSS). 18 queries. 0.390 seconds.