Results tagged “MT4”

Found another probem with the Post Office plugin for Movable Type: you can't include any kind of punctuation characters in the subject line of your email message/entry title, otherwise it will munge the image file name that goes along with it.

Granted, the Post Office plugin isn't to blame for this, since it won't rename the image at all; this was functionality I had to add in later. So, really, it's my own fault.

Well, it's fixed now. Weird chars are replaced with underscores.

Good little tip from BrainLog

In MT 4, the QuickPost bookmarklet pre-populates the entry's title with the title of the page, and sticks the URL of the page and the selected text in the message body. The URL is not a link, it's just the URL, followed by two <br /> tags, then the selected text, if any. Like this:

[Title:] Title Of Page
[Body:]
http://url-of-page/<br /><br />

Selected text, if any.

The new behavior is weird. Entry titles are all the rage with newer blogs and RSS feeds, so I'll grant that I'm behind the times for not using entry titles on short link-y entries. And perhaps usability studies showed that most people didn't want the page title to be the link text, though it doesn't seem like a hassle to make that the default. But I can't think of a reason why I'd want to use the URL without being a link.

Revising Movable Type 4's QuickPost Bookmarklet - BrainLog

After playing around with the Movable Type Motion Beta (I've got a copy of it running somewhere), I spent the better part of an afternoon trying to figure out if the problems with updating external app streams (such as Twitter updates) were related to some kind of configuration problem or related to the beta-state of Motion. After realizing that the run-periodic-tasks script for my permanent blog does nothing for installed betas, or other instances of Movable Type (me stupid), I realized that MT still hasn't corrected some easy errors in their modules. Nor have I. The problem is fixed now, and I'm writing down two simple fixes to two hard-to-research problems.

Problem 1: Can't locate MT/Bootstrap.pm in @INC

So, say you're getting a constant error in your daily cron logs when trying to do background publishing in Movable Type. You know, you're trying to run the run-periodic-tasks script to take care of background tasks by setting up a cron job, either daily, or six times an hour. Assuming your crontab syntax doesn't suck ass, now you're getting messages that look like this:

Can't locate MT/Bootstrap.pm in @INC (@INC contains: ...

This website has some good examples on how to fix this (hint: you don't have to modify @INC, you can simply modify your run-periodic-tasks file).

Getting background publishing to work in MT 4.1 -- GoBecky.net

The problem is that '..lib';. It's simply pointing to the wrong place in the MT file structure, which is weird, given that it's their app and all, but whatev. So what you need to do is point the script to Bootstrap.pm using the absolute filepath, and all will be well.

Problem 2: Subroutine MT::Template::Context::post_process_handler and Subroutine MT::Template::Context::add_global_filter

After upgrading your v2.x of Movable Type to v3.x or even v4, you may see these messages in your daily cron logs, if you're running the run-periodic-tasks script to enable background publishing and housekeeping:

Subroutine MT::Template::Context::post_process_handler redefined at /usr/local/www/cgi-bin/mt/extlib/bradchoate/postproc.pm line 41.

Subroutine MT::Template::Context::add_global_filter redefined at /usr/local/www/cgi-bin/mt/extlib/bradchoate/postproc.pm line 22.

Took me a while to sort this out, but only because I enabed run-periodic-tasks for two fresh installations of v4, and there were no errors in the logs. As discussed here, the problem is that the postproc.pm isn't used in v3 or v4 of Movable Type. To fix these very noisy messages in your crontab logs, go into /usr/local/www/cgi-bin/mt/plugins and edit the processtags.pl file, replacing:

use bradchoate::postproc;

with something like this:

if (MT->VERSION =~ m/^2.2/) { require bradchoate::postproc; }

or even just comment out the line altogether. You'll notice all your post processing still works, and you'll get no more error messages.