I've now implemented Movable Type solutions for several clients, primarily as Intranets. As with any Intranet, there are a large number of users who are only casually acquainted with the user interface and for whom a simple interface with good usability is the key to a successful experience. Unfortunately, MT is really not designed to be used casually by disinterested users, so some modifications are often needed to help those less sophisticated.
I've made some small but important hacks to the "Add Entry" bookmarklet pop-up screen, which have helped users at my client sites better get through the posting process without frustration or error.
The "Post to MT Weblog" screen is really designed for a blog administrator or a power user who has bothered spending time learning the MT interface and knows what is meant by "Trackback" and "Allow Pings."
In my experience every new user who sees the screen makes the same mistake; they forget to "Select a weblog for this post" from the drop-down menu, and then are confused when nothing appears in the "Primary Category" screen. This is an annoying problem, especially since virtually all corporate clients I've worked with roll out only a single blog for their installation.
The second issue I come across time and again is the "Where is my posting?" problem. This occurs because in many of my custom installations I have used the Categories system to determine which posts appear on which pages. Thus, the Category field has become a de facto required field, even though MT does not require that each post have a category assigned.
To solve both of these problems, I've created a hack to the bm_entry.tmpl file which hardcodes a default blog_id and requires the user to choose a category before submitting.
Installation
1. Download this file: bm_entry.tmpl and put it somewhere on your blog server.
2. Find the existing template file, located here:
/MTDIR/tmpl/cms/bm_entry.tmpl
3. Rename it so that if the new file screws things up you'll still be OK.
mv bm_entry.tmpl bm_entry.tmpl.old
4. Move the new template you downloaded into the /tmpl/cms/ directory.
5. You must edit the new file to change the default ID to the blog you wish to default to (typically blog#1 since you only have one blog, right?). Look for the lines in the code:
//this is a hack which defaults the form to a specific blogfunction defaultBlog () {
document.forms[0].blog_id.selectedIndex = "1";
setMenu(document.forms[0])
}
Change the selectedIndex="1" to the appropriate blog_id for your default. (Note, if you don't know your blog_id, you probably shouldn't be hacking with the source code).
That's it. The next time you use the bookmarklet to add a post you will be defaulted to the blog_id indicated. In addition, you will not be able to submit a new posting without choosing a primary category.
Disclaimer! This hack was written for MT 2.61, there is no guarantee that it will work on previous or future versions of the program. As with any hack, use at your own risk.
Hi Ari, and thank you for your very informational sites. I'm also very interested in corporate use of blogs and wikis.
I believe this problem could be solved even if there would be several blogs in use. With a little hacking you can add bookmark link to the blog page (if it's used by people who have access to blog) with a specification of in which blog to post in the link's GET data.
With this method the users wouldn't even have to worry about making bookmarks if they could post the blog within the blog. Basic users wouldn't have to visit Movable Type interface basically ever.
I'm not sure if I explained it well. Maybe I'll post about it when I work on this case.
PS. Do you have some relatives in Finland or what's the story of your Finnish name? :)
Posted by: Petri Vilen on July 20, 2004 8:20 AM