Overnight, I thought about the post I made yesterday regarding de-publishing. I’m working up an editorial policy to make it clear to my readers (both of you!) what is subject to change, what is not, and to be able to represent that changes have take place through representation of posted vs. modified dates.
One of the few frustrations I have with Movable Type is that MTEntryDate is always the date of the creation of the entry (e.g. when you clicked on “New Entry”) and not the posting date. I frequently create a post and use Movable Type’s draft mode to save it while I work on it. Sometimes, I might not post it for a day or two. If I don’t remember to manually change the entry date, I wind up “posting to the past” because the date defaults to date of creation, not date of posting.
What I would like is, for each entry, to be able to automatically indicate the time and date of creation, the time and date of posting, and the time and date of the last update.
The LastModified MT plug-in gets me that last part. I haven’t been able to find the appropriate combination of MT tags or plug-ins that will allow me to automatically distinguish the “created on” date from the time of posting.
Thoughts? Solutions?
Movable Type, Weblogs
This is a test of the Zempt blog client for Movable Type. The client runs on your local machine and posts directly to MT (I hope — this post is the test of it).
The dandy thing about it for me is that because (a) I use Mozilla and (b) no one has implemented the Mozilla Midas specification for rich-text editing in MT (yet), Zempt gives me a WYSIWYG editing environment in which to write (and edit?) MT posts.
Here goes.. . . we’re trying to post.
Update: Hey, whaddayaknow! It worked!. And it’s gonna make my XHTML a lot more valid, probably.
Movable Type, Weblogs
Looks like the archive URL formats are working nicely. Thanks to Erik Barzeski for his tips on starting a blog with Movable Type.
Movable Type
Here it is. Movable Type is up and running on my new domain. I’ve seen people complain about how difficult Movable Type is to set up. While it’s certainly more complex than Blogger, I found it to be a pretty simple process. I only hit four hiccups, and they were all simply remedied with a search of the support forums. The four hiccups? I misspelled “cgi-bin” in the mt.cfg file, forgot to un-comment a line in the mt.cfg file for the location of images, set the permissions on a directory wrong, and entered the wrong home URL. All human error.
I’m still a bit curious to see if the archive URLs are going to work out like I think they will and want them to. A couple of test posts to figure that out.
Movable Type