Print, video, sounds

Removing the Movable Type logos

Movable Type CMS splatters its logo on your pages.
Here is how to remove them.
pdf version
The last appearance issue I wanted to fix in the original installation is the fact there was a huge logo "Powered by Movable Type" in the sidebar. There was also a link to Movable Type in the footer. Finally, Movable Type seems geared to making all your content free by having you sign up for a Creative Commons license they will spray on the footer as well. You can suppress the license in the setting tab, at least I hope you can if you signed up for it by mistake like I did.
I changed the footer template in all the blogs to suppress the creative commons license if-than code, and put in "Copyright 1996-2011". I also took out the link to Movable Type's site in the footer template in all the blogs.The other big Movable Type logo is part of a widget in the sidebar, so I went into the widget tab in all the blogs and removed the "powered
 by" widget from the sidebar. Then all you do is rep-publish all your entries. I am glad to see DreamHost server never gave me a "500 internal server error" like 1&1 does.

As I suffered through the tedium of changing all all nine blogs, it occurred to me that an entry template file may be able to point and call a footer template file in the top-level site (blogID=1). Then I could set all the blogs up to use the exact same header and footer. I am not sure I want the same header on all the blogs, but I can definitely see them sharing a footer. Since the whole site shares a common mysql database there is no reason that I should not be able to set up a master footer by referring to a specific footer template file in the template files for the entries and other pages. I will let you know how if this works in a later post.
Bottom of first columnmove down to the left

[Update] Yes you can make any blog use a master module, see this nearly incomprehensible help page. The short explanation is that you can go to every blog entry template and change the page to call the footer module like this:
<$mt:Include module="Banner Footer" blog_id="1"$>
instead of the local footer module call:
<$mt:Include module="Banner Footer"$>
Alternatively you could just replace the local banner footer module code with the same code:
<$mt:Include module="Banner Footer" blog_id="1"$>
That way the master footer will appear in the entry, the index and the archive and the category pages.

Making a uniform header is more problematical. The incomprehensible help page points out your master header code would need if-than statements so each blog has the proper name, etc, I am not sure all this complexity is preferable to having 9 blog header templates you just call up and modify by hand should you want to make a common change to all of them.

The incomprehensible help page also explains how I make the master table of contents update when any blog gets added to. You go to the "tools>>plugins>>Multiblog>>settings" and you can set up the triggers that make your master table of contents update when you post any new blog entry.
move up a little to the right move down to the left

This post is in these categories:

border bar
Bottom of first column This is the end.