Nullam mi risus, congue non, porta vel, tincidunt sed, leo. Duis at tortor. Donec vitae sem quis quam tempor consequat. Nam vel lacus quis diam varius varius. Curabitur velit lorem, consectetuer ac, cursus eget, aliquet ac, eros. Etiam egestas bibendum dui. Integer nec nulla. Nullam urna. Suspendisse luctus vehicula sem. Pellentesque ligula. Etiam faucibus, elit a consectetuer egestas, tellus elit venenatis tortor, eget pharetra metus dui eu sapien. Cras ac augue. Quisque sed tellus. Pellentesque mollis arcu id dolor. Mauris pharetra erat et tortor. Ut nisi. Ut nec nunc.

Integer sed massa a justo accumsan viverra. Quisque at nisl vitae neque sodales convallis. Morbi id orci sed lectus lobortis congue. Maecenas lectus orci, varius ut, scelerisque non, commodo nec, diam. Aenean risus elit, feugiat vel, sodales eget, auctor eget, sem. Phasellus dolor tortor, tempus in, posuere sit amet, placerat sed, arcu. Suspendisse tristique. Aliquam nunc sem, bibendum sed, semper eu, placerat at, arcu. Aliquam eu tortor. Donec in dui ut orci hendrerit ultrices. Cras facilisis volutpat erat. Integer sit amet elit nec odio consectetuer lacinia. Praesent venenatis metus a erat.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Ut justo. Quisque sed libero quis tellus imperdiet auctor. Curabitur laoreet tortor sit amet dolor. Morbi metus est, dignissim vel, adipiscing in, porta rhoncus, eros. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia Curae; Phasellus dictum nulla eget eros. Donec sagittis. Pellentesque volutpat. Cras tristique aliquam massa. In blandit urna et magna. Etiam consectetuer justo volutpat quam. Vivamus viverra ipsum eget massa. Praesent facilisis augue vehicula eros.

http://www.scriptygoddess.com/archives/2004/01/06/another-revision-to-the-showhide-script/

<script type=”text/javascript”>
function showHide(entryID, entryLink, htmlObj, type) {
if (type == “comments”) {
extTextDivID = (’comText’ + (entryID));
extLinkDivID = (’comLink’ + (entryID));
} else {
extTextDivID = (’extText’ + (entryID));
extLinkDivID = (’extLink’ + (entryID));
}
if( document.getElementById ) {
if( document.getElementById(extTextDivID).style.display ) {
if( entryLink != 0 ) {
document.getElementById(extTextDivID).style.display = “block”;
document.getElementById(extLinkDivID).style.display = “none”;
htmlObj.blur();
} else {
document.getElementById(extTextDivID).style.display = “none”;
document.getElementById(extLinkDivID).style.display = “block”;
}
} else {
location.href = entryLink;
return true;
}
} else {
location.href = entryLink;
return true;
}
}
</script>

Marie b. asks if there's a way to stop MT from emailing you your own comments. There was back for 2.6 and 2.6x, and I posted that here, along with the info for stopping Blacklist from doing the same thing here and then again here for Blacklist v1.62.

Last year when MT 3.x came out, all that went out the window. I spent weeks trying to hack 3.0D and never figured it out - at which time I threw in the towel. Sure, it's frustrating to get my own comments emailed to me, and it's a pain in the ass, but the alternative was not getting anyone's comments emailed to me. That's just not an option since I like to reply to people who comment on my sites. Thankfully, marie b. brought this to my attention again today, and I saw that someone had posted the code to do this in reply to something I posted on the Support Forums, back in November.

I've just hacked and tested, and it appears to be working perfectly. So here's what you're going to need to do.

But first, a caveat: Do not try this if you a) don't know what you're doing, or b) won't take responsibility when you fuck it up and break your whole site. Because I'm not going to fix it for you.

So! All you need to do is add one line of code. Find the module

lib/MT/App/Comments.pm

Then find the line (around 429) that says:

And add this line after it:

so the code now looks like this:

That works on MT3.15. But since I'm also using MT-Blacklist 2.04b, I needed to change that. You're going to take this same bit of code and use it on

Module: plugins/Blacklist/lib/Blacklist/App/Submission.pm

on (or about) line 723. You'll see this:

Add that line after it so that it looks like this:

Piece of cake, right?

Having spent a few hours this morning researching and re-researching referrer spam among other things, I thought I'd throw some links out here.

Proposal on Referrer Spam
Blocking Referrer Spam
Referrer Spam Protection
Using Blacklist on Referrer Spam
Blacklist to Mod_Security

What this does is let you put content from a syndicated feed in your MT Template. You need the feed plugin, and then you'll have to have some way of rebuilding the template occassionally so the content updates. The MT-Rebuild.pl plugin is perfect for this. I have mine set up to update every half hour.

First, you'll need the plugin. http://www.timaoutloud.org/code/mt/index.html#mt-rssfeed. The zip file will include the feed plugin and also the rebuild plugin.

Follow the directions in the package. All you really need to do (if you've got all the correct modules installed on your hosts server) is the following:

1. Go to your MT directory and make a dir called "db".
2. Go to MT/extlib/xml and make a dir called "RSS". Put LP.pm there.
3. Put the .pl files in your plugins folder (mt-rssfeed.pl and mtlist.pl).
4. Put mt-rebuild.pl into your main MT directory NOT the plugin folder.

Configure the display according to the directions. You need a template module (mine's called "feedlist") containing the urls of each feed, one per line. Then you need an include with the mtfeed code.

Then, you need to configure mt-rebuild.pl to rebuild the page an intervals during the day. Don't do it too often or you'll piss your host off.

Here's the links referenced here:
MT-List
MT-Rebuild
MT-RSSFeed

Discussion about the plugin: (the download link in this post is no longer valid, so don't try to use it)

MT Support Forum Topic

Want to put a little "Listening to:" field in your entries? Are you using your keywords field? No? Well, you're in luck. First, put this in your index template, just above the "posted" line.

What that says is, if there is something in the Keywords field, put the "Listening to:" there with whatever is in the MTEntryKeywords field. If there isn't anything in the Keywords field, don't do anything.

Now, you need a class on your stylesheet to style what you want it to look like. I called the class "listen" and made it a pink box. Here's the stylesheet class:

.listen {
font-size: x-small;
color: #000;
margin: 10px 10px 10px 10px;
padding-left: 10px;
border: 1px solid black;
background-color: #FFD6D8;
}

So when I put something in the keywords box, it looks like this:

Remember to put that in your Individual archive templates also.

The many steps involved in getting related entries to work on your site. You need MySQL, and the MTsql plugin, and the MTAuthors plugin.

You'll need to install those two plugins, then follow Adam Kalsey's instructions.

The MTIfEmpty / MTIfNotEmpty plugin: discussed in the support forums here. Good for conditional formatting, for instance, if comments are closed it will say they're closed instead of leaving a big blank space there.